Discovery and endpoints - Proofable Docs

The MCP URL and the HTTP API use different transports and base paths. Discovery and the agent card list what your integration needs.

MCP endpoint

URL	Role
`https://mcp.proofable.me/mcp`	MCP. Setup

OAuth discovery

URL	Role
`https://mcp.proofable.me/.well-known/oauth-protected-resource`	Protected resource metadata (RFC 9728 origin)
`https://mcp.proofable.me/.well-known/oauth-protected-resource/mcp`	Protected resource metadata (RFC 9728 path insertion)
`https://proofable.me/.well-known/oauth-authorization-server`	Authorization server metadata (RFC 8414)

OAuth endpoints

URL	Role
`https://proofable.me/oauth/authorize`	Authorization endpoint (browser login)
`https://proofable.me/api/v1/auth/mcp/token`	Token endpoint (code exchange + refresh)
`https://proofable.me/api/v1/auth/mcp/revoke`	Token revocation

Full OAuth reference: MCP OAuth.

Other discovery

URL	Role
`https://mcp.proofable.me/.well-known/mcp`	MCP discovery (extensionless handshake)
`https://mcp.proofable.me/.well-known/mcp.json`	MCP discovery
`https://proofable.me/.well-known/mcp`	Same discovery card on the product domain (`url` stays `https://mcp.proofable.me/mcp`)
`https://mcp.proofable.me/.well-known/mcp/server-card.json`	MCP server card
`https://mcp.proofable.me/.well-known/glama.json`	Glama connector claim
`https://proofable.me/.well-known/a2a/agent-card.json`	Platform A2A agent card. Docs
`https://proofable.me/.well-known/agent-card.json`	Platform service discovery and ERC-8004 registration status

MCP OAuth

OAuth flow reference.

Setup

Install and configure.

Last modified on October 5, 2026