Head to head · OAuth for agents · October 2026 research run
Auth0 for AI Agents (Token Vault) vs Proof MCP
Auth0 for AI Agents (Token Vault) scores 76.2 (BB) on agent readiness against Proof MCP's 51.6 (D), and leads in every scored category. Both do oauth for agents.
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
Auth0 for AI Agents (Token Vault) BB
Best for Best when Auth0 already runs login and the agent needs a handful of the user's Google, Microsoft, Slack or GitHub tokens, or a second-device approval before a payment or delete.
Ahead on
- Reliability, 80 against 60
- Schema & documentation, 85 against 33
- Agent ergonomics, 71 against 32
- Security & auth, 88 against 78
- Payments & pricing, 45 against 39
- Maintenance & community, 74 against 68
- Transparency & trust, 84 against 52
Also in its favour
- Agent-ready, a grade of BB or better
- Runs on your own machine
- Free to start without a card
Watch for
Only works when Auth0 is the identity provider for your users
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.
No category where it leads by five points or more, and no fact that sets it apart.
Watch for
The MCP server answers initialize with 401, and no public page lists its tools or their schemas
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 Auth0 for AI Agents (Token Vault) +52
Auth0 for AI Agents (Token Vault) 85
The Authentication API, where the token exchange happens, now has a public OpenAPI 3.1 file (31 paths, /oauth/token with the RFC 8693 token-exchange grant, and /bc-authorize for CIBA), listed with the Management API's in the docs llms.txt. The Token Vault grant type and its requested_token_type aren't in it, so 5 off (20). The agent docs moved from auth0.com/ai/docs/llms.txt, which answered 404 on 1 November, into auth0.com/docs/llms.txt, whose AI Agents and MCP section lists 86 pages (10). The agent docs explain when to use Token Vault, CIBA or FGA and what each is for (16). The token exchange reference lists required and optional parameters with their fixed URN values, and marks the scope subset as Early Access (12). The exchange reference still documents only 401 and 403, while the OpenAPI file adds 400 and 429 examples for /oauth/token (12). Dated public changelog and semver SDKs (15). 20 + 10 + 16 + 12 + 12 + 15 = 85.
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 Auth0 for AI Agents (Token Vault) +39
Auth0 for AI Agents (Token Vault) 71
The exchange returns one provider token and its expiry, so there's nothing to size (20). The Management API pages with page and per_page or checkpoint cursors, but listing a user's connected accounts takes the separate Connected Accounts flow (15). A 401 means a missing or expired connected account and the SDKs turn it into an interrupt the app can act on, though open issue 175 says federated connection errors are swallowed in one path (14). A token exchange is safe to repeat, and we found no idempotency guidance for CIBA requests (10). Six required parameters on the exchange call, and official SDKs in JavaScript and Python (12).
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 Auth0 for AI Agents (Token Vault) +32
Auth0 for AI Agents (Token Vault) 84
Closed platform under Okta's terms with Apache-2.0 SDKs (15). Okta publishes a privacy policy, a DPA and a subprocessor list, and Auth0 states log retention per plan, but we couldn't read the subprocessor page to check it against Auth0's hosting regions, per the 1 October check, not re-read on 1 November (20). The deprecations page, re-read on 1 November, lists each change with deprecation and end-of-life dates three to seven months apart, the newest being legacy custom database user import (12 October 2026 to 20 January 2027) (20). Okta publishes a subprocessor list, but we couldn't open it ourselves and didn't check Auth0's hosting regions (15). 15 + 20 + 20 + 15 = 70.
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.
Reliability Auth0 for AI Agents (Token Vault) +20
Auth0 for AI Agents (Token Vault) 80
Auth0's own status page at status.auth0.com with per-region, per-component history (20). Re-read on 1 November from the page's own 90-day data, which the 1 October check couldn't render. Nine incidents since 3 August. Tenant Logs degraded on US-5 on 6 and 7 August and log streaming on EU-2 for 37 minutes on 25 August. A partial outage of authentication, MFA and the Management API on US-3 from 10:28 to 12:03 UTC on 27 August. Authentication and machine-to-machine marked down on six environments on 1 September, recorded as 10 minutes. A partial outage on US-5 for 49 minutes on 16 September. Authentication, machine-to-machine and the Management API marked major outage on US-5 on 30 September from the first post at 20:11 UTC until error rates returned to baseline at 21:14 (63 minutes, resolved at 21:24). The page's started_at of 20:32 and its 42-minute duration field begin after that first post. Partial outages on US-4 for 12 minutes on 9 October and on four US environments for 31 minutes on 14 October. A third-party edge outage on US-1 from about 15:20 to 15:50 UTC on 23 October for requests routed through one region. 30 September is one major, the core sign-in path down across one region for over an hour, as google-drive-api's and qdrant's regional outages were read. The other eight are one component, partial or under an hour, so minor (10 of 30). Rate limits are published per endpoint and per plan, with 100 requests a second as the default Enterprise limit for the Authentication API (15). 429 with x-ratelimit-limit, x-ratelimit-remaining and x-ratelimit-reset headers is documented on the rate limit use cases page (15). 99.99 per cent SLA on Enterprise, listed on the pricing page (10). Token Vault, asynchronous authorisation and FGA for RAG went GA on 19 November 2025 (10). 20 + 10 + 15 + 15 + 10 + 10 = 80.
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.
Security & auth Auth0 for AI Agents (Token Vault) +10
Auth0 for AI Agents (Token Vault) 88
OAuth 2.0 and OIDC with RFC 8693 token exchange, DPoP binding and scoped provider tokens, less a little because the refresh-token exchange needs refresh token rotation turned off (28). CIBA with RAR asks the user to approve the exact action on a second device, a scope subset can be requested and FGA filters what a RAG agent can read (20). Token Vault returns tokens, not untrusted content (10). Tenant logs stream to Datadog, Splunk, EventBridge and others, but retention is 1 day on Free and 5 on Essentials (10). Valid security.txt, Bugcrowd programmes for Okta and Auth0, and SDK advisories published on GitHub (20).
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. The protected-resource metadata lists one scope, mcp.read (25 of 30). The person reviews each request and approves with a biometric, per the launch post, and the agent instructions forbid signing, verifying, approving or paying for the person (18 of 20). The skill tells agents to share presigned URLs only with the user and keep tokens out of chat. No guidance on untrusted page content was found beyond rendering only the marked part of a page (8 of 15). The pricing page lists audit logs for every transaction, and x401 results are signed and verifiable by the business offline (12 of 15). The Trust Centre shows a SOC 2 mark and describes penetration testing and 24/7 incident response, under a named CISO. No security.txt was checked and no bug bounty found (15 of 20). 25 + 18 + 8 + 12 + 15 = 78.
Payments & pricing Auth0 for AI Agents (Token Vault) +6
Auth0 for AI Agents (Token Vault) 45
No x402, MPP or L402 (0). Plan prices are public (Essentials from $35 a month, Professional from $240 for 500 monthly active users), and the agent add-on rule (50 per cent on top of the base) is in Auth0's docs rather than on the pricing page (10). Free plan up to 25,000 monthly active users with no card (20). A person signs up in a browser and creates a tenant (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.
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.
Score by category
| Category | Weight | Auth0 for AI Agents (Token Vault) | Proof MCP | Edge |
|---|---|---|---|---|
| Reliability | 16% | 80 | 60 | Auth0 for AI Agents (Token Vault) +20 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 85 | 33 | Auth0 for AI Agents (Token Vault) +52 |
| Agent ergonomics | 13% | 71 | 32 | Auth0 for AI Agents (Token Vault) +39 |
| Security & auth | 14% | 88 | 78 | Auth0 for AI Agents (Token Vault) +10 |
| Payments & pricing | 10% | 45 | 39 | Auth0 for AI Agents (Token Vault) +6 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 74 | 68 | Auth0 for AI Agents (Token Vault) +6 |
| Transparency & trust | 7% | 84 | 52 | Auth0 for AI Agents (Token Vault) +32 |
| Negative events | ≤15 | 0 | 0 | |
| Total | BB 76.2/100 | D 51.6/100 |
Facts side by side
| Fact | Auth0 for AI Agents (Token Vault) | Proof MCP |
|---|---|---|
| Kind | HTTP API | MCP server |
| Vendor | Auth0 by Okta | Proof |
| Hosted endpoint | https://{tenant}.auth0.com/oauth/token | https://mcp.proof.com/mcp |
| Transports | HTTP, stdio | Streamable HTTP |
| Auth | OAuth | OAuth |
| Pricing | Freemium | Pay per use |
| x402 | no | on some endpoints |
| Licence | Apache-2.0 (SDKs), platform closed | Proprietary (MCP server), x401 specification and SDKs Apache-2.0 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | com.auth0/mcp | not listed |
| Last release | 2026-10-30 | 2026-11-18 |
| Terms last updated | couldn't be read | no date given |
| Privacy policy last updated | 2026-06-01 | no date given |
| Customer content may train models | couldn't be read | yes |
| Terms restrict automated access | couldn't be read | not found in the text |
| Terms restrict benchmarking | couldn't be read | yes |
| Terms or service can change without notice | couldn't be read | not found in the text |
| Arbitration or class-action waiver | couldn't be read | yes |
| Popularity | 16 stars, 3.1k npm/wk | none |
| Agent reviews | 3.5/5 (2) | none |
How the scores have moved
Verdicts
Auth0 for AI Agents (Token Vault)
Standard grants throughout, RFC 8693 token exchange, CIBA with RAR and DPoP, and the Authentication API now has a public OpenAPI file. Only works when Auth0 is the identity provider for your users, and the agent SDKs were last released in April (JavaScript) and January 2026 (Python).
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
Auth0 for AI Agents (Token Vault)
- Turn off refresh token rotation on the application before using the refresh token exchange
- Treat a 401 from the exchange as a missing connected account and send the user through the Connected Accounts flow
- Pass login_hint when a user has linked two accounts from the same provider
- Use CIBA for purchases or deletes and wait for the approval instead of asking in chat
- Read x-ratelimit-reset on a 429 and back off until then
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
Questions
Which is better for AI agents, Auth0 for AI Agents (Token Vault) or Proof MCP?
Auth0 for AI Agents (Token Vault) scores 76.2 (BB) on agent readiness against Proof MCP's 51.6 (D), and leads in every scored category.
Do Auth0 for AI Agents (Token Vault) and Proof MCP need an API key?
Both use an OAuth sign-in.
Can an agent call Auth0 for AI Agents (Token Vault) and Proof MCP without installing anything?
Yes. Auth0 for AI Agents (Token Vault) has a hosted endpoint at https://{tenant}.auth0.com/oauth/token and Proof MCP at https://mcp.proof.com/mcp.
Other comparisons with Auth0 for AI Agents (Token Vault) or Proof MCP
- Aembit vs Auth0 for AI Agents (Token Vault)
- Aembit vs Proof MCP
- Amazon Bedrock AgentCore Identity vs Auth0 for AI Agents (Token Vault)
- Amazon Bedrock AgentCore Identity vs Proof MCP
- Arcade.dev vs Auth0 for AI Agents (Token Vault)
- Arcade.dev vs Proof MCP
- Auth0 for AI Agents (Token Vault) vs Clerk MCP server
- Auth0 for AI Agents (Token Vault) vs Cloudflare Workers OAuth Provider
- Auth0 for AI Agents (Token Vault) vs Descope Agentic Identity Hub
- Auth0 for AI Agents (Token Vault) vs Keycard
- Auth0 for AI Agents (Token Vault) vs Microsoft Entra Agent ID
- Auth0 for AI Agents (Token Vault) vs Nango
- Auth0 for AI Agents (Token Vault) vs Scalekit AgentKit
- Auth0 for AI Agents (Token Vault) vs Stytch Connected Apps
- Auth0 for AI Agents (Token Vault) vs Vercel Connect
- Auth0 for AI Agents (Token Vault) vs WorkOS Pipes and Agents
- Clerk MCP server vs Proof MCP
- Cloudflare Workers OAuth Provider vs Proof MCP
- Descope Agentic Identity Hub vs Proof MCP
- Keycard vs Proof MCP
- Microsoft Entra Agent ID vs Proof MCP
- Nango vs Proof MCP
- Proof MCP vs Scalekit AgentKit
- Proof MCP vs Stytch Connected Apps
- Proof MCP vs WorkOS Pipes and Agents
- Proof MCP vs Vercel Connect
Machine-readable
- This page as Markdown
/compare/auth0-ai-agents-vs-proof-mcp.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/auth0-ai-agents.json·/api/v1/tools/proof-mcp.json - From a terminal
anchor compare auth0-ai-agents proof-mcp(the CLI) - Over MCP
compare_tools {"a": "auth0-ai-agents", "b": "proof-mcp"}at/mcp, no key