# Proof MCP vs Vercel Connect (slim)

> Vercel Connect scores 73.3 (BB) to Proof MCP's 51.6 (D) for auth consent. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/proof-mcp-vs-vercel-connect.md (~5,300 tokens) · this version ~1,130 tokens · JSON https://www.anchorterminal.com/compare/proof-mcp-vs-vercel-connect.json · canonical https://www.anchorterminal.com/compare/proof-mcp-vs-vercel-connect
- 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)

Vercel Connect scores 73.3 (BB) on agent readiness against Proof MCP's 51.6 (D), and leads in every scored category. Both do auth consent.

- Proof MCP: D 51.6, rank #1122 of 1557 · https://www.anchorterminal.com/tools/proof-mcp.min.md
- Vercel Connect: BB 73.3, rank #181 of 1557 · https://www.anchorterminal.com/tools/vercel-connect.min.md
- 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. Also No incidents deducted, where Vercel Connect loses 3 points for them.
- Vercel Connect, good for Teams already deploying on Vercel whose agents need user or app tokens for Slack, GitHub, Microsoft, Linear, Snowflake or an MCP server without storing provider secrets, and providers behind IP allowlists through Secure Compute. Ahead on Reliability, 73 against 60; Schema & documentation, 84 against 33; Agent ergonomics, 75 against 32; Security & auth, 83 against 78; Payments & pricing, 60 against 39; Maintenance & community, 81 against 68; Transparency & trust, 77 against 52. Also Agent-ready, a grade of BB or better.

| Category | Proof MCP | Vercel Connect |
| --- | --- | --- |
| Reliability (16%) | 60 | 73 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 33 | 84 |
| Agent ergonomics (13%) | 32 | 75 |
| Security & auth (14%) | 78 | 83 |
| Payments & pricing (10%) | 39 | 60 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 68 | 81 |
| Transparency & trust (7%) | 52 | 77 |

| Fact (where they differ) | Proof MCP | Vercel Connect |
| --- | --- | --- |
| Kind | MCP server | HTTP API |
| Vendor | Proof | Vercel |
| Hosted endpoint | `https://mcp.proof.com/mcp` | `https://api.vercel.com` |
| Transports | Streamable HTTP | HTTP |
| Auth | OAuth | OAuth or key |
| Pricing | Pay per use | Freemium |
| x402 | on some endpoints | no |
| Licence | Proprietary (MCP server), x401 specification and SDKs Apache-2.0 | Proprietary service under Vercel's Terms of Service and the Vercel Connect product terms. The `@vercel/connect` SDK and the Vercel CLI are Apache-2.0 |
| Last release | 2026-11-18 | 2026-10-31 |
| Terms last updated | no date given | 2026-06-01 |
| Privacy policy last updated | no date given | 2026-06-01 |
| Customer content may train models | yes | yes, with an opt-out |
| Terms restrict benchmarking | yes | not found in the text |
| Popularity | none | 16k stars, 738k npm/wk |
| Agent reviews | none | 3.5/5 (4) |

Why the edge:
- Schema & documentation, Vercel Connect +51: 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).); Vercel Connect 84 (Vercel's public OpenAPI 3.0.3 document, re-read on 1 November 2026, has 14 paths under `/v1/connect` and `/v2/connect`, the token and authorise calls…)
- Agent ergonomics, Vercel Connect +43: Proof MCP 32 (Tool count and size unknown, since the list is behind sign-in.); Vercel Connect 75 (A token call returns one token with its expiry and identifiers, so there is little to size (22).)
- Transparency & trust, Vercel Connect +25: Proof MCP 52 (The MCP server is closed, under Proof's general terms (Delaware law).); Vercel Connect 77 (Closed service under the Terms of Service last updated 19 October 2026, with the Connect product terms now in Vercel's Service Terms (last updated 15 October 20…)
- Payments & pricing, Vercel Connect +21: Proof MCP 39 (x402 (v2, exact scheme, USDC on Base) only on the x401 signatures endpoint, which a verifier with no card on file pays per presentation.); Vercel Connect 60 (No x402, MPP or L402 (0).)
- Reliability, Vercel Connect +13: Proof MCP 60 (An Atlassian Statuspage at status.proof.com, linked from the Trust Centre, with an incident history feed (20).); Vercel Connect 73 (Graded on the hosted lines.)
- Maintenance & community, Vercel Connect +13: Proof MCP 68 (The Proof MCP's first release in ChatGPT was announced on 18 November 2026 (30).); Vercel Connect 81 (`@vercel/connect` 2.7.0 was published on 31 October 2026, per npm's search API (30).)
