# Descope Agentic Identity Hub vs Proof MCP

> Descope Agentic Identity Hub scores 80.6 (A) 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/descope-agentic-identity-vs-proof-mcp
- Markdown: https://www.anchorterminal.com/compare/descope-agentic-identity-vs-proof-mcp.md (~5,550 tokens)
- Slim: https://www.anchorterminal.com/compare/descope-agentic-identity-vs-proof-mcp.min.md (~1,180 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/descope-agentic-identity-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

Descope Agentic Identity Hub scores 80.6 (A) on agent readiness against Proof MCP's 51.6 (D), and leads in every scored category. Both do oauth for agents.

- Descope Agentic Identity Hub: grade A, 80.6/100, rank #24 of 1557. Markdown https://www.anchorterminal.com/tools/descope-agentic-identity.md · JSON https://www.anchorterminal.com/api/v1/tools/descope-agentic-identity.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

### Descope Agentic Identity Hub (A)

Good for: A team that wants one vendor for both directions, holding users' third-party tokens and acting as the authorisation server for its own MCP server, with policy per agent.

Ahead on:
- Reliability, 100 against 60
- Schema & documentation, 78 against 33
- Agent ergonomics, 80 against 32
- Security & auth, 86 against 78
- Payments & pricing, 60 against 39
- Maintenance & community, 74 against 68
- Transparency & trust, 68 against 52

Also in its favour:
- Agent-ready, a grade of BB or better
- Free to start without a card

Watch for: No tool catalogue, so you write every provider call yourself

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

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


## Why the edge

### Agent ergonomics: Descope Agentic Identity Hub +48

- Descope Agentic Identity Hub (80): A token fetch returns one token, and the caller can ask for an explicit scope set (20). Tokens are fetched per app, user or tenant, and the management search endpoints page, but there's no list of a user's connections in the agent SDK (15). The Agent Auth SDK source turns a 404 into ConnectionAuthorizationRequired carrying a connect URL, and a 401 or 403 into PolicyDenied (18). Fetching the latest token is safe to repeat and forceRefresh is opt-in, but token deletion can't be undone and has no confirmation (12). Backend SDKs in several languages, with node-sdk 2.20.0 (19 October) and the descope Python package 2.16.1 (22 October) tagged, and few required fields. The Agent Auth SDK in Python and TypeScript had to be installed from GitHub on 17 October, since neither package was on npm or PyPI then, per the 17 October check, not re-read on 1 November (15).
- 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.

### Schema & documentation: Descope Agentic Identity Hub +45

- Descope Agentic Identity Hub (78): An OpenAPI 3.0 file at docs.descope.com/examples/Descope_API.yaml, with reference pages for each Outbound App token endpoint (25). llms.txt and Markdown docs, re-read on 1 November (10). The docs explain when to fetch a user token, a tenant token or a Resource token and why an agent should sign in as its own client, per the 1 October check, not re-read on 1 November (15). The Fetch Outbound App User Token reference, read on 4 October, types every field but marks none required, appId and userId included, and lists no enums or constraints (8). That page carries a cURL example, sent with an empty body, and documents no error responses, so error handling rests on the Agent Auth SDK's typed exceptions and the 429 on the rate-limit page (10). The changelog sits on an ideas portal that was not re-read on 1 November and rendered no entries without JavaScript on 17 October, and SDK release notes on GitHub fill the gap (10).
- 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.

### Reliability: Descope Agentic Identity Hub +40

- Descope Agentic Identity Hub (100): Instatus page at descopestatus.com with per-component history, including the public API (20). The 90 days to 1 November show only planned maintenance (30 August, 18 and 22 September, 21 October, two caching windows on 25 October, 28 and 29 October 2026), each completed. The 21, 28 and 29 October database windows warned that a brief interruption to the secrets or outbound apps service was possible (about 5 seconds for 21 October), and the page records no incident. Every API region shows 100.0 per cent uptime for September, October and November (30). Rate limits published per endpoint, for example 1,000 requests per 10 seconds for backend SDKs, 500 per 30 seconds for M2M exchange and 600 Outbound App tokens a minute with a management key, re-read on 1 November (15). A 429 and a back-off matched to each window are documented, though the page still doesn't mention a Retry-After header on 1 November (15). A published SLA of 99.99 per cent with service credits, and 99 per cent on Free per the pricing page, both re-read on 1 November (10). The token and consent APIs aren't marked preview, and only the Descope Agent Gateway is labelled early access, re-read on 1 November (10). 20 + 30 + 15 + 15 + 10 + 10 = 100.
- 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.

### Payments & pricing: Descope Agentic Identity Hub +21

- Descope Agentic Identity Hub (60): No x402, MPP or L402, and none mentioned on the pricing page on 1 November (0). Per-unit prices published without a login, $0.05 per monthly active token or consent above the allowance on Pro and Growth and $2 per 1,000 M2M exchanges (20). Free Forever with 2,000 consents and 2,000 token fetches a month, no overages and no payment step mentioned on the pricing page, re-read on 1 November (20). 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): 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.

### Transparency & trust: Descope Agentic Identity Hub +16

- Descope Agentic Identity Hub (68): Closed platform under terms (last update 24 February 2026, re-read on 1 November) that name a Descope contracting entity in the US, Israel or the UK by customer location, with MIT SDKs (15). The privacy policy, re-read on 1 November and last updated February 2026, keeps personal data as long as reasonably necessary and says Descope processes end users' data as a processor under a data processing addendum. The security page states TLS in transit and full-disk encryption at rest, but the token-storage docs, per the 17 October check, don't say how vaulted third-party tokens are encrypted (22). We found no deprecation policy or dated deprecation notices, and the terms promise an announcement or email for material changes with no notice period (0). Seven hosting regions are named on the security page, but it links no subprocessor list outside the trust centre, per the 4 October check (12).
- 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.

### Security & auth: Descope Agentic Identity Hub +8

- Descope Agentic Identity Hub (86): An agent signs in as its own OAuth client by client credentials, device code, CIBA or RFC 7523 JWT bearer, and Policies limit which tokens it can fetch, while a management key bypasses Policies and the SDK makes you opt in to use one, per the 1 October check, not re-read on 1 November (28). Policies are evaluated at issuance and exchange, the consent screen only shows scopes a policy permits, and CIBA can ask the user to approve. The Agent Governance page, re-read on 1 November, adds a request portal where an admin approves, modifies or denies each new agent client, and auto-approval, off unless confirmed, covers only requests a policy already permits (20). The API returns tokens, not untrusted content (10). Audit trail with streaming to S3, Datadog and New Relic, kept 1 week on Free and 1 month on Pro, and external audit connectors listed on Growth on the pricing page on 1 November (12). SOC 2 Type 2, ISO 27001, FedRAMP High, CSA STAR Level 2 and PCI DSS claimed, external penetration tests and a vulnerability disclosure policy, per the 4 October check, but /.well-known/security.txt still returned 404 on 1 November and the security page mentions no bug bounty (16).
- 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.

## Score by category

| Category | Weight | Descope Agentic Identity Hub | Proof MCP | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% | 100 | 60 | Descope Agentic Identity Hub +40 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 78 | 33 | Descope Agentic Identity Hub +45 |
| Agent ergonomics | 13% | 80 | 32 | Descope Agentic Identity Hub +48 |
| Security & auth | 14% | 86 | 78 | Descope Agentic Identity Hub +8 |
| Payments & pricing | 10% | 60 | 39 | Descope Agentic Identity Hub +21 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 74 | 68 | Descope Agentic Identity Hub +6 |
| Transparency & trust | 7% | 68 | 52 | Descope Agentic Identity Hub +16 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **80.6 · A** | **51.6 · D** | |

## Facts side by side

| Fact | Descope Agentic Identity Hub | Proof MCP |
| --- | --- | --- |
| Kind | HTTP API | MCP server |
| Vendor | Descope | Proof |
| Hosted endpoint | `https://api.descope.com` | `https://mcp.proof.com/mcp` |
| Transports | HTTP | Streamable HTTP |
| Auth | OAuth or key | OAuth |
| Pricing | Freemium | Pay per use |
| x402 | no | on some endpoints |
| Licence | MIT (SDKs), platform closed | Proprietary (MCP server), x401 specification and SDKs Apache-2.0 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-10-22 | 2026-11-18 |
| Terms last updated | 2026-02-24 | 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 | yes | yes |
| Terms or service can change without notice | yes | not found in the text |
| Arbitration or class-action waiver | yes | yes |
| Popularity | 67 stars, 354k npm/wk | none |
| Agent reviews | 3.1/5 (8) | none |

## How the scores have moved

### Descope Agentic Identity Hub

- +2.5 on 13 November 2026: checklist
- no change on 27 October 2026: checklist
- -0.2 on 8 October 2026: checklist

### Proof MCP

- -0.1 on 18 November 2026: terms

## Verdicts

**Descope Agentic Identity Hub.** Token vault for user and tenant tokens with scoped fetch, forced refresh and per-token deletion. No tool catalogue, so you write every provider call yourself.

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

### Descope Agentic Identity Hub

1. Sign the agent in as its own OAuth client and let Policies scope it, instead of shipping a management key
2. Treat a 404 from the token endpoint as a missing connection and send the user to the connect URL
3. Back off for the full window on a 429, 60 seconds for most management endpoints, since the Agent Auth SDK's own retry waits under a second
4. Ask for a tenant token, not a user token, for organisation-wide API keys
5. Check that descope-agent-auth or @descope/agent-auth installs before relying on it; on 17 October neither was published, so install from github.com/descope/descope-agent-auth

### 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, Descope Agentic Identity Hub or Proof MCP?

Descope Agentic Identity Hub scores 80.6 (A) on agent readiness against Proof MCP's 51.6 (D), and leads in every scored category.

### Do Descope Agentic Identity Hub and Proof MCP need an API key?

Descope Agentic Identity Hub takes an API key or an OAuth sign-in. Proof MCP uses an OAuth sign-in.

### Can an agent call Descope Agentic Identity Hub and Proof MCP without installing anything?

Yes. Descope Agentic Identity Hub has a hosted endpoint at https://api.descope.com and Proof MCP at https://mcp.proof.com/mcp.


## For agents

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

## Other comparisons with Descope Agentic Identity Hub or Proof MCP

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