Proof Holdings vs ThoughtProof
Proof Holdings is an MCP server published by proof.holdings. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). ThoughtProof is an MCP server published by ThoughtProof. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-29. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |   Proof Holdings |  ThoughtProof |
|---|---|---|
| Official MCP Registry | Listed Version: 1.7.1 Downloads/month (npm): 739 Downloads/week (npm): 422 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 0.3.2 Downloads/month (npm): 232 Downloads/week (npm): 25 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
| npm registry (MCP servers) | Listed Version: 1.7.1 Downloads/month (npm): 739 Downloads/week (npm): 422 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Not listed |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | Proof Holdings | ThoughtProof |
|---|---|---|
| Marketplaces that list it (differs) | 2 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 0 (worse) | 1 (better) |
| Forks (GitHub) | 0 | 0 |
| Last release (differs) | 2026-10-26 | Not published |
| Where it runs (differs) | Remote server or your machine | On your machine (thoughtproof-mcp) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 2, secrets among them: 1 | 3, secrets among them: 3 |
| Licence | MIT | MIT |
| Repository (differs) | github.com/proofholdings/mcp-server | github.com/thoughtproof/thoughtproof-mcp |
| Changes in the last 7 days (differs) | 3 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 17 h ago | no remote endpoint we check |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
Proof Holdings
One API, all things verified — control, delegation, human approval, anti-impersonation.
ThoughtProof
Pre-action gate: verify before pay/trade/write/deploy. execute=true only on ALLOW.
How to run each
Proof Holdings As a remote MCP server
claude mcp add --transport http proof-holdings https://api.proof.holdings/mcpRequires: PROOF_API_KEY (secret)
ThoughtProof As a local MCP server: npm package
claude mcp add --env "DQL_API_KEY=<YOUR_DQL_API_KEY>" --env "SENTINEL_API_KEY=<YOUR_SENTINEL_API_KEY>" --env "THOUGHTPROOF_API_KEY=<YOUR_THOUGHTPROOF_API_KEY>" --transport stdio thoughtproof-mcp -- npx -y thoughtproof-mcpRequires: DQL_API_KEY (secret), SENTINEL_API_KEY (secret), THOUGHTPROOF_API_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Proof Holdings has a remote endpoint we check. How we check endpoints
Tools each declares
Neither the marketplaces of ThoughtProof nor its endpoint list any tools, so we do not compare tools.
Settings each asks for
Only Proof Holdings asks for
PROOF_API_KEY (secret)PROOF_BASE_URL
Only ThoughtProof asks for
DQL_API_KEY (secret)SENTINEL_API_KEY (secret)THOUGHTPROOF_API_KEY (secret)
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: Proof Holdings · What it can do: ThoughtProof · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.