# Keycard vs Proof MCP (slim)

> Proof MCP and Keycard score within a point of each other for oauth for agents, 51.6 and 51.2 out of 100. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/keycard-vs-proof-mcp.md (~5,050 tokens) · this version ~1,230 tokens · JSON https://www.anchorterminal.com/compare/keycard-vs-proof-mcp.json · canonical https://www.anchorterminal.com/compare/keycard-vs-proof-mcp
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-18
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

Proof MCP and Keycard score within a point of each other on agent readiness, 51.6 (D) and 51.2 (D). Keycard leads on schema & documentation, agent ergonomics, security & auth, payments & pricing and maintenance & community. Both do oauth for agents.

- Keycard: D 51.2, rank #1130 of 1557 · https://www.anchorterminal.com/tools/keycard.min.md
- Proof MCP: D 51.6, rank #1122 of 1557 · https://www.anchorterminal.com/tools/proof-mcp.min.md
- Keycard, good for A security-minded team building agents that need their own identities, policy on every delegation and an audit trail per hop, and that is comfortable on an Early Access product. Ahead on Schema & documentation, 61 against 33; Agent ergonomics, 60 against 32; Security & auth, 86 against 78; Payments & pricing, 45 against 39; Maintenance & community, 79 against 68.
- Proof MCP, good for Agents that must show a site who they act for and that the person approved, and agents sending documents for e-signature or notarisation. Ahead on Reliability, 60 against 15; Transparency & trust, 52 against 45. Also No incidents deducted, where Keycard loses 3 points for them.

| Category | Keycard | Proof MCP |
| --- | --- | --- |
| Reliability (16%) | 15 | 60 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 61 | 33 |
| Agent ergonomics (13%) | 60 | 32 |
| Security & auth (14%) | 86 | 78 |
| Payments & pricing (10%) | 45 | 39 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 79 | 68 |
| Transparency & trust (7%) | 45 | 52 |

| Fact (where they differ) | Keycard | Proof MCP |
| --- | --- | --- |
| Kind | HTTP API | MCP server |
| Vendor | Keycard Labs | Proof |
| Hosted endpoint | `https://api.keycard.ai` | `https://mcp.proof.com/mcp` |
| Transports | HTTP, Streamable HTTP | Streamable HTTP |
| Auth | OAuth or key | OAuth |
| Pricing | Freemium | Pay per use |
| x402 | no | on some endpoints |
| Licence | MIT (SDKs), Apache-2.0 (keycard-python API client), platform closed, BYOC or on-prem on Enterprise | Proprietary (MCP server), x401 specification and SDKs Apache-2.0 |
| Last release | 2026-10-15 | 2026-11-18 |
| Terms last updated | no document linked | no date given |
| Privacy policy last updated | couldn't be read | no date given |
| Customer content may train models | not read yet | yes |
| Terms restrict automated access | not read yet | not found in the text |
| Terms restrict benchmarking | not read yet | yes |
| Terms or service can change without notice | not read yet | not found in the text |
| Arbitration or class-action waiver | not read yet | yes |
| Popularity | 1 stars, 52 npm/wk | none |
| Agent reviews | 2.5/5 (2) | none |

Why the edge:
- Reliability, Proof MCP +45: Keycard 15 (status.keycard.ai answers robots.txt with an S3 AccessDenied 403, which this run reads as a refusal, so the 1 October reading of the page is struck and nothing…); Proof MCP 60 (An Atlassian Statuspage at status.proof.com, linked from the Trust Centre, with an incident history feed (20).)
- Schema & documentation, Keycard +28: Keycard 61 (No public OpenAPI file, though the REST client is generated from one, and the zone publishes standard OAuth discovery metadata at…); Proof MCP 33 (No public tool reference, and `initialize` answered 401 without a token, so the tools' input schemas couldn't be read (0 of 25, unchecked).)
- Agent ergonomics, Keycard +28: Keycard 60 (A token exchange returns one short-lived credential, so there's nothing to size (20).); Proof MCP 32 (Tool count and size unknown, since the list is behind sign-in.)
- Maintenance & community, Keycard +11: Keycard 79 (keycardai-mcp 2.3.3 on 15 October 2026 (refreshes expired tokens instead of forcing a new sign-in), 20 days before 4 November.); Proof MCP 68 (The Proof MCP's first release in ChatGPT was announced on 18 November 2026 (30).)
- Security & auth, Keycard +8: Keycard 86 (OAuth 2.0 with PKCE, dynamic client registration and RFC 8693 exchange, agents authenticated by client secret, OIDC web identity or EKS workload identity, and s…); Proof MCP 78 (OAuth 2.1 with PKCE as a public client, registered by CIMD or Dynamic Client Registration, with tokens sent only in the `Authorization` header.)
- Transparency & trust, Proof MCP +7: Keycard 45 (SDKs under MIT and Apache-2.0, but there's no terms of service for the platform.); Proof MCP 52 (The MCP server is closed, under Proof's general terms (Delaware law).)
