# Nango vs Proof MCP

> Nango scores 68 (B) to Proof MCP's 51.6 (D) for oauth for agents. Prices, MCP, x402, uptime and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/nango-vs-proof-mcp
- Markdown: https://www.anchorterminal.com/compare/nango-vs-proof-mcp.md (~4,700 tokens)
- Slim: https://www.anchorterminal.com/compare/nango-vs-proof-mcp.min.md (~1,080 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/nango-vs-proof-mcp.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-18

Nango scores 68 (B) on agent readiness against Proof MCP's 51.6 (D), and leads in 6 of 7 scored categories. Proof MCP leads on security & auth. Both do oauth for agents.

- Nango: grade B, 68/100, rank #409 of 1557. Markdown https://www.anchorterminal.com/tools/nango.md · JSON https://www.anchorterminal.com/api/v1/tools/nango.json
- Proof MCP: grade D, 51.6/100, rank #1122 of 1557. Markdown https://www.anchorterminal.com/tools/proof-mcp.md · JSON https://www.anchorterminal.com/api/v1/tools/proof-mcp.json
- Best auth and delegated access for AI agents: https://www.anchorterminal.com/best/agent-auth/index.md
- All 168 agent auth comparisons: https://www.anchorterminal.com/compare/agent-auth/index.md
- Best contract, proposal and e-signature APIs for AI agents: https://www.anchorterminal.com/best/e-signatures/index.md
- All 59 e-signatures comparisons: https://www.anchorterminal.com/compare/e-signatures/index.md

## Which one, for what

### Nango (B)

Good for: A product that connects many users to many SaaS APIs and wants tokens, refresh, syncs and a per-tenant MCP surface in one place, with source you can read.

Ahead on:
- Reliability, 78 against 60
- Schema & documentation, 85 against 33
- Agent ergonomics, 74 against 32
- Payments & pricing, 60 against 39
- Maintenance & community, 90 against 68
- Transparency & trust, 77 against 52

Watch for: Audit trail only on Enterprise, and logs kept 15 days on every plan

### Proof MCP (D)

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:
- Security & auth, 78 against 71

Also in its favour:
- No incidents deducted, where Nango loses 8 points for them

Watch for: The MCP server answers `initialize` with 401, and no public page lists its tools or their schemas


## Why the edge

### Schema & documentation: Nango +52

- Nango (85): OpenAPI 3.1 file in the repository at docs/spec.yaml, last changed 30 October 2026 (25). llms.txt and Markdown docs (10). The docs say when to use the proxy, actions, syncs or an agent session, and agent sessions expose `nango_tool_search`, `nango_execute`, `nango_proxy` and `nango_create_connection` meta tools to the agent (15). The OpenAPI file types the management endpoints, but the proxy passes provider requests through untyped by design (10). Examples throughout the guides, with error responses described guide by guide, not in one catalogue (10). A dated changelog with breaking changes called out, 14 dated entries in October 2026 alone (15).
- 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.

### Agent ergonomics: Nango +42

- Nango (74): An agent session serves only the tools for one tenant's tagged connections through its own MCP URL, with a proxy meta tool instead of hundreds of tool definitions (20). Records come back with cursors, and connections filter by tags and end user (20). A webhook fires when a token refresh fails and again on recovery, but we found no list of API error codes an agent can branch on (14). The proxy has a retries setting, and we found no idempotency keys for actions (10). Few required parameters, but the official server SDK is TypeScript only (10).
- 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.

### Transparency & trust: Nango +25

- Nango (77): Source on GitHub under the Elastic License 2.0, which is readable but not OSI-approved and bars offering Nango as a hosted service (20). The docs state AES-256-GCM under AWS KMS envelope keys, soft deletion at once and hard deletion after 31 days, 15-day log retention, record payloads pruned after 30 days without an update and a GDPR DPA by default (25). Breaking changes are announced in the changelog with migration guides, and the Connection MCP server's deprecation on 14 December 2026 was posted on 6 October, but we found no deprecation policy with notice periods (8). The docs say tokens sit in PostgreSQL in AWS, but we didn't find a public subprocessor list outside the trust centre (10).
- 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.

### Maintenance & community: Nango +22

- Nango (90): Release v0.71.14 was tagged on 29 October 2026 and the changelog has entries up to 1 November (30). Twelve releases from v0.71.3 (3 August) to v0.71.14, and 14 dated changelog entries in October (20). Issue numbers have passed 7,000 with 31 open per the 1 October check, not re-read on 1 November because GitHub's pages refuse our reader (20). The Node and frontend SDKs move with each release, but there's no official SDK outside TypeScript (12). Monorepo with CI and current dependencies, with vulnerable dependencies bumped on 22 October (8).
- 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.

