Skip to main content
Proofable MCP uses the Authorization Code grant with PKCE. The user signs in on Proofable with the same passkey or wallet flow as the product.
Most clients only need https://mcp.proofable.me/mcp and the sign-in they open. This page is for custom MCP hosts, security review, and raw HTTP integration.

Flow overview

/oauth/authorize validates OAuth parameters. Without a session it redirects to https://proofable.me/verify?intent=mcp&returnTo=/oauth/authorize?.... After login it issues a single-use code (5-minute TTL) and redirects to redirect_uri.

Discovery

Protected resource metadata

A request with no credential, on any method including initialize, returns the challenge that starts DCR and PKCE, so the first sign-in happens when you add the connector. An access key uses the same URL as a Bearer token. The anonymous surface at https://mcp.proofable.me/mcp/public serves the handshake, the advertised tool list and the four keyless tools for directory listings and account-free checks.

Authorization server metadata

Authorization

The examples on this page use the Proofable SDK CLI loopback flow (proofable auth --oauth), which identifies as proofable-cli. A host MCP client sends the client_id that DCR issued to it, its own registered redirect_uri, and the same resource.

Token exchange

Response:

Refresh tokens

Refresh tokens last 30 days and rotate on each use. Include offline_access in the initial scope to receive one.

Token claims

The MCP access token is a JWT: The MCP server accepts a token only when aud, iss and token_use match these values and the token is unexpired and unrevoked.

Scope model

These four scopes are the complete public permission model. Access keys (npk_*) are a full-profile credential.

Revocation

Revoking an access token also invalidates all associated refresh tokens.

Registered clients

Host MCP clients use a URL-only MCP config. The host reads /.well-known/oauth-protected-resource, registers itself at /oauth/register, and owns its PKCE and silent-refresh lifecycle. Host clients send their own DCR client ID, never proofable-cli.

Security properties

Auth

Sign-in and access keys.

Endpoints

Discovery URLs.
Last modified on November 16, 2026