Read first
- Home — hosted MCP endpoint, then Connect
- Connect Proofable — chat, IDEs, jobs, listings, and proofs
- Agent setup to set identity and permissions
- MCP tools for exact tool behavior
- Trust for checks and reusable proofs
- Standards & interoperability for how Proofable uses existing protocols
MCP
Product server:https://mcp.proofable.me/mcp for profile, proofs, listings, permissions, agents, and private context.
Not the product: https://docs.proofable.me/mcp for documentation search only (Mintlify).
- Register
https://mcp.proofable.me/mcpin the host (marketplace, registry, or URL-only config). - Click Connect in the host.
- Follow Connect Proofable and the MCP workflow. Reuse proofs before you verify again.
npk_*) are for servers and CI only.
Rules
- Browser → Proofable: SDK (
ProofableClient, widgets) or Hosted Verify. Do not callapi.proofable.mefrom the browser with secrets or ad-hoc headers; use a server proxy when you need custom server-side calls. - Server → Proofable:
gateCheck, eligibility, secrets, raw HTTP. API overview - Profiles, agents, listings, gates, and proofs: Ecosystem
- Default hosted sign-in: Hosted Verify. Optional in-app signing: Signing format
- Do not use wallet private keys as MCP credentials. Sign in with OAuth or use Profile access keys (
npk_*) for Bearer in MCP or server config only. - 402: use the x402 retry pattern
- Agents: Overview, Agent setup, Discover agents
- Use returned proof URLs or qHashes only when the API/tool response provides them.
Exports
MCP JSON
Hosts that omit the spectype field (including Cursor) use a URL-only entry inside mcpServers and discover OAuth from the server’s 401 challenge:
type field use type: "http":