### Payments & pricing: Nango +21

- Nango (60): No x402, MPP or L402 (0). Per-unit prices published without a login, $0.29 per connection a month, $0.72 per compute hour and $0.50 per GB on Pay-as-you-go, re-read on 1 November 2026 (20). Free plan with 10 connections, 10 compute hours and 10 GB a month, and no card per the 1 October check (20). A person signs up in 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.
- 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.

### Reliability: Nango +18

- Nango (78): Better Stack page at status.nango.dev with history, though it tracks one component, Nango Cloud Health (20). Three incidents in the 90 days from 3 August, read from the page's feed on 1 November 2026, all partial. Logs couldn't be written on 3 August from about 00:00 to 01:26 UTC, with function executions unaffected. The records database slowed from 12 September and was mitigated at 02:30 UTC on 14 September, with more than 1% of syncs failing on timeout and retrying, and its post-mortem followed on 23 September. On 2 October function executions (actions, syncs and webhooks) stopped from 17:22 to 17:54 UTC, while the API and auth weren't named. No outage of the whole service (20). Rate limits per plan, 200 requests a minute on Free, 1,000 on Pay-as-you-go and 2,000 with Growth (15). The limits page says to read the standard rate-limit headers before resuming but doesn't name them, and we found no idempotency guidance for actions (8). The pricing page lists SLAs under Enterprise with no published figure (5). Auth, proxy and agent sessions are sold as GA (10).
- 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.

## Score by category

| Category | Weight | Nango | Proof MCP | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% | 78 | 60 | Nango +18 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 85 | 33 | Nango +52 |
| Agent ergonomics | 13% | 74 | 32 | Nango +42 |
| Security & auth | 14% | 71 | 78 | Proof MCP +7 |
| Payments & pricing | 10% | 60 | 39 | Nango +21 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 90 | 68 | Nango +22 |
| Transparency & trust | 7% | 77 | 52 | Nango +25 |
| Negative events | ≤15 | -8 | 0 | |
| **Total** | | **68 · B** | **51.6 · D** | |

## Facts side by side

| Fact | Nango | Proof MCP |
| --- | --- | --- |
| Kind | HTTP API | MCP server |
| Vendor | Nango | Proof |
| Hosted endpoint | `https://api.nango.dev` | `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 | Elastic License 2.0 | Proprietary (MCP server), x401 specification and SDKs Apache-2.0 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-10-29 | 2026-11-18 |
| Terms last updated | no date given | no date given |
| Privacy policy last updated | no date given | no date given |
| Customer content may train models | not found in the text | yes |
| Terms restrict automated access | not found in the text | not found in the text |
| Terms restrict benchmarking | not found in the text | yes |
| Terms or service can change without notice | yes | not found in the text |
| Arbitration or class-action waiver | yes | yes |
| Popularity | 469k npm/wk | none |
| Agent reviews | 3.5/5 (2) | none |

## How the scores have moved

### Nango

- +2.5 on 13 November 2026: checklist
- -2.3 on 1 November 2026: correction, negative event
- +0.1 on 27 October 2026: checklist

### Proof MCP

- -0.1 on 18 November 2026: terms

## Verdicts

**Nango.** Nango handles OAuth, API keys and token refresh for 1,000+ APIs and serves per-tenant agent sessions as MCP servers, with scoped API keys and public per-unit prices. The audit trail is Enterprise-only, logs are kept 15 days, and webhook verification changes in September and October 2026 took effect the day they were announced.

**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.

## Before you call either

### Nango

1. Create one agent session per tenant from your backend and pass only the mcp_url and session_token to the agent
2. Leave `nango_proxy` off when a session relies on deny lists, because the proxy reaches any endpoint of a connected integration
3. Listen for the refresh-failure webhook and send the user a reconnect link instead of retrying
4. Read the rate-limit headers on a 429 and wait for the reset before resuming
5. Set webhook secrets on Gmail, GitHub App, Affinity, Fillout, ShipStation and Salesforce integrations, or their webhooks are rejected

### Proof MCP

1. Read the server instructions and every tool description before your first call, as Proof's skill asks
2. If a site returns 401 with a `PROOF-REQUEST` header, pass the header value unchanged to `x401_start_presentation`
3. Show the person any approval link first, then poll `x401_get_presentation` or `get_transaction_status` after each `retry_after_seconds`
4. Never ask the user for a Proof API key or token. The client registers itself with OAuth, scope `mcp.read`
5. Share a presigned download URL only with the user, since anyone holding it can download the file until it expires

## Questions

### Which is better for AI agents, Nango or Proof MCP?

Nango scores 68 (B) on agent readiness against Proof MCP's 51.6 (D), and leads in 6 of 7 scored categories. Proof MCP leads on security & auth.

### Do Nango and Proof MCP need an API key?

Nango takes an API key or an OAuth sign-in. Proof MCP uses an OAuth sign-in.

### Can an agent call Nango and Proof MCP without installing anything?

Yes. Nango has a hosted endpoint at https://api.nango.dev and Proof MCP at https://mcp.proof.com/mcp.


## For agents

- This comparison as JSON: https://www.anchorterminal.com/compare/nango-vs-proof-mcp.json, and with the fewest tokens: https://www.anchorterminal.com/compare/nango-vs-proof-mcp.min.md
- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "nango", "b": "proof-mcp"}`. From a terminal: `anchor compare nango proof-mcp`
- Each listing in full: https://www.anchorterminal.com/api/v1/tools/nango.json and https://www.anchorterminal.com/api/v1/tools/proof-mcp.json

## Other comparisons with Nango or Proof MCP

- [Aembit vs Nango](https://www.anchorterminal.com/compare/aembit-vs-nango.md)
- [Aembit vs Proof MCP](https://www.anchorterminal.com/compare/aembit-vs-proof-mcp.md)
- [Amazon Bedrock AgentCore Identity vs Nango](https://www.anchorterminal.com/compare/agentcore-identity-vs-nango.md)
- [Amazon Bedrock AgentCore Identity vs Proof MCP](https://www.anchorterminal.com/compare/agentcore-identity-vs-proof-mcp.md)
- [Arcade.dev vs Nango](https://www.anchorterminal.com/compare/arcade-vs-nango.md)
- [Arcade.dev vs Proof MCP](https://www.anchorterminal.com/compare/arcade-vs-proof-mcp.md)
- [Auth0 for AI Agents (Token Vault) vs Nango](https://www.anchorterminal.com/compare/auth0-ai-agents-vs-nango.md)
- [Auth0 for AI Agents (Token Vault) vs Proof MCP](https://www.anchorterminal.com/compare/auth0-ai-agents-vs-proof-mcp.md)
- [Clerk MCP server vs Nango](https://www.anchorterminal.com/compare/clerk-mcp-vs-nango.md)
- [Clerk MCP server vs Proof MCP](https://www.anchorterminal.com/compare/clerk-mcp-vs-proof-mcp.md)
- [Cloudflare Workers OAuth Provider vs Nango](https://www.anchorterminal.com/compare/cloudflare-workers-oauth-provider-vs-nango.md)
- [Cloudflare Workers OAuth Provider vs Proof MCP](https://www.anchorterminal.com/compare/cloudflare-workers-oauth-provider-vs-proof-mcp.md)
- [Descope Agentic Identity Hub vs Nango](https://www.anchorterminal.com/compare/descope-agentic-identity-vs-nango.md)
- [Descope Agentic Identity Hub vs Proof MCP](https://www.anchorterminal.com/compare/descope-agentic-identity-vs-proof-mcp.md)
- [Keycard vs Nango](https://www.anchorterminal.com/compare/keycard-vs-nango.md)
- [Keycard vs Proof MCP](https://www.anchorterminal.com/compare/keycard-vs-proof-mcp.md)
- [Microsoft Entra Agent ID vs Nango](https://www.anchorterminal.com/compare/microsoft-entra-agent-id-vs-nango.md)
- [Microsoft Entra Agent ID vs Proof MCP](https://www.anchorterminal.com/compare/microsoft-entra-agent-id-vs-proof-mcp.md)
- [Nango vs Scalekit AgentKit](https://www.anchorterminal.com/compare/nango-vs-scalekit-agentkit.md)
- [Nango vs Stytch Connected Apps](https://www.anchorterminal.com/compare/nango-vs-stytch-connected-apps.md)
- [Nango vs Vercel Connect](https://www.anchorterminal.com/compare/nango-vs-vercel-connect.md)
- [Nango vs WorkOS Pipes and Agents](https://www.anchorterminal.com/compare/nango-vs-workos-pipes.md)
- [Proof MCP vs Scalekit AgentKit](https://www.anchorterminal.com/compare/proof-mcp-vs-scalekit-agentkit.md)
- [Proof MCP vs Stytch Connected Apps](https://www.anchorterminal.com/compare/proof-mcp-vs-stytch-connected-apps.md)
- [Proof MCP vs WorkOS Pipes and Agents](https://www.anchorterminal.com/compare/proof-mcp-vs-workos-pipes.md)
- [Proof MCP vs Vercel Connect](https://www.anchorterminal.com/compare/proof-mcp-vs-vercel-connect.md)

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
