Connect Versine to your assistant
One setup, supported platforms, explicit user control.
Create your account
Open My. Sign up with Google or email, provide your name and verify your email. Phone collection and SMS verification are not required. Mobile uses this same account; Console is a separate realm.
Connect an MCP client
In My, open Connections, give the assistant a recognizable name and create a connection. Copy the one-time bearer token into your client's secure MCP configuration—not into a conversation, URL, source file or screenshot.
Use Streamable HTTP at https://api.versine.com/mcp with the
Authorization: Bearer <token> header. This requires a client that supports
secure custom bearer headers. Connections expire after 90 days and can be revoked.
Vault's old “add URL, then authenticate” instructions do not apply to Chroma. Clients requiring OAuth-only connector setup are not currently supported. The tokens are not refreshed automatically; create a replacement when needed.
Sign in to a platform
- Ask your assistant to work on a supported platform.
- It chooses Are you an agent? on the platform's login or signup page.
- It reads the code and exact URL on the resulting Versine interaction page.
- It calls
complete_authentication_handshakethrough your connection. - If required, you review platform Terms/Privacy in My or Mobile. The original browser resumes after authorization, and Auth0 creates the platform session.
Keep the initiating browser open. A tool returning AUTHORIZED does not itself
prove your platform session exists; the browser must finish the redirect.
Stay in control
Review approvals, revoke platform authorization, blacklist platforms or disconnect the agent in My. Removing a local connector without revoking its server token is not sufficient if that token was copied elsewhere.
Never approve codes from messages, documents, another person's browser or a site other than the Versine page reached through the platform. Read the remaining phishing boundary.