Glossary
Public client
An OAuth client that cannot keep a secret, so it uses PKCE instead of a client secret. OneLifeVibe's Muse client onelifevibe-muse is a public client.
Updated November 13, 2026
- Standard
- RFC 6749 (The OAuth 2.0 Authorization Framework)
- Also called
client without secret
At OneLifeVibe
- OneLifeVibe requires PKCE with the S256 method for the account connector. Meta Muse uses the public client onelifevibe-muse with PKCE and no client secret.
- The account connector https://onelifevibe.com/mcp (a person's own data) signs in with OAuth 2.1 and PKCE; today its sign-in is set up for Meta Muse only (public client onelifevibe-muse, and dynamic client registration open only for the Muse callback hosts), so other MCP clients use the free connector.
Related terms
What it means
In OAuth 2.0, a public client is an application that cannot keep a client secret. RFC 6749 calls this a client without a secret. The app might run on a phone, in a browser, on a desktop, or as a command line tool, where anyone with access to the device or the code can read the secret. So the client does not use one. It relies on PKCE to protect the authorization code exchange. OneLifeVibe's Muse client onelifevibe-muse is a public client.
How it works
With the authorization code flow, the client sends the user to the authorization server, gets back a code, and exchanges that code for tokens. A confidential client proves itself at the token endpoint with a client secret. A public client cannot do that, so PKCE adds a code verifier and a code challenge. The client creates a random verifier, hashes it with the S256 method, and sends the hash as the challenge with the authorization request. When it exchanges the code, it sends the original verifier. The server hashes the verifier and checks it against the challenge. An intercepted code is not enough on its own because the attacker does not have the verifier.
How OneLifeVibe uses it
OneLifeVibe requires PKCE with the S256 method for the account connector. Meta Muse uses the public client onelifevibe-muse with PKCE and no client secret. The account connector at https://onelifevibe.com/mcp gives an app access to a person's own data and signs in with OAuth 2.1 and PKCE. Today its sign-in is set up for Meta Muse only. Dynamic client registration is open only for the Muse callback hosts. Other MCP clients use the free connector.
Common mistakes
The main mistake is treating a public client like a confidential one. Putting a client secret in a mobile app or a browser app does not make it secret, and onelifevibe-muse does not use one. Another mistake is skipping PKCE or using a weaker method. OneLifeVibe requires S256 for the account connector, so a request that does not use it does not meet the requirement. Do not assume dynamic client registration is open for any callback host. It is open only for the Muse callback hosts, and other MCP clients use the free connector.
Questions
What is a public client in OAuth?
A public client is an OAuth client that cannot keep a client secret, so it uses PKCE to protect the authorization code exchange. RFC 6749 describes it as a client without a secret. OneLifeVibe's Meta Muse client onelifevibe-muse is an example.
Can any MCP client use the OneLifeVibe account connector?
The account connector at https://onelifevibe.com/mcp currently has sign-in set up for Meta Muse only, using the public client onelifevibe-muse. Dynamic client registration is open only for the Muse callback hosts. Other MCP clients use the free connector.
See it working. The OneLifeVibe connector and Platform API put these pieces together.
Written from the OneLifeVibe tool registry and platform configuration, and checked automatically before publishing. Something wrong? Tell us.