Skip to content
Conduit

mcp server

mcp

Context and control for any AI. Agent identity, scoped access, and proof across tools.

proofable/mcpcommunitylistedunreviewed

Set up

Hosted by its author. Add the URL to your agent — nothing to install.

~/Library/Application Support/Claude/claude_desktop_config.json
Settings → Connectors → Add custom connector

Name: mcp
URL:  https://mcp.proofable.me/mcp

same format Cursor, GitHub Copilot CLI, Junie, JetBrains AI Assistant, Augment (Auggie CLI), Factory Droid, Kiro, Devin CLI +12

Values in angle brackets are placeholders. Restart Claude Desktop after editing its config.Claude Desktop docs

README

synced Oct 17, 2026

Proofable MCP

npm License

Identity, scoped access, and proof for AI agents.

Connect Proofable once so agents can use your current profile, proofs, permissions, and protected tools across Cursor, Claude, Codex, VS Code, ChatGPT, and other MCP clients.

Start

Open Set up Proofable, choose your client, and finish sign-in. Then ask:

Show my Proofable profile and the proofs I can reuse.

For a specific requirement:

Check whether I already have the proof needed for this task. Reuse it if it qualifies; otherwise show me the next step.

Connect

Add the hosted endpoint to any MCP client:

https://mcp.proofable.me/mcp

Or use a standard MCP configuration:

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

The optional installer writes the same connection for supported clients:

npx -y @proofable/sdk setup

Claude Code can install the server and workflow skills together:

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

Install one Proofable connection per client. A marketplace plugin and a manual entry together create a duplicate connection.

What agents can do

OutcomeTools
Load the signed-in profile and current contextproofable_context
Find supported checks and their required inputsproofable_verifiers_catalog
Check whether a qualifying proof already existsproofable_proofs_check
Reuse a current proof or get the next verification stepproofable_verify_or_guide
Create or refresh a proofproofable_verify
Prepare and submit a check needing another signerproofable_verify_prepare, proofable_verify_submit
Find and read proofsproofable_proofs_get
Update proof metadata or add feedbackproofable_proofs_update
Check, create, and load agent permissionsproofable_agent_link, proofable_agent_create, proofable_agent_mount
Save, list, and revoke encrypted secretsproofable_secret_create, proofable_secret_list, proofable_secret_revoke

Call proofable_context once after connecting. Proofable then reuses current proofs before starting another verification and returns Passed, Action needed, or Blocked.

See the MCP tool reference for inputs and result shapes.

Servers and automation

Create an access key under Account → Access keys, store it as PROOFABLE_ACCESS_KEY, and send it as a Bearer token. Keep access keys out of source code, browser bundles, and chat.

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

Build with Proofable

Use the Proofable SDK for application code, verification gates, and the CLI. @proofable/mcp publishes the MCP registry manifest and public workflow skills; the hosted server runs at mcp.proofable.me.

To see what your agent's permission stops, run the prompt injection test: it hides AgentDojo attacks in a note your agent reads and grades every run from its signed receipt.

Support

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

↑↓ navigate openesc close