Skip to main content
MCP server CX Codex

Proof Holdings — Claude Code MCP server: 167 verification tools

An MCP server for the proof.holdings API. Agents create verifications, confirm domains and ask a person to approve. Run it over HTTP or locally with npx.

Install into Claude Code · Platform CLI: remote server All methods and platforms ↓
claude mcp add --transport http mcp-server https://api.proof.holdings/mcp
Open on GitHub

What Proof Holdings does

The server hands your agent 167 tools from the proof.holdings API. They cover verifications and requests, domains and DNS, account and billing, human approvals, circles of trusted contacts, public profiles, templates and webhooks. An agent can open a verification challenge and poll until it finishes, attach a domain, mint a scoped API key, or send someone an approval request and read back the answer.

There are two ways in. The hosted one needs no install: the same tool set is served at https://api.proof.holdings/mcp, so you add that URL as a remote MCP server and sign in through the browser the first time a tool wants an account. The local one is the @proof-holdings/mcp-server package, a stdio server started with npx -y @proof-holdings/mcp-server.

A key is optional. With no PROOF_API_KEY the server still starts, in public mode: account bootstrap, login, and proof and delegation verification work, while everything else returns api_key_required. Get a key from the dashboard, or run npx @proof-holdings/mcp-server login, which confirms over a second channel and stores the key in ~/.proof-holdings/credentials. That command needs an interactive terminal and an https:// API address. Pinning a client to 1.0.0 costs you the delegation tools and the keyless mode — upgrade the client or switch to the hosted server.

What it helps with

  • open a verification challenge and poll until it completes
  • prove control of a domain with a DNS record
  • get a person to approve an agent action before it runs
  • mint an API key with limited scopes
  • verify a proof or delegation without a key

Example prompts for the agent

  • Create a verification for this number and wait for it to finish
  • Add example.com and verify it through DNS
  • Send an approval request and poll for the result

How to install Proof Holdings

1Platform CLI: remote server

claude mcp add --transport http mcp-server https://api.proof.holdings/mcp

2Platform CLI

claude mcp add --env PROOF_API_KEY=<PROOF_API_KEY> --env PROOF_BASE_URL=<PROOF_BASE_URL> --transport stdio proof-holdings -- npx -y @proof-holdings/mcp-server

Replace <…> with your own values

Step by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more

Questions about Proof Holdings

How do I install Proof Holdings in Claude Code?

Hosted: claude mcp add --transport http proof-holdings https://api.proof.holdings/mcp. Local: `claude mcp add --env PROOF_API_KEY=<PROOF_API_KEY> --env PROOF_BASE_URL=<PROOF_BASE_URL> --transport stdio proof-holdings -- npx -y @proof-holdings/mcp-server`.

What does Proof Holdings do?

It exposes 167 proof.holdings API tools to an agent: verifications, domains and DNS, account and billing, human approvals, circles, public profiles, templates and webhooks.

Do I need an API key to run the server?

No. Without PROOF_API_KEY it starts in public mode, where account bootstrap, login and proof verification work and the rest answer api_key_required.

Similar MCP servers

All MCP servers for Agent setup: memory, context, orchestration →

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor