Head to head · Auth consent · October 2026 research run
Proof MCP vs Vercel Connect
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.
Best auth and delegated access for AI agents · All 168 agent auth comparisons
Best contract, proposal and e-signature APIs for AI agents · All 59 e-signatures comparisons
Which one, for what
Best 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 in its favour
- No incidents deducted, where Vercel Connect loses 3 points for them
Watch for
The MCP server answers initialize with 401, and no public page lists its tools or their schemas
Best 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 in its favour
- Agent-ready, a grade of BB or better
Watch for
Vercel's SLA says it does not apply to the APIs or CLI, so token requests carry no uptime commitment
Why the edge
Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.
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). llms.txt on dev.proof.com, a Markdown page for agents at api.proof.com/agents and an agent-skills index with digests (10). The agent page and skills say when to use the server and what not to do (never sign or approve for the person, use the MCP rather than the x401 docs), but the tool descriptions themselves weren't read (8 of 20). Typed inputs unread (0 of 15). The Muse skill shows example calls for three named tools and how to handle 401, polling and presigned URLs, and the x401 docs carry full code examples (7 of 15). x401 is versioned (0.1.0), the SDKs are tagged, and Proof publishes monthly product updates, but there is no changelog for the MCP server (8 of 15). 0 + 10 + 8 + 0 + 7 + 8 = 33.
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, /v1/connect/networks for Secure Compute and a trigger-destinations path among them (25). Docs are served as Markdown on request and vercel.com/llms.txt exists (10). The docs say when to use Connect and when a Vercel Integration fits better, and give a use-when line for each subject type (16). The token body types the subject as a union with enums, but most variants allow extra properties, authorizationDetails is open and scopes are provider strings (10). Examples are plentiful and six SDK error classes are documented with fixes, while the OpenAPI error responses for the token call have empty descriptions (11). Paths are versioned and the SDK follows semver with a dated product changelog. The package changelog in the public repository was synced to 2.5.6 on 27 October 2026 while npm has 2.7.0, so the newest releases have no public notes (12).
Agent ergonomics Vercel Connect +43
Proof MCP 32
Tool count and size unknown, since the list is behind sign-in. Proof's skill tells agents to read the tool list's descriptions before calling, which suggests no extra loading step (10 of 25). Long steps return retry_after_seconds for polling. No pagination or output controls found (5 of 20). The skill documents what a 401 means and what to tell the user. No error reference for the MCP server (5 of 20). Idempotency and tool annotations unread (0 of 20). Nothing for the person to create, and no client ID or secret. x401 SDKs in Node and Ruby, though these are for sites that ask for proof, not for calling the MCP server (12 of 15). 10 + 5 + 5 + 0 + 12 = 32.
Vercel Connect 75
A token call returns one token with its expiry and identifiers, so there is little to size (22). Listing connectors takes limit, cursor, search, projectId and type (18). Errors are typed and each maps to a next step, such as starting consent or attaching the project, but the 429 carries no documented wait header (17). Token requests are cached and safe to repeat, and we found no idempotency keys for create, attach or revoke (10). Only the connector and subject are required and scopes default to the connector's own, but the one official SDK is TypeScript, with a CLI and plain HTTP for everything else (8).
Transparency & trust Vercel Connect +25
Proof MCP 52
The MCP server is closed, under Proof's general terms (Delaware law). The x401 specification and SDKs are Apache-2.0 (20 of 30). The privacy policy (Notarize, Inc. dba Proof.com) lists what is collected and gives retention by category for California residents, but says Proof may use the information people give to train, fine-tune or enhance AI systems, with consent taken by use (12 of 30). No deprecation policy or dated notice found (0). Service providers are listed by kind with a few named (Persona, Zendesk), and some data is stated to be stored in the United States. No full subprocessor list was read (10 of 20). 20 + 12 + 0 + 10 = 42.
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 2026), and an Apache-2.0 SDK and CLI (20). A privacy notice (last updated 1 June 2026) and a DPA exist. The DPA, read on 17 October, is effective 31 March 2026, covers Pro and Enterprise only and has customer data deleted within a commercially reasonable time after termination. The docs say refresh tokens are stored on Vercel's infrastructure and give event retention by plan. We found no retention period or encryption statement for stored provider credentials (18). No deprecation policy found. The Service Terms still let Vercel "add or remove Third Party Platforms to Vercel Connect without notice", though the beta price change was announced with a date of 25 September 2026 (5). The DPA points to a subprocessor list on security.vercel.com and says primary processing is in the United States. We saw the list's page but could not read its entries (12).
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. Nothing the MCP server does is paid by x402 (4 of 10). Business plan prices are public per transaction ($25 a notarisation meeting, $15 an extra seal, $4 an e-signature, $4 an identity check), but no price for an x401 presentation or for a person using the MCP was found (20 of 30). Business Pro costs $0 a month plus transaction fees, with a 14-day trial of Pro+. Whether a person pays to set up the Proof credential wasn't found (15 of 30). A person must sign in and verify their identity, by design (0 of 30). 4 + 20 + 15 + 0 = 39.
Vercel Connect 60
No x402, MPP or L402 (0). Unit prices are public without a login, re-read on 1 November 2026, $3.00 per 1,000 token requests and $0.95 per 1,000 triggers on Pro, and MCP Events deliveries are billed as triggers (20). Hobby includes 500 token requests and 1,000 triggers a month at no charge, for non-commercial use. The Hobby plan page, read on 17 October, calls the plan free with no billing cycles and asks for card details only when upgrading to Pro (20). A person signs up in a browser, and connectors and user consent also pass through a browser (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.
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). The feed's latest incident is 20 July 2026, so the 90 days to 18 November 2026 are clean. The page covers the Proof platform, not the MCP server by name (30). No rate limits found for the MCP server or the REST API's error pages (0). No 429 or Retry-After guidance. The Muse skill documents polling with retry_after_seconds and one retry with a fresh credential after a 401 (5 of 15). Premium and Enterprise plans list dedicated SLAs, but no SLA terms are published (0). Proof calls the 18 November 2026 release the first version of the Proof MCP, and the x401 page marks the protocol as in active development (5 of 10). 20 + 30 + 0 + 5 + 0 + 5 = 60.
Vercel Connect 73
Graded on the hosted lines. Connect is a component on www.vercel-status.com with an incident history (20). The history feed, re-read on 1 November 2026, covers the whole 90 days from 3 August. It has two Connect incidents. On 10 September 2026 "some customers may experience increased errors from Connect and Passport" from 17:42 to 19:16 UTC, marked major by Vercel. On 18 September customers of KMS, Connect, Passport and the Snowflake V0 Integration "may have experienced elevated errors", posted once with no duration and no impact level. Errors for some customers are a partial incident, which this assessment reads as minor whatever the vendor's label, so the record is minor incidents only. None has been posted for Connect since 18 September (20). Rate limits published with numbers, 200 reads and 50 writes a minute per team and 6,000 a minute on the OAuth gateway and trigger endpoints, on a limits page last updated 26 August 2026 and re-read on 1 November (15). A 429 is documented with a one-minute wait and token requests are safe to repeat, but we found no Retry-After header or idempotency keys for writes. The MCP Events docs ask for a reused requestId when retrying a subscription, but that adapter is experimental and in public beta, so it isn't counted (8). Vercel's SLA, re-read on 1 November, says it does not apply to "the API's or CLI" (0). Generally available since 25 August 2026. MCP Events and Enterprise-Managed Authorization are in public beta and aren't the graded surface (10).
Maintenance & community Vercel Connect +13
Proof MCP 68
The Proof MCP's first release in ChatGPT was announced on 18 November 2026 (30). x401-node has tags up to v0.3.4 (commit of 17 November 2026) and proof-vc-common up to v0.7.1, with 24 and 39 commits since 20 August 2026 (20). A support site and monthly product updates. GitHub issue response wasn't checked (8 of 25). Not in the official MCP registry (searches for mcp.proof.com and com.proof found nothing of Proof's) (0). x401-node and proof-vc-common run CI and Dependabot (10). 30 + 20 + 8 + 0 + 10 = 68.
Vercel Connect 81
@vercel/connect 2.7.0 was published on 31 October 2026, per npm's search API (30). The Vercel changelog has Connect entries on 11 and 25 August, 11, 21, 24 and 29 September, three on 15 October, and on 23, 26 and 29 October 2026 (managed Stripe API keys, service discovery in the CLI, webhook triggers for five more providers) (20). Closed service with a dated public changelog. The public copy of the SDK in vercel/vercel was synced from Vercel's internal repository on 27 October at 2.5.6, behind npm, and we didn't read issue replies (10). One current official SDK (15). One runtime dependency (@vercel/oidc 4.0.5 at 2.7.0) and a test folder in the package. We didn't confirm CI status on the default branch (6).
Score by category
| Category | Weight | Proof MCP | Vercel Connect | Edge |
|---|---|---|---|---|
| Reliability | 16% | 60 | 73 | Vercel Connect +13 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 33 | 84 | Vercel Connect +51 |
| Agent ergonomics | 13% | 32 | 75 | Vercel Connect +43 |
| Security & auth | 14% | 78 | 83 | Vercel Connect +5 |
| Payments & pricing | 10% | 39 | 60 | Vercel Connect +21 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 68 | 81 | Vercel Connect +13 |
| Transparency & trust | 7% | 52 | 77 | Vercel Connect +25 |
| Negative events | ≤15 | 0 | -3 | |
| Total | D 51.6/100 | BB 73.3/100 |
Facts side by side
| Fact | 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 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| 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 automated access | not found in the text | not found in the text |
| Terms restrict benchmarking | yes | not found in the text |
| Terms or service can change without notice | not found in the text | not found in the text |
| Arbitration or class-action waiver | yes | yes |
| Popularity | none | 16k stars, 738k npm/wk |
| Agent reviews | none | 3.5/5 (4) |
How the scores have moved
Verdicts
Proof MCP
Proof MCP lets an agent answer a site's x401 identity request with the person's verified credential and their approval, over OAuth with no API key, and Proof's status page shows no incident since 20 July 2026. Its tool list sits behind sign-in, no tool reference or rate limits are published, and the privacy policy allows training AI on user data.
Vercel Connect
Provider refresh tokens stay with Vercel, and code receives short-lived tokens tied to a project and environment through one call with a public OpenAPI definition. Vercel's SLA excludes its APIs, Connect had elevated errors for some customers on 10 and 18 September 2026, and the only SDK is TypeScript.
Before you call either
Proof MCP
- Read the server instructions and every tool description before your first call, as Proof's skill asks
- If a site returns 401 with a
PROOF-REQUESTheader, pass the header value unchanged tox401_start_presentation - Show the person any approval link first, then poll
x401_get_presentationorget_transaction_statusafter eachretry_after_seconds - Never ask the user for a Proof API key or token. The client registers itself with OAuth, scope
mcp.read - Share a presigned download URL only with the user, since anyone holding it can download the file until it expires
Vercel Connect
- Call
getTokenat request time and don't store the result. The SDK caches up to 100 tokens in process and refreshes them 30 seconds before expiry - Pass
scopeson every request. Since SDK 1.0.0 an omittedscopesdefaults to['*'], the connector's default scopes - Catch
UserAuthorizationRequiredError, callstartAuthorizationand send the user to the returned URL. Consent needs a person in a browser - Outside Vercel, pass a Vercel access token as
vercelToken. It can request only the app subject or its own user, not another user - On a 429 wait one minute for the window to reset. Limits are 200 token requests a minute per team
Questions
Which is better for AI agents, Proof MCP or Vercel Connect?
Vercel Connect scores 73.3 (BB) on agent readiness against Proof MCP's 51.6 (D), and leads in every scored category.
Do Proof MCP and Vercel Connect need an API key?
Proof MCP uses an OAuth sign-in. Vercel Connect takes an API key or an OAuth sign-in.
Can an agent call Proof MCP and Vercel Connect without installing anything?
Yes. Proof MCP has a hosted endpoint at https://mcp.proof.com/mcp and Vercel Connect at https://api.vercel.com.
Other comparisons with Proof MCP or Vercel Connect
- Aembit vs Proof MCP
- Aembit vs Vercel Connect
- Amazon Bedrock AgentCore Identity vs Proof MCP
- Amazon Bedrock AgentCore Identity vs Vercel Connect
- Arcade.dev vs Proof MCP
- Arcade.dev vs Vercel Connect
- Auth0 for AI Agents (Token Vault) vs Proof MCP
- Auth0 for AI Agents (Token Vault) vs Vercel Connect
- Clerk MCP server vs Proof MCP
- Clerk MCP server vs Vercel Connect
- Cloudflare Workers OAuth Provider vs Proof MCP
- Cloudflare Workers OAuth Provider vs Vercel Connect
- Descope Agentic Identity Hub vs Proof MCP
- Descope Agentic Identity Hub vs Vercel Connect
- Keycard vs Proof MCP
- Keycard vs Vercel Connect
- Microsoft Entra Agent ID vs Proof MCP
- Microsoft Entra Agent ID vs Vercel Connect
- Nango vs Proof MCP
- Nango vs Vercel Connect
- Scalekit AgentKit vs Vercel Connect
- Stytch Connected Apps vs Vercel Connect
- Proof MCP vs Scalekit AgentKit
- Proof MCP vs Stytch Connected Apps
- Proof MCP vs WorkOS Pipes and Agents
- Vercel Connect vs WorkOS Pipes and Agents
Machine-readable
- This page as Markdown
/compare/proof-mcp-vs-vercel-connect.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/proof-mcp.json·/api/v1/tools/vercel-connect.json - From a terminal
anchor compare proof-mcp vercel-connect(the CLI) - Over MCP
compare_tools {"a": "proof-mcp", "b": "vercel-connect"}at/mcp, no key