Head to head · OAuth for agents · October 2026 research run

Cloudflare Workers OAuth Provider vs Proof MCP

Cloudflare Workers OAuth Provider scores 79.3 (A) 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

Cloudflare Workers OAuth Provider A

Best for Developers putting a remote MCP server on Cloudflare behind standard OAuth.

Ahead on

  • Reliability, 74 against 60
  • Schema & documentation, 86 against 33
  • Agent ergonomics, 74 against 32
  • Payments & pricing, 75 against 39
  • Maintenance & community, 87 against 68
  • Transparency & trust, 86 against 52

Also in its favour

  • Agent-ready, a grade of BB or better
  • Open source

Watch for

Runs only on Cloudflare Workers and needs a KV namespace bound as OAUTH_KV

Proof MCP D

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

  • A hosted endpoint, with nothing to install

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 Cloudflare Workers OAuth Provider +53

Cloudflare Workers OAuth Provider 86

Read as a library. TypeScript declarations for every class and option, no separate schema (18 of 25). Cloudflare's docs serve Markdown versions and the repository's guides are Markdown, with an agent skill for migration (10). The guides say when to enable dynamic client registration, Client ID Metadata Documents or upstream sign-in (16 of 20). Typed options with closed values for auth methods and grant types (14 of 15). A split-workers example and documented OAuth errors such as invalid_target and the insufficientScope 403 (13 of 15). Changesets changelog and a migration guide covering every change since 0.10 (15). Total 86.

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 Cloudflare Workers OAuth Provider +42

Cloudflare Workers OAuth Provider 74

Framework reading. Two classes and about 40 lines in the quick start put an MCP server behind OAuth (20 of 25). Required scopes and step-up per request (16 of 20). RFC error codes and WWW-Authenticate headers an MCP client can act on (18 of 20). Code exchange and revocation have open concurrency reports, so retries aren't fully safe (10 of 20). TypeScript on Workers only, with sensible defaults (10 of 15). Total 74.

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.

Payments & pricing Cloudflare Workers OAuth Provider +36

Cloudflare Workers OAuth Provider 75

Self-hosted rule. No x402, MPP or L402 (0 of 40). Free under MIT, with Workers prices public (20). Workers has a free plan (20). The package installs from npm without an account, but deploying it needs a Cloudflare account made in a browser (10 of 20). Total 50. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 50 is 75.

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.

Transparency & trust Cloudflare Workers OAuth Provider +34

Cloudflare Workers OAuth Provider 86

MIT (30). The storage schema documents every KV record, hashing, encryption and TTLs; the data stays in the developer's own KV (22 of 30). The migration guide covers every change since 0.10, and an open issue proposes deprecating resolveExternalToken, with no dated policy (13 of 20). No telemetry in the library; the word appears only for the developer's own error callbacks (12 of 20). Total 77.

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 Cloudflare Workers OAuth Provider +19

Cloudflare Workers OAuth Provider 87

1.2.4 on 22 October 2026 (30). Nine npm releases in 90 days (20). Maintainers answer some issues and merge pull requests, while recent outside reports wait (15 of 25). Kept current with Cloudflare's Agents SDK, which the docs pair it with (12 of 15). npm provenance, changesets, semgrep and conformance CI (10). Total 87.

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.

Reliability Cloudflare Workers OAuth Provider +14

Cloudflare Workers OAuth Provider 74

Local-software lines, as a library the developer deploys. On npm with the Workers runtime and KV requirements stated (20). ci.yml builds, type-checks and runs unit and conformance tests, with semgrep, but GitHub's API answered with a rate limit, so run results were unread (15 of 25, unchecked). 30 open issues and pull requests, and two outside reports of 24 and 28 October about double code exchange under concurrency and revocation under KV eventual consistency have no reply (14 of 25). Changesets changelog and a migration guide, but 1.2.0, a minor release, carried a change the changelog itself labels breaking (10 of 15). Version 1.2.4 (15). Total 74.

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

CategoryWeightCloudflare Workers OAuth ProviderProof MCPEdge
Reliability16%7460Cloudflare Workers OAuth Provider +14
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8633Cloudflare Workers OAuth Provider +53
Agent ergonomics13%7432Cloudflare Workers OAuth Provider +42
Security & auth14%8078Cloudflare Workers OAuth Provider +2
Payments & pricing10%7539Cloudflare Workers OAuth Provider +36
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8768Cloudflare Workers OAuth Provider +19
Transparency & trust7%8652Cloudflare Workers OAuth Provider +34
Negative events≤1500
TotalA 79.3/100D 51.6/100

Facts side by side

FactCloudflare Workers OAuth ProviderProof MCP
KindSDK + MCPMCP server
VendorCloudflareProof
Hosted endpointno (local only)https://mcp.proof.com/mcp
TransportsStreamable HTTP
AuthOAuthOAuth
PricingFreePay per use
x402noon some endpoints
LicenceMITProprietary (MCP server), x401 specification and SDKs Apache-2.0
Read-only variant documentednono
llms.txtnoyes
Last release2026-10-222026-11-18
Terms last updated2025-09-12no date given
Privacy policy last updatedno date givenno date given
Customer content may train modelsnot found in the textyes
Terms restrict automated accessyesnot found in the text
Terms restrict benchmarkingnot found in the textyes
Terms or service can change without noticeyesnot found in the text
Arbitration or class-action waiveryesyes
Popularity1.9k stars, 1.1M npm/wknone

How the scores have moved

Verdicts

Cloudflare Workers OAuth Provider

Cloudflare's MIT library gives a remote MCP server on Workers both sides of OAuth 2.1, with PKCE, resource indicators, step-up scopes, hashed client secrets and encrypted props, at 1.2.4 with a conformance suite. It runs only on Workers with KV, 1.2.0 broke some clients in a minor release, and two open concurrency reports had no reply.

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

Cloudflare Workers OAuth Provider

  1. Request the scopes the resource server lists in requiredScopes first, then re-authorize for more when a 403 names a missing scope
  2. Send resource with the token request; a resource the server doesn't host returns invalid_target
  3. Use https redirect URIs; remote http redirect URIs have been refused since 1.2.0
  4. Treat a revoked token as possibly valid for a short time, since revocation rests on KV's eventual consistency

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, Cloudflare Workers OAuth Provider or Proof MCP?

Cloudflare Workers OAuth Provider scores 79.3 (A) on agent readiness against Proof MCP's 51.6 (D), and leads in every scored category.

Can an agent call Cloudflare Workers OAuth Provider and Proof MCP without installing anything?

No hosted endpoint is listed for Cloudflare Workers OAuth Provider. Proof MCP has a hosted endpoint at https://mcp.proof.com/mcp.

Are Cloudflare Workers OAuth Provider and Proof MCP open source?

Cloudflare Workers OAuth Provider is open source (MIT). No open-source release is listed for Proof MCP.

Other comparisons with Cloudflare Workers OAuth Provider or Proof MCP

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.