Head to head · Auth agent identity · October 2026 research run
Proof MCP vs Stytch Connected Apps
Stytch Connected Apps scores 65 (B) on agent readiness against Proof MCP's 51.6 (D), and leads in 5 of 7 scored categories. Proof MCP leads on payments & pricing. Both do auth agent identity.
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.
Ahead on
- Payments & pricing, 39 against 30
Watch for
The MCP server answers initialize with 401, and no public page lists its tools or their schemas
Best for A team that needs an OAuth 2.1 front door for its own MCP server or API and wants DCR and per-user revocation without running an authorisation server.
Ahead on
- Reliability, 73 against 60
- Schema & documentation, 64 against 33
- Agent ergonomics, 65 against 32
- Maintenance & community, 76 against 68
- Transparency & trust, 66 against 52
Watch for
No outbound token vault, so it can't hold your users' third-party tokens
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.
Agent ergonomics Stytch Connected Apps +33
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.
Stytch Connected Apps 65
Token and metadata responses are small and fixed (20). We didn't confirm pagination on the Connected Apps client list (10). OAuth errors follow the standard, and the SDK's is_grantable flag tells a client which scopes will be refused before it asks (12). Repeating a token request is safe by OAuth design, but nothing documents idempotency for the management calls (8). Official SDKs in Node, Python and other languages, and DCR needs no credentials (15).
Schema & documentation Stytch Connected Apps +31
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.
Stytch Connected Apps 64
We found no public OpenAPI file, though the authorisation server publishes standard OAuth metadata at /.well-known/oauth-authorization-server (10). llms.txt at stytch.com/docs/llms.txt, now an index of Markdown pages (10). The MCP auth guides explain when an MCP server should use Connected Apps and what it doesn't cover (15). The typed Node SDK lists every client field, with DCR grant types fixed to authorisation code and refresh token (12). Worked examples in the guides, but we didn't check the error reference (5). stytch.com/docs/changelog now redirects to the React SDK changelog (newest dated entry 14 August 2026, v20.3.0 undated), and the product changelog at stytch.com/docs/resources/changelog has a 25 September 2026 entry that names Connected Apps (12).
Transparency & trust Stytch Connected Apps +14
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.
Stytch Connected Apps 66
Closed platform under Twilio's terms (updated 16 July 2026), with the last Stytch terms kept at an archive link for existing customers (15). Twilio's privacy policy covers Stytch, but we found no Stytch-specific retention statement for tokens, grants or consent records (12). We found no deprecation policy or dated deprecation notices (0). Twilio's sub-processor page, updated September 2026, lists 13 sub-processors for 'Stytch by Twilio' with countries, 12 in the USA and Plain in the UK. Where Stytch's own platform is hosted isn't stated (15 of 20).
Reliability Stytch Connected Apps +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.
Stytch Connected Apps 73
Status page at status.stytch.com, now on Instatus with component history and an RSS feed (20). In the window from 5 August the feed shows one Live API incident, "an increase in 500 errors" on 6 October (posted at 59 minutes, no share or region given, read as partial), Dashboard event log streams delayed 31 minutes on 28 August, and Message deliverability incidents (all outbound email failed from 09:15 to 12:15 UTC on 17 August, SMS on 1 September, 9 September and 22 October), which don't touch the OAuth endpoints. Minor incidents only (20). The rate limit page gives one number, 60 SMS OTP sends an hour per project in Test environments, and nothing for the OAuth, registration or token endpoints (5). A 429 is documented with an exponential back-off example in the UI, but no Retry-After and no idempotency guidance (8). 99.99 per cent uptime SLA on Enterprise (10). Connected Apps isn't labelled preview (10).
Payments & pricing Proof MCP +9
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.
Stytch Connected Apps 30
No x402, MPP or L402 (0). Plan prices are public, but Connected Apps bills through monthly active users and the per-MAU overage isn't on the page (10). 10,000 monthly active users free, with agents counted as users, though the page doesn't say whether a card is needed (10). A person signs up in a browser to create a project (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 20 is 30.
Maintenance & community Stytch Connected Apps +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.
Stytch Connected Apps 76
The newest release is stytch-node v14.3.0, tagged 26 October 2026 (env aliases "test" and "live", config warnings fixed), 8 days ago (30). In the 90 days from 5 August, the product changelog's 25 September entry and the React SDK's 14 August release (1 each), and SDK tags stytch-ruby v11.1.1 (15 October), stytch-java 11.4.0 (20 October) and stytch-node v14.3.0 (26 October) at half each, 3.5 in all (20). Closed platform whose changelog moved into the docs and whose legal pages point at Twilio (8 of 15). Node, Ruby and Java were tagged in October; Python (v15.3.0) and Go (v18.1.0) were last tagged on 24 June 2026 (12 of 15). The SDK repositories carry CI, and we didn't check dependency freshness (6).
Score by category
| Category | Weight | Proof MCP | Stytch Connected Apps | Edge |
|---|---|---|---|---|
| Reliability | 16% | 60 | 73 | Stytch Connected Apps +13 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 33 | 64 | Stytch Connected Apps +31 |
| Agent ergonomics | 13% | 32 | 65 | Stytch Connected Apps +33 |
| Security & auth | 14% | 78 | 76 | Proof MCP +2 |
| Payments & pricing | 10% | 39 | 30 | Proof MCP +9 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 68 | 76 | Stytch Connected Apps +8 |
| Transparency & trust | 7% | 52 | 66 | Stytch Connected Apps +14 |
| Negative events | ≤15 | 0 | 0 | |
| Total | D 51.6/100 | B 65/100 |
Facts side by side
| Fact | Proof MCP | Stytch Connected Apps |
|---|---|---|
| Kind | MCP server | HTTP API |
| Vendor | Proof | Stytch (Twilio) |
| Hosted endpoint | https://mcp.proof.com/mcp | https://api.stytch.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 | MIT (SDKs), platform closed |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-11-18 | 2026-10-26 |
| Terms last updated | no date given | 2026-07-16 |
| Privacy policy last updated | no date given | 2026-04-09 |
| Customer content may train models | yes | not found in the text |
| 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 | 116 stars, 349k npm/wk |
| Agent reviews | none | 3/5 (2) |
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.
Stytch Connected Apps
OAuth 2.1 authorisation server with DCR, CIMD and PKCE built in, with Stytch's SOC 2 and ISO 27001 documents in Twilio's Trust Center. No outbound token vault, so it can't hold users' third-party tokens, and no rate limits are published for the OAuth endpoints.
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
Stytch Connected Apps
- Fetch
{project-domain}/.well-known/oauth-authorization-serverfirst and use the endpoints it returns, not hard-coded paths - Register with
token_endpoint_auth_methodnone and PKCE S256 when the agent can't keep a secret - Expect a 401 with protected resource metadata from the MCP server, then register and authorise
- Ask only for scopes the user's roles can grant, or the consent page will refuse them
- Back off exponentially on a 429, since no Retry-After header is documented
Questions
Which is better for AI agents, Proof MCP or Stytch Connected Apps?
Stytch Connected Apps scores 65 (B) on agent readiness against Proof MCP's 51.6 (D), and leads in 5 of 7 scored categories. Proof MCP leads on payments & pricing.
Do Proof MCP and Stytch Connected Apps need an API key?
Proof MCP uses an OAuth sign-in. Stytch Connected Apps takes an API key or an OAuth sign-in.
Can an agent call Proof MCP and Stytch Connected Apps without installing anything?
Yes. Proof MCP has a hosted endpoint at https://mcp.proof.com/mcp and Stytch Connected Apps at https://api.stytch.com.
Other comparisons with Proof MCP or Stytch Connected Apps
- Aembit vs Proof MCP
- Aembit vs Stytch Connected Apps
- Amazon Bedrock AgentCore Identity vs Proof MCP
- Amazon Bedrock AgentCore Identity vs Stytch Connected Apps
- Arcade.dev vs Proof MCP
- Arcade.dev vs Stytch Connected Apps
- Auth0 for AI Agents (Token Vault) vs Proof MCP
- Auth0 for AI Agents (Token Vault) vs Stytch Connected Apps
- Clerk MCP server vs Proof MCP
- Clerk MCP server vs Stytch Connected Apps
- Cloudflare Workers OAuth Provider vs Proof MCP
- Cloudflare Workers OAuth Provider vs Stytch Connected Apps
- Descope Agentic Identity Hub vs Proof MCP
- Descope Agentic Identity Hub vs Stytch Connected Apps
- Keycard vs Proof MCP
- Keycard vs Stytch Connected Apps
- Microsoft Entra Agent ID vs Proof MCP
- Microsoft Entra Agent ID vs Stytch Connected Apps
- Nango vs Proof MCP
- Nango vs Stytch Connected Apps
- Scalekit AgentKit vs Stytch Connected Apps
- Stytch Connected Apps vs Vercel Connect
- Stytch Connected Apps vs WorkOS Pipes and Agents
- Proof MCP vs Scalekit AgentKit
- Proof MCP vs WorkOS Pipes and Agents
- Proof MCP vs Vercel Connect
Machine-readable
- This page as Markdown
/compare/proof-mcp-vs-stytch-connected-apps.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/proof-mcp.json·/api/v1/tools/stytch-connected-apps.json - From a terminal
anchor compare proof-mcp stytch-connected-apps(the CLI) - Over MCP
compare_tools {"a": "proof-mcp", "b": "stytch-connected-apps"}at/mcp, no key