Proofable MCP

Give AI access without giving up control.

Add Proofable to any app, chat, or agent that speaks MCP.

https://mcp.proofable.me/mcp

https://mcp.proofable.me/mcp is the endpoint: it answers the MCP handshake with a 401 challenge, so Cursor, VS Code, Claude Code, and Codex start their own OAuth (DCR + PKCE). The same URL serves server-key Bearer access, so there is one endpoint for every caller.

Install

Set up Proofable has the setup skill and install links for Cursor, VS Code, Claude Code, Codex, and other MCP clients.

Then sign in when your client prompts, and ask:

Show my Proofable profile and current proofs.

Claude Code

In Claude Code, the repository is also a plugin marketplace:

/plugin marketplace add proofable/mcp
/plugin install proofable-mcp@proofable

Use either the plugin or a manual entry, not both. The plugin registers the same endpoint from one .mcp.json — read by both Cursor and Claude Code — and ships the skills in plugins/proofable-mcp. Codex loads the skills only; register its server with npx -y @proofable/sdk setup --client codex.

Connect

Two paths, one product, one profile:

• Interactive clients (OAuth): add https://mcp.proofable.me/mcp, finish the sign-in your client opens. Best for Cursor, VS Code, Claude Code, Codex, and other interactive hosts.
• Server key: best for servers, CI, and headless agents. Send it as a Bearer token to https://mcp.proofable.me/mcp.

Any MCP client:

{
  "mcpServers": {
    "proofable": { "type": "http", "url": "https://mcp.proofable.me/mcp" }
  }
}

Servers and automation:

{
  "mcpServers": {
    "proofable": {
      "type": "http",
      "url": "https://mcp.proofable.me/mcp",
      "headers": { "Authorization": "Bearer ${PROOFABLE_ACCESS_KEY}" }
    }
  }
}

Create a key at Access keys, then export PROOFABLE_ACCESS_KEY=npk_... in that environment.

Or let the installer write the same entry for any tool:

npx -y @proofable/sdk setup

Then ask: "Show my Proofable profile and current proofs."

What it does

Job	Tools
Load the signed-in profile and workflow	proofable_context (call first)
Check, reuse, or create proof	proofable_proofs_check, proofable_verify_or_guide, proofable_verify, proofable_proofs_get, proofable_proofs_update, proofable_verifiers_catalog
Give agents an owner and permissions	proofable_agent_link, proofable_agent_create, proofable_agent_mount
Store secrets without exposing them	proofable_secret_create, proofable_secret_list, proofable_secret_revoke

Full reference: docs.proofable.me/mcp/tools.

Authentication

Two paths, one session model: interactive clients Connect with OAuth (PKCE, silent refresh); servers and CI send a server key (npk_...) as a Bearer token from PROOFABLE_ACCESS_KEY. Same endpoint, same Proofable profile, same tools and policy. Never put a key in client config or chat when Connect works. See Auth.

This package

@proofable/mcp publishes the registry manifest (server.json) and the public skills. It does not run a local server. To build an app against Proofable, start from github.com/proofable/sdk.

import { serverManifest } from '@proofable/mcp';

The standards server card (server.json, /.well-known/mcp/server-card.json) stays OAuth-first.

Support

• Docs: docs.proofable.me/mcp/overview
• Issues: github.com/proofable/mcp/issues
• Security: SECURITY.md
• Contributing: CONTRIBUTING.md

Apache-2.0. Proofable is published by NEUS Network, Inc.