Mcp MCP Server

Proofable MCP

Hosted MCP server for AI agent identity, permissions, verification, and reusable proof. Connect an AI client, sign in with OAuth, and check what an agent may do before it acts.

Connect

Two paths, one endpoint, one profile:

• Connect (OAuth): add the hosted server, click Connect, sign in in the browser. Best for interactive clients.
• Access key: best for servers, CI, and headless agents. Send a Profile access key as a Bearer token.

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 Cursor, Claude Code, Codex, or VS Code:

npx -y @proofable/sdk setup

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

This repository is also a plugin marketplace. In Claude Code:

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

The plugin registers the server and ships the skills in plugins/proofable-mcp. Use either the plugin or a manual entry, not both.

What it does

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 Profile access 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.

Marketplace gateways (such as Smithery) use OAuth when their client supports it; where a gateway cannot run browser sign-in it forwards the key as x-proofable-access-key, which the server maps to the same Bearer principal. smithery.config.json publishes that optional configuration.

This package

@proofable/mcp publishes the registry manifest (server.json), the public skills, and the Smithery release metadata (smithery.config.json). It does not run a local server.

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

The standards server card (server.json, /.well-known/mcp/server-card.json) stays OAuth-first; gateway-specific config schemas belong to the marketplace release metadata, not in the card.

Smithery release metadata

smithery.config.json is the optional Smithery configuration schema for the hosted endpoint: one optional profileAccessKey field forwarded as x-proofable-access-key. With no key configured, Smithery clients get the standard OAuth challenge and click Connect. To (re)publish with the config schema:

smithery mcp publish "https://mcp.proofable.me/mcp" -n @proofable/mcp --config-schema "$(cat smithery.config.json)"

npm run validate:smithery guards the file's contract (optional fields only, reserved headers, 1KB limit).

Support

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

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