https://mcp.proofable.me/mcp
Use a marketplace plugin or registry listing when the host offers one. npx -y -p @proofable/sdk proofable setup writes the same URL from a terminal.
Then ask the new client to load what you already built:
Show my Proofable profile, agents, approved tools, and current proofs.Proofable answers Passed, Action needed, or Blocked.
Do the work
Callproofable_context. Create or import an agent, or publish a listing.
Create or import an agent on my Proofable profile. Use generate if I need a separate spend account. Set spend and action limits. Then confirm it is ready.Open Connections on proofable.me to link apps. Connections To sell: set payouts, then publish a listing. Full steps: Connect Proofable. Chat now. Pro jobs run in the background or on a schedule. Cursor, Claude Code, Codex, Hermes, and Grok can connect to this endpoint. Private cloud. Point the runtime at the same URL. Private Cloud Trust Harness. Same install block: Connect Proofable.
Tools
Callproofable_context once. Reuse a current proof before you create another.
Field names and per-tool pages: MCP tools.
Privacy
Proofable returns the result and the proof. It does not return the private data used to complete it. Proofs are private by default. The client or runtime must enforce that result. What you can carry across supported clients:- Your profile, agents, and current permissions
- Approved tools, skills, and selected context
- Connected apps and custom MCP servers
- On-demand and scheduled jobs
- Completed checks that are still valid
- Proofs another connected product can confirm
- Vault context when you allow it
