Skip to main content
Do this once. Afterwards, an agent with a browser can sign in and sign up for you on any site that offers Are you an agent? Not connected yet? Your agent can still sign up, and you claim the account afterwards. Your agent connects to this MCP server through your Versine account:

​
1. Create a connection

Sign up at My. Open Account → Connect an assistant and copy the MCP URL into your agent’s remote MCP settings. Choose OAuth, then Connect or Authenticate; some clients have a separate authentication command after adding the URL. Your agent opens the same My login, with Google or email/password. If you’re already signed in, you go straight to the approval screen. Check the assistant name and callback destination, then choose Allow connection. The name is supplied by the client, not verified by Versine. Your password and My session are never shared with the assistant. The client handles the tokens: access lasts 10 minutes, refresh tokens rotate, and the connection lasts up to 90 days. Disconnecting in My invalidates both access and refresh tokens immediately.
Use Streamable HTTP, authorization code with S256 PKCE and dynamic client registration (RFC 7591). Versine publishes protected-resource metadata (RFC 9728) and authorization-server metadata (RFC 8414). The resource and audience are exactly https://api.versine.com/mcp; the required scope is mcp:tools. Clients can additionally request openid email for account identification and email verification status. The email scope requires openid. OAuth-only clients remain supported. URL-based Client ID Metadata Documents are not supported in this version.
In ChatGPT’s MCP configuration, use OAuth with DCR. To enable OpenID Connect, use the MCP-specific values:Do not use the root platform-login OIDC discovery or /userinfo endpoints here. Those serve platforms integrating Versine, not assistants connecting to My. The MCP authorization, token and registration endpoints remain under /mcp/oauth.My asks for explicit permission to share your account identifier, email and verification status. UserInfo accepts the MCP access token in the Authorization: Bearer header and supports GET and POST. It returns sub for openid, plus email and email_verified when email was approved. It does not include other Wallet fields. Existing connections do not gain these identity permissions automatically; start a new consent flow.email_verified reflects the account email’s actual verification status, not a value supplied by the agent or Wallet. Password-only signup can leave it false; enabling OIDC does not verify the address. ChatGPT’s enterprise protection requires a verified email and a workspace with the corresponding domain verified. It can prevent connecting a corporate identity outside that organization’s workspace. See OpenAI’s authentication guidance.
In Account, expand Advanced: manual bearer token for older clients, name your assistant and choose Create MCP connection. Copy the token directly into its secure MCP settings as Authorization: Bearer <token>. It is shown once, expires after 90 days and cannot refresh. Existing manual connections continue working until revoked or expired.
Keep tokens out of chats, source files and screenshots. Connecting an assistant is separate from a platform’s OIDC client credentials and agent sign-in flow.

​
2. Use it

Ask your agent to do something on a site that offers Are you an agent? When it reaches the login page, it clicks the button, reads the one-time code on the Versine page and approves it through the connection. The page then completes the sign-in, and that browser returns to the site signed in as you. If you have no account there yet, the same sign-in creates one. If the site has terms, you accept them once in Approvals. The agent waits and can’t accept for you.

​
How a sign-in completes

Only the browser that started the sign-in can complete it. If the page stalls, reload it; if the site still shows you as signed out, start again from its sign-in button. The agent should approve only codes from a Versine page it opened through the site it’s using. Versine can’t verify that the approving agent controls that browser.

​
Claim an account your agent created

An agent that isn’t connected to Versine can still sign up on sites that offer Are you an agent? It gets a temporary account with limited access, and sends you a claim link.
  1. Open the link within 24 hours and sign in to My, or create an account.
  2. Verify your email and accept the site’s terms.
  3. Connect the agent to Versine and ask it to sign in again. It reaches the same account with your verified profile, subject to the site’s agent permissions.
Anyone with the link can claim the account, so don’t forward it.

​
Share your details

Save details in Wallet so your agent can fill in sign-up forms: first and last name, email, phone, company and job title. Your phone is shared only after you verify it by SMS in Wallet. If the agent needs something you haven’t saved, it asks. You get a request in Approvals and can fill it in or decline; requests expire after 24 hours. Details go to your agent, not to sites: Versine doesn’t add them to sign-in tokens or webhooks. Never give your agent an SMS code.

​
What the agent can do

  • Sign in to, or sign up for, sites that offer Are you an agent? It never sees a password.
  • Read the details in your Wallet.
  • It can’t accept terms for you, unblock a site or change your Versine account.

​
Stay in control

  • Platforms: see where your agent has signed in, and revoke access.
  • Blacklist: block a site. Only you can remove it.
  • Account: disconnect an agent. Its token stops working immediately.
Revoking doesn’t delete your account on the site or end a session you already have there.
Every result includes nextAction and retryAfterMs. Follow nextAction, and poll only at the given delay.