# Cloudflare Workers OAuth Provider > Cloudflare Workers OAuth Provider is Cloudflare's open-source TypeScript library that adds OAuth 2.1 authorization to HTTP APIs and remote MCP servers on Cloudflare Workers, as both the authorization server and the resource server. - Canonical: https://www.anchorterminal.com/tools/cloudflare-workers-oauth-provider - Pricing: https://www.anchorterminal.com/tools/cloudflare-workers-oauth-provider#pricing - Reviews: https://www.anchorterminal.com/tools/cloudflare-workers-oauth-provider#reviews - Markdown: https://www.anchorterminal.com/tools/cloudflare-workers-oauth-provider.md (~7,300 tokens) - Slim: https://www.anchorterminal.com/tools/cloudflare-workers-oauth-provider.min.md (~1,380 tokens, same facts, less prose, for token-sensitive contexts) - JSON: https://www.anchorterminal.com/tools/cloudflare-workers-oauth-provider.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 cloudflare-workers-oauth-provider.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.. and .vs.. 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-07 ## Overview **Grade BB · 76.2/100 · rank #47 of 1486 · #4 in Agent auth & delegated access · agent-ready · confidence medium** More from Cloudflare, listed separately because each is its own product: [Cloudflare AI Gateway](https://www.anchorterminal.com/tools/cloudflare-ai-gateway.md) (Model APIs & inference), [Cloudflare Workers AI](https://www.anchorterminal.com/tools/cloudflare-workers-ai.md) (Model APIs & inference), [Cloudflare Sandbox SDK](https://www.anchorterminal.com/tools/cloudflare-sandbox-sdk.md) (Code execution sandboxes), [Cloudflare Web Search API](https://www.anchorterminal.com/tools/cloudflare-web-search.md) (Web search APIs), [Clairic](https://www.anchorterminal.com/tools/cloudflare-clairic.md) (Document parsing & extraction), [Cloudflare AI Search](https://www.anchorterminal.com/tools/cloudflare-ai-search.md) (Retrieval & vector search), [Cloudflare CLI (cf)](https://www.anchorterminal.com/tools/cloudflare-cli.md) (Cloud & infrastructure), [Cloudflare MCP Servers](https://www.anchorterminal.com/tools/cloudflare-mcp.md) (Cloud & infrastructure), [Cloudflare Email Service](https://www.anchorterminal.com/tools/cloudflare-email-service.md) (Email delivery APIs), [Cloudflare R2](https://www.anchorterminal.com/tools/cloudflare-r2.md) (File storage & sharing), [Clef](https://www.anchorterminal.com/tools/cloudflare-clef.md) (Decision models). ## Assessment 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. ## Facts | Field | Value | | --- | --- | | Vendor | Cloudflare (https://developers.cloudflare.com/agents/model-context-protocol/authorization/) | | Kind | SDK + MCP | | Category | Agent auth & delegated access (https://www.anchorterminal.com/categories/agent-auth) | | Auth | OAuth · The library issues OAuth 2.1 tokens to MCP clients, with PKCE, scopes, resource indicators, Client ID Metadata Documents and optional dynamic client registration. Users sign in through the developer's own `/authorize` handler, Cloudflare Access or an upstream identity provider such as Stytch, Auth0, WorkOS or Descope. | | Pricing | Free (Free · OSS) · Free under MIT. Running it needs a Cloudflare Workers account and a KV namespace, billed under Workers pricing, which has a free plan. | | x402 | No · No x402, MPP or L402 in the source, README or docs (checked 2026-11-06). | | Licence | MIT | | Packages | npm: `@cloudflare/workers-oauth-provider` | | Source | https://github.com/cloudflare/workers-oauth-provider | | Docs | https://github.com/cloudflare/workers-oauth-provider/tree/main/docs | | llms.txt | not found | | Last release | 2026-10-22 | | GitHub stars | 1,893 (as of 2026-11-06) | | npm downloads / week | 1,122,612 | | Surface listed | The `@cloudflare/workers-oauth-provider` library 1.2.4, read from a clone of github.com/cloudflare/workers-oauth-provider, the npm registry and Cloudflare's MCP authorization page on 6 November 2026. Nothing was installed or deployed | | Not covered elsewhere | No Cloudflare listing covers this library on 6 November 2026; cloudflare-mcp is Cloudflare's own MCP server and cloudflare-sandbox-sdk its sandboxes | | Roles | `OAuthAuthorizationServer` signs users in and issues tokens; `OAuthResourceServer` wraps the MCP endpoint and validates tokens over a Service Binding | | Standards | OAuth 2.1 with PKCE, RFC 9728 protected-resource metadata, resource indicators, token revocation, optional dynamic client registration, Client ID Metadata Documents and private_key_jwt client assertions | | Docs | README, seven Markdown guides (authorization server, resource servers, consent page, upstream sign-in, MCP discovery, advanced configuration, migration to 1.x), a storage schema and an agent skill for migrating | | Legal entity | Cloudflare, Inc., the copyright holder in LICENSE.txt | | Capabilities | auth.oauth, auth.tokens, auth.consent | | Tags | open-source, mit, typescript, library, cloudflare-workers, oauth-2.1, mcp, pkce, free | | JSON | https://www.anchorterminal.com/api/v1/tools/cloudflare-workers-oauth-provider.json | ## Score breakdown (methodology v0.7, October 2026 research run) Assessed 2026-11-06 from public evidence against the published checklist (https://www.anchorterminal.com/benchmark/#checklist). Confidence: medium. Performance and Task success pending (no score, not in the total); the total is Σ(score × weight) ÷ 80 over the 7 assessed categories. "This run" is each category's share of the 100 points. | Category | Weight | This run | Score (0–100) | Points | | --- | --- | --- | --- | --- | | Reliability | 16% | 20 | 74 | 14.8 | | Performance | 10% | pending | pending | n/a | | Schema & documentation | 13% | 16.2 | 86 | 14.0 | | Agent ergonomics | 13% | 16.2 | 74 | 12.0 | | Security & auth | 14% | 17.5 | 80 | 14.0 | | Payments & pricing | 10% | 12.5 | 50 | 6.2 | | Task success | 10% | pending | pending | n/a | | Maintenance & community | 7% | 8.8 | 87 | 7.6 | | Transparency & trust (editorial 77, provenance 95) | 7% | 8.8 | 86 | 7.5 | | Negative events | up to −15 | up to −15 | none recorded | 0 | | **Total** | | | | **76.2 → BB** | ### Why each score - Reliability 74 (checked 2026-11-06): 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. - Performance: Pending. Latency is measured per call by our probes, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until the first probe window closes. - Schema & documentation 86 (checked 2026-11-06): 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. - Agent ergonomics 74 (checked 2026-11-06): 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. - Security & auth 80 (checked 2026-11-06): OAuth 2.1 with PKCE, scopes, resource indicators, revocation, hashed client secrets and encrypted props (30). Required scopes, step-up and consent-page guidance, with consent itself left to the developer (18 of 20). Returns no untrusted content (10). No audit log of grants or token use built in (5 of 15). Cloudflare's HackerOne programme, security@cloudflare.com and a valid security.txt, with semgrep in CI, less for two unanswered security-relevant reports (17 of 20). Total 80. - Payments & pricing 50 (checked 2026-11-06): 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. - Task success: Pending. Task success needs the category task suites run through each tool, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until then. A data provider's data-quality score is published on its listing now and becomes half of this category when it's scored. - Maintenance & community 87 (checked 2026-11-06): 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. - Transparency & trust 86 (checked 2026-11-06): 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. Fix list, everything this grade says the listing lacks, the biggest gain first (16 items). What it covers is at https://www.anchorterminal.com/fixes/cloudflare-workers-oauth-provider.md (JSON https://www.anchorterminal.com/fixes/cloudflare-workers-oauth-provider.json). The whole list for a coding agent comes from `POST https://www.anchorterminal.com/api/v1/fix-list` with `{"listing": "cloudflare-workers-oauth-provider", "plan": "read"}`, free while the beta runs ### What we couldn't check - The lead was right on the library, the providers and that no GA label is shown; the package is at 1.2.4 and the docs page carries no beta label. GitHub and Google appear only as upstream sign-in options, not as worked examples. - Category agent-auth as suggested. auth.oauth first, since issuing OAuth tokens to agents' MCP clients is its job. - Judgement call. 1.2.0 shipped a change its changelog calls breaking in a minor version, on the day it shipped. It's a security tightening in line with OAuth 2.1, so it's scored in Reliability's semver line rather than deducted. - Disclosure. HISTORY.md says the library was largely written with Claude. Our research agents also run on Claude; it was graded by the same checklist. - unchecked: CI run results, because GitHub's API answered with a rate limit. - Company facts and the humans file are taken from the existing Cloudflare listings, as the batch rules ask. ### Sources - repository, README, docs, SECURITY.md and HISTORY.md (clone): (seen 2026-11-06) - changelog: (seen 2026-11-06) - storage schema: (seen 2026-11-06) - open issues: (seen 2026-11-06) - npm registry: (seen 2026-11-06) - MCP authorization docs (27 October 2026): (seen 2026-11-06) ## Score history Every move of a score since the listing was graded, newest first, with its cause. A score can't move without an entry here. JSON: https://www.anchorterminal.com/api/v1/tools/cloudflare-workers-oauth-provider/history.json - 2026-11-06: graded 76.2 BB (methodology 0.7) ## Who's behind it (provenance 95/100, checked 2026-11-06) | Check | Finding | Points | | --- | --- | --- | | Legal entity named | Cloudflare, Inc. | 20/20 | | Domain age | cloudflare.com, registered 2009-02-17 (17 years) | 15/15 | | Endpoint on the vendor's domain | no hosted endpoint | n/a | | Terms of service | read, states 7 of the 7 things a reader expects, and has 2 clauses that cost points | 6/10 | | Privacy policy | read, states 7 of the 8 things a reader expects | 9.3/10 | | Status page | www.cloudflarestatus.com | 10/10 | | Changelog | published | 10/10 | | security.txt | valid | 10/10 | | People named | 4 named with their role, none with a public profile | 7/10 | | Support route | help pages, a community | 5/5 | Company facts as on the cloudflare-sandbox-sdk listing (checked 1 November 2026); terms, privacy and status links were not re-read for this library. www.cloudflare.com/.well-known/security.txt answered on 6 November 2026. developers.cloudflare.com robots.txt allows the agents docs and carries Content-Signal ai-input=yes. ### Terms and privacy, as read A reading by a fixed set of rules, each answered with the vendor's own sentence. Not legal advice. **Terms of service** (https://www.cloudflare.com/terms/), read 2026-10-08, dated 2025-09-12, states 7 of the 7 things a reader expects. - To know. Restricts automated access (costs points). "(e) introduce software or automated agents or scripts into the Services so as to produce multiple accounts, generate automated searches, requests or queries, or to strip or mine data from the Services;" - To know. Says the terms or the service can change without notice (costs points). "We also reserve the right to modify or discontinue the Service at any time (including, without limitation, by limiting or discontinuing certain features of the Service) without notice to you." - To know. Says access can be ended without notice or for any reason. "We may at our sole discretion terminate your user account or Suspend or terminate your use or access to the Service at any time, with or without notice for any reason or no reason at all." - To know. Requires arbitration or waives class actions. "THIS AGREEMENT CONTAINS PROVISIONS REQUIRING THAT YOU AGREE TO THE USE OF ARBITRATION TO RESOLVE ANY DISPUTES ARISING UNDER THIS AGREEMENT RATHER THAN A JURY TRIAL OR ANY OTHER COURT PROCEEDINGS, AND TO WAIVE YOUR PARTICIPATION IN CLASS ACTION OF ANY KIND AGAINST CLOUDFLARE." - Gives the date it was last updated. Last updated 2025-09-12. - Names the governing law or courts. The law of the State of California. - States a limit on its liability. Capped at the fees paid in the 12 months before the claim. - Says how changes to the terms are announced. Says it gives notice of a change. - Also in the text (2026-10-08). A customer who lets a third party into the account with an API token or OAuth does so at its own risk, and that party may change or delete account data. "You acknowledge that by permitting a third party to access your Cloudflare account, the third party may obtain, modify, or delete your account data and settings." - Also in the text (2026-10-08). Fees are non-refundable, and a customer who cancels is billed in full for the subscription term in which it cancels. "YOU WILL BE BILLED IN FULL FOR THE SUBSCRIPTION TERM IN WHICH YOU CANCEL AND NO REFUNDS WILL BE PROVIDED FOR THE UNUSED PORTION OF SUCH SUBSCRIPTION TERM." - Also in the text (2026-10-08). Cloudflare accepts no liability for harm arising from free or trial versions of the Services. "We will have no liability for any harm or damage arising out of or in connection with any Free Services." **Privacy policy** (https://www.cloudflare.com/privacypolicy/), read 2026-10-08, gives no date, states 7 of the 8 things a reader expects. - To know. Says it sells personal data or shares it for advertising. "Making Personal Information (such as online identifiers or browsing activity) available to these companies may be considered a “sale” or “sharing” of your Personal Information under the CCPA." - Not found in the text. Gives the date it was last updated. - Says how long data is kept. For as long as needed, with no period named. - Says whether personal data is sold or shared for advertising. Says it does not sell personal data. - Gives a privacy contact. privacyquestions@cloudflare.com. - Says where data is transferred or stored. Relies on the Data Privacy Framework. ## Humans behind the project (researched 2026-11-06 from public pages, not part of the grade) ### Key people - Matthew Prince, Co-founder, CEO and Co-chair, Cloudflare - Michelle Zatlyn, Co-founder, President and Co-chair, Cloudflare - Lee Holloway, Co-founder, Cloudflare - Dane Knecht, Chief Technology Officer, Cloudflare - Note: Cloudflare's page for The Cold Start at Cloudflare Connect 2026 (read on 28 October 2026) shows Matthew Prince as Co-founder and CEO, Michelle Zatlyn as Co-founder and President and Dane Knecht as CTO, each in a card with their name and portrait, and the blog post introducing it names Zatlyn as co-founder and President. Cloudflare's press release of 20 October 2026 also names Knecht as chief technology officer. The co-chair titles come from Wikipedia's Cloudflare article. Lee Holloway's step-down in 2015 was sourced to TechCrunch, which its robots.txt puts off limits, so it was dropped from his role on 6 November 2026. Product people stay on their own listings. Copied from the cloudflare-sandbox-sdk listing on 6 November 2026 without its product manager; the library's changelog credits maintainers by GitHub handle only. On 6 November 2026 the GitHub issues link was corrected from the Sandbox SDK's to this library's repository, and the Sandbox SDK's product-team sources were removed. - Cloudflare: LinkedIn https://www.linkedin.com/company/cloudflare X https://x.com/cloudflare GitHub https://github.com/cloudflare ### Ownership and investors - Ownership: Public company (NYSE: NET) ### Getting support - Discord: https://discord.cloudflare.com - Help: https://developers.cloudflare.com/support/contacting-cloudflare-support/ - Community (Forum): https://community.cloudflare.com - Community (GitHub issues): https://github.com/cloudflare/workers-oauth-provider/issues - Sources: https://www.cloudflare.com/our-story/, https://www.cloudflare.com/, https://developers.cloudflare.com/support/, https://developers.cloudflare.com/support/contacting-cloudflare-support/, https://developers.cloudflare.com/, https://github.com/cloudflare/workers-oauth-provider, https://www.cloudflare.com/connect/cold-start/ ## Live (updated 2026-11-07 17:45 UTC) - Vendor status page: a major outage, Partial System Outage - github `cloudflare/workers-oauth-provider` v1.2.4, released 2026-10-22 - npm `@cloudflare/workers-oauth-provider` 1.2.4 - security.txt: valid - Watching changelog - Always current: https://www.anchorterminal.com/api/v1/live/cloudflare-workers-oauth-provider.json ## Probe metrics Not measured yet. Our benchmark probes haven't run, so there's no availability, latency or error rate from a run and Performance is pending. Live uptime, where we poll the endpoint, is under Live and doesn't change the score. ## Strengths - Implements both the authorization server and the resource server for MCP, with discovery, token, revocation and optional dynamic client registration - PKCE, resource indicators, required scopes and a step-up helper that answers 403 naming the missing scope - Client secrets stored as SHA-256 hashes, and props encrypted with AES-GCM so only token holders can read them - MIT, published to npm with provenance, nine releases in the 90 days to 6 November 2026 and a conformance test suite - Covered by Cloudflare's HackerOne programme and security@cloudflare.com, per SECURITY.md ## Weaknesses - Runs only on Cloudflare Workers and needs a KV namespace bound as OAUTH_KV - Open issues of 24 and 28 October 2026 report that a code can be exchanged twice under concurrent requests and that revocation isn't final under KV eventual consistency, with no reply - 1.2.0, a minor release, stopped clients with remote http or private-use redirect URIs authorizing - The consent page and user sign-in are left to the developer's own `/authorize` handler - No audit log of grants or token use is built in ## Before you call it (notes for agents) 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 ## Connect Install: ```bash npm install @cloudflare/workers-oauth-provider ``` Through letme: https://letme.dev/cloudflare-workers-oauth-provider. letme answers with the pick and how to call it direct. How it works: https://www.anchorterminal.com/letme/index.md ## Similar tools Ranked by shared capabilities, then score. Same-category tools with no shared capability key are listed last. | Tool | Grade | Score | Rank | Shared capabilities | x402 | Markdown | | --- | --- | --- | --- | --- | --- | --- | | Descope Agentic Identity Hub | A | 78.1 | 25 | auth.oauth, auth.tokens, auth.consent | no | https://www.anchorterminal.com/tools/descope-agentic-identity.md | | Amazon Bedrock AgentCore Identity | BB | 76.4 | 44 | auth.oauth, auth.tokens, auth.consent | no | https://www.anchorterminal.com/tools/agentcore-identity.md | | Auth0 for AI Agents (Token Vault) | BB | 74.3 | 88 | auth.oauth, auth.tokens, auth.consent | no | https://www.anchorterminal.com/tools/auth0-ai-agents.md | | Scalekit AgentKit | BB | 72.2 | 136 | auth.oauth, auth.tokens, auth.consent | no | https://www.anchorterminal.com/tools/scalekit-agentkit.md | | Vercel Connect | BB | 70.8 | 185 | auth.tokens, auth.oauth, auth.consent | no | https://www.anchorterminal.com/tools/vercel-connect.md | | Aembit | B | 68.4 | 286 | auth.oauth, auth.tokens, auth.consent | no | https://www.anchorterminal.com/tools/aembit.md | ## Panel reviews (0) Reviewed by the Anchor panel (https://www.anchorterminal.com/reviewers/index.md): . Desk reviews, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. For a desk review, the outcome says whether the reviewer's questions could be answered from public material: success, partial or failure. How reviews work: https://www.anchorterminal.com/reviews/how-it-works.md ## Notable - v1.2.4 published to npm on 22 October 2026 with provenance, nine npm releases in the 90 days to 6 November and first published on 16 March 2025 (source: ) - The 1.2.0 changelog entry, a minor release, says clients registered with a remote http redirect URI or a private-use scheme stop authorizing, with an opt-in for RFC 8252 native-app schemes (source: ) - storage-schema.md says client secrets are stored as SHA-256 hashes, props are AES-GCM encrypted and tokens and codes expire through KV TTLs; dynamically registered clients default to 90 days (source: ) - HISTORY.md says the library was largely written with the help of Claude and reviewed line by line by Cloudflare engineers against the RFCs (source: ) - Open issues filed on 24 and 28 October 2026 report that an authorization code can be exchanged twice under concurrent token requests and that grant revocation isn't final under KV eventual consistency, neither with a reply on 6 November (source: ) - Cloudflare's MCP authorization page, last updated 27 October 2026, gives deployable examples with Stytch, Auth0, WorkOS and Descope (source: ) - #4 of 18 in Best auth and delegated access for AI agents: https://www.anchorterminal.com/best/agent-auth/index.md - All 138 agent auth comparisons: https://www.anchorterminal.com/compare/agent-auth/index.md ## Compare - [Aembit vs Cloudflare Workers OAuth Provider](https://www.anchorterminal.com/compare/aembit-vs-cloudflare-workers-oauth-provider.md): B 68.4 vs BB 76.2 - [Amazon Bedrock AgentCore Identity vs Cloudflare Workers OAuth Provider](https://www.anchorterminal.com/compare/agentcore-identity-vs-cloudflare-workers-oauth-provider.md): BB 76.4 vs BB 76.2 - [Arcade.dev vs Cloudflare Workers OAuth Provider](https://www.anchorterminal.com/compare/arcade-vs-cloudflare-workers-oauth-provider.md): B 64 vs BB 76.2 - [Auth0 for AI Agents (Token Vault) vs Cloudflare Workers OAuth Provider](https://www.anchorterminal.com/compare/auth0-ai-agents-vs-cloudflare-workers-oauth-provider.md): BB 74.3 vs BB 76.2 - [Cloudflare Workers OAuth Provider vs Descope Agentic Identity Hub](https://www.anchorterminal.com/compare/cloudflare-workers-oauth-provider-vs-descope-agentic-identity.md): BB 76.2 vs A 78.1 - [Cloudflare Workers OAuth Provider vs Keycard](https://www.anchorterminal.com/compare/cloudflare-workers-oauth-provider-vs-keycard.md): BB 76.2 vs D 49.3 - [Cloudflare Workers OAuth Provider vs Microsoft Entra Agent ID](https://www.anchorterminal.com/compare/cloudflare-workers-oauth-provider-vs-microsoft-entra-agent-id.md): BB 76.2 vs BB 74.5 - [Cloudflare Workers OAuth Provider vs Nango](https://www.anchorterminal.com/compare/cloudflare-workers-oauth-provider-vs-nango.md): BB 76.2 vs B 65.5 - [Cloudflare Workers OAuth Provider vs Scalekit AgentKit](https://www.anchorterminal.com/compare/cloudflare-workers-oauth-provider-vs-scalekit-agentkit.md): BB 76.2 vs BB 72.2 - [Cloudflare Workers OAuth Provider vs Stytch Connected Apps](https://www.anchorterminal.com/compare/cloudflare-workers-oauth-provider-vs-stytch-connected-apps.md): BB 76.2 vs B 63.8 - [Cloudflare Workers OAuth Provider vs Vercel Connect](https://www.anchorterminal.com/compare/cloudflare-workers-oauth-provider-vs-vercel-connect.md): BB 76.2 vs BB 70.8 - [Cloudflare Workers OAuth Provider vs WorkOS Pipes and Agents](https://www.anchorterminal.com/compare/cloudflare-workers-oauth-provider-vs-workos-pipes.md): BB 76.2 vs B 66.4 ## Verify this listing For the vendor. The badge or a plain link to this page verifies the listing, from a page on cloudflare.com or one of its subdomains, or the README at the root of github.com/cloudflare/workers-oauth-provider. It shows the listing is the vendor's and that the vendor knows it's here, and it never changes a grade, rank or review. The vendor sends the page's address to `POST https://www.anchorterminal.com/api/v1/verify` as `{"slug": "cloudflare-workers-oauth-provider", "url": "…"}`, or calls the `verify_listing` tool at https://www.anchorterminal.com/mcp. We fetch the page once, then again every week; two failed checks in a row and the verification lapses, and a later pass restores it. What we check: https://www.anchorterminal.com/builders/index.md#verify HTML badge: ```html Cloudflare Workers OAuth Provider on Anchor Terminal ``` Markdown badge, for a README: ```markdown [![Cloudflare Workers OAuth Provider on Anchor Terminal](https://www.anchorterminal.com/badges/cloudflare-workers-oauth-provider.svg)](https://www.anchorterminal.com/tools/cloudflare-workers-oauth-provider) ``` Plain link: ```html Cloudflare Workers OAuth Provider on Anchor Terminal ``` ## Share this listing For the vendor. Sharing assets for social media, two PNGs of 1200 × 630 that say Cloudflare Workers OAuth Provider is listed on Anchor Terminal, with the vendor's logo and this page's address and no grade or score. - Dark: https://www.anchorterminal.com/assets/share/cloudflare-workers-oauth-provider-dark.png - Light: https://www.anchorterminal.com/assets/share/cloudflare-workers-oauth-provider-light.png --- Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp