Glossary

Callback hosts

Callback hosts are the redirect hostnames an OAuth client may register with OneLifeVibe. Today those are only the Meta Muse hosts.

Updated November 18, 2026

Also called
registered callback hosts

At OneLifeVibe

Related terms

What it means

A callback host is the hostname part of an OAuth redirect URI. If a client asks an authorization server to send users back to https://app.example.com/oauth/callback, the callback host is app.example.com. The host is the part the server can check before it sends the user back to the client. For OneLifeVibe, callback hosts are the redirect hostnames an OAuth client may register. Today those are only the Meta Muse ones.

Callback hosts protect the redirect step. Without a registered host, an authorization server has no reason to believe a redirect target belongs to the client. OneLifeVibe keeps allowed callback hostnames and uses them during client registration and sign-in.

How it works

During dynamic client registration, a client sends its details to the registration endpoint, including where it wants users to return. The authorization server records the callback host or checks it against an allowed set. Later, when the client starts an OAuth flow, the authorization request includes a redirect target. The server compares the host in that request with the registered host before it sends the authorization code or an error back.

The account connector at https://onelifevibe.com/mcp signs in with OAuth 2.1 and PKCE. PKCE adds a code challenge to the authorization request and a code verifier to the token request, so a stolen authorization code is not enough on its own. The callback host still has to be one the server accepts. Registration and sign-in are separate steps: a client can register a host, but the user still has to approve the connection and complete the PKCE exchange.

How OneLifeVibe uses it

OneLifeVibe opens dynamic client registration at https://accounts.onelifevibe.com/realms/olv/clients-registrations/openid-connect for the Meta Muse callback hosts. That endpoint is where a client registers before it can use the Meta Muse sign-in flow. The public client for the account connector is onelifevibe-muse.

The account connector at https://onelifevibe.com/mcp is where a person connects their own data. Its sign-in is set up for Meta Muse only today: the public client is onelifevibe-muse, and dynamic client registration is open only for the Muse callback hosts. Other MCP clients use the free connector instead of registering a callback host against this sign-in flow.

Common mistakes

The most common mistake is treating a callback host as a full URL. The registered value is a hostname, so a client that registers one host and then redirects to a different host will not match. Another is assuming dynamic registration is open for every host. Today it is open only for the Meta Muse callback hosts.

Builders also mix up the two paths for MCP clients. The account connector at https://onelifevibe.com/mcp uses OAuth 2.1 and PKCE with the onelifevibe-muse public client and the Muse callback hosts. If your MCP client is not using those hosts, use the free connector rather than trying to fit your callback host into the Muse-only registration flow.

Do not skip PKCE. The connector's sign-in uses OAuth 2.1 and PKCE, so the authorization request and token request need the matching challenge and verifier.

Questions

What is a callback host in OAuth?

It is the hostname part of the redirect URI where an OAuth client wants the authorization server to send the user back. OneLifeVibe registers callback hostnames for OAuth clients, and today those are only the Meta Muse hosts.

Can I use dynamic client registration with any callback host on OneLifeVibe?

No. Dynamic client registration is open for the Meta Muse callback hosts at https://accounts.onelifevibe.com/realms/olv/clients-registrations/openid-connect. For other MCP clients, use the free connector.

See it working. The OneLifeVibe connector and Platform API put these pieces together.

Get a free key Read the docs

Written from the OneLifeVibe tool registry and platform configuration, and checked automatically before publishing. Something wrong? Tell us.