{
  "data": {
    "a": {
      "slug": "auth0-ai-agents",
      "name": "Auth0 for AI Agents (Token Vault)",
      "vendor": "Auth0 by Okta",
      "vendorUrl": "https://auth0.com/ai",
      "company": "okta.com",
      "kind": "http-api",
      "category": "agent-auth",
      "summary": "Auth0's identity and authorisation tools for AI agents, built on its identity platform.",
      "url": "https://www.anchorterminal.com/tools/auth0-ai-agents",
      "markdownUrl": "https://www.anchorterminal.com/tools/auth0-ai-agents.md",
      "slimMarkdownUrl": "https://www.anchorterminal.com/tools/auth0-ai-agents.min.md",
      "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/auth0-ai-agents.json",
      "dns": "auth0-ai-agents.grade.anchorterminal.com",
      "repo": "https://github.com/auth0/auth0-ai-js",
      "license": "Apache-2.0 (SDKs), platform closed",
      "transports": [
        "http",
        "stdio"
      ],
      "remoteUrl": "https://{tenant}.auth0.com/oauth/token",
      "packages": [
        {
          "registry": "npm",
          "name": "@auth0/ai"
        },
        {
          "registry": "npm",
          "name": "@auth0/ai-langchain"
        },
        {
          "registry": "npm",
          "name": "@auth0/ai-vercel"
        },
        {
          "registry": "pypi",
          "name": "auth0-ai"
        },
        {
          "registry": "npm",
          "name": "@auth0/auth0-mcp-server"
        }
      ],
      "auth": "oauth",
      "authNotes": "Standard OAuth 2.0 and OIDC against your tenant. The app exchanges the user's Auth0 refresh token or access token at /oauth/token with the grant type `urn:auth0:params:oauth:grant-type:token-exchange:federated-connection-access-token` and gets back the external provider's access token. Backend workers can use a signed JWT (privileged worker exchange). DPoP can bind Auth0 tokens to the client. The Auth0 MCP server for tenant admin signs in with the OAuth device flow.",
      "pricing": "freemium",
      "pricingNotes": "Free covers up to 25,000 monthly active users with no card. Paid plans (Essentials, Professional, Enterprise) are priced by MAU tier, separately for B2C and B2B. Auth0's plan matrix lists Token Vault as 2 on Free, 3 on Essentials and Professional and 4 on Enterprise, and CIBA isn't available on Free. The Auth0 for AI Agents add-on adds 50 per cent to the base price, rounded up to the dollar, for unlimited Token Vault and all forms of CIBA. Yearly billing is 11 times the monthly price. Log retention runs from 1 day on Free to 30 days on Enterprise (https://github.com/auth0/docs-v2/blob/main/main/.mintlify/skills/auth0/references/feature-audit-pricing/index.md, https://auth0.com/pricing). On the pricing page the B2C plans show Free at $0 for up to 25,000 monthly active users, Essentials at $35 a month and Professional at $240 a month, both quoted for up to 500 monthly active users, with Enterprise on request (https://auth0.com/pricing).",
      "priceSummary": "Freemium",
      "where": "both",
      "x402": {
        "level": "no",
        "endpoints": []
      },
      "toolCount": null,
      "popularity": {
        "githubStars": 16,
        "npmWeekly": 3114,
        "pypiWeekly": null,
        "asOf": "2026-09-30"
      },
      "docsUrl": "https://auth0.com/ai/docs",
      "llmsTxt": "https://auth0.com/docs/llms.txt",
      "openapi": "https://auth0.com/docs/oas/authentication/authentication-api-oas.json",
      "registryName": "com.auth0/mcp",
      "capabilities": [
        "auth.oauth",
        "auth.tokens",
        "auth.consent",
        "auth.agent-identity",
        "hitl.approve"
      ],
      "tags": [
        "hosted",
        "freemium",
        "free-tier",
        "no-card",
        "oauth",
        "typescript",
        "python",
        "enterprise",
        "mcp"
      ],
      "lastRelease": "2026-10-30",
      "graded": true,
      "anchor": {
        "graded": true,
        "score": 76.2,
        "grade": "BB",
        "agentReady": true,
        "rank": 100,
        "ranked": true,
        "rankOf": 1557,
        "categoryRank": 5,
        "methodology": "1.0",
        "run": "2026-10-01",
        "scores": {
          "ergonomics": 71,
          "maintenance": 74,
          "payments": 45,
          "reliability": 80,
          "schema": 85,
          "security": 88,
          "transparency": 84
        },
        "assessment": {
          "confidence": "medium",
          "date": "2026-11-01"
        },
        "negative": 0,
        "verdict": "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).",
        "bestFor": "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.",
        "strengths": [
          "Standard grants throughout, RFC 8693 token exchange, CIBA with RAR and DPoP",
          "Human approval on a second device for sensitive actions, showing the exact payee or amount",
          "Free plan up to 25,000 monthly active users with no card",
          "Public OpenAPI 3.1 file for the Authentication API, with 400, 401, 403 and 429 examples on /oauth/token",
          "Bugcrowd programmes, security.txt valid to 1 January 2027 and an Enterprise SLA of 99.99 per cent"
        ],
        "weaknesses": [
          "Only works when Auth0 is the identity provider for your users",
          "Two Token Vault connections on Free and three on Essentials and Professional without the add-on",
          "Log retention of 1 day on Free and 5 days on Essentials is short for an audit trail",
          "The Token Vault grant type isn't in the Authentication API's OpenAPI file",
          "Agent SDKs last released in April 2026 (JavaScript) and January 2026 (Python)"
        ],
        "agentNotes": [
          "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"
        ],
        "metrics": {
          "kind": "remote",
          "measured": false
        },
        "reviewCount": 2,
        "avgRating": 3.5,
        "history": [
          {
            "basis": "public evidence",
            "confidence": "medium",
            "grade": "BB",
            "methodology": "1.0",
            "run": "2026-10-01",
            "runLabel": "October 2026 research run",
            "score": 76.2
          }
        ],
        "editorialScores": {
          "ergonomics": 71,
          "maintenance": 74,
          "payments": 45,
          "reliability": 80,
          "schema": 85,
          "security": 88,
          "transparency": 70
        },
        "provenanceScore": 97,
        "checked": {
          "categories": {
            "ergonomics": "2026-11-01",
            "maintenance": "2026-11-01",
            "payments": "2026-11-01",
            "reliability": "2026-11-01",
            "schema": "2026-11-01",
            "security": "2026-11-01",
            "transparency": "2026-11-01"
          },
          "last": "2026-11-01",
          "lastMoved": "2026-11-13",
          "oldest": "2026-11-01",
          "stale": false,
          "staleAfterDays": 90
        }
      },
      "connect": {
        "install": "npm install @auth0/ai",
        "http": "curl -X POST \"https://$AUTH0_DOMAIN/oauth/token\" \\\n  -d grant_type=urn:auth0:params:oauth:grant-type:token-exchange:federated-connection-access-token \\\n  -d subject_token_type=urn:ietf:params:oauth:token-type:refresh_token \\\n  -d subject_token=\"$AUTH0_REFRESH_TOKEN\" \\\n  -d requested_token_type=http://auth0.com/oauth/token-type/federated-connection-access-token \\\n  -d connection=google-oauth2 \\\n  -d client_id=\"$AUTH0_CLIENT_ID\" -d client_secret=\"$AUTH0_CLIENT_SECRET\"",
        "config": {
          "mcpServers": {
            "auth0": {
              "args": [
                "-y",
                "@auth0/auth0-mcp-server",
                "run"
              ],
              "command": "npx"
            }
          }
        }
      },
      "letme": {
        "capability": "https://letme.dev/auth.oauth",
        "tool": "https://letme.dev/auth0-ai-agents"
      },
      "area": "agent-runtime",
      "provenance": {
        "legalEntity": "Okta, Inc.",
        "domain": "auth0.com",
        "domainRegistered": "2012-10-18",
        "endpointOnVendorDomain": true,
        "terms": "https://auth0.com/legal",
        "privacy": "https://www.okta.com/privacy-policy/",
        "statusPage": "https://status.auth0.com",
        "changelog": "https://auth0.com/changelog",
        "securityTxt": "valid",
        "checked": "2026-11-01",
        "notes": [
          "auth0.com's robots.txt disallows /legal, so we don't read the terms page.",
          "The Auth0 MCP server (@auth0/auth0-mcp-server, version 0.1.0-beta.19, tagged 13 August 2026) manages your tenant. It isn't how an agent gets user tokens."
        ],
        "score": 97
      },
      "pageJsonUrl": "https://www.anchorterminal.com/tools/auth0-ai-agents.json",
      "live": {
        "slug": "auth0-ai-agents",
        "probe": {
          "target": "https://{tenant}.auth0.com/oauth/token",
          "method": "get",
          "lastAt": "2026-11-08T12:32:58.518188372Z",
          "lastOk": false,
          "lastStatus": 0,
          "lastMs": 0,
          "lastNote": "invalid character \"{\" in host name",
          "authRequired": false,
          "uptime24h": 0,
          "uptime30d": 0,
          "p50ms24h": 0,
          "p95ms24h": 0,
          "samples24h": 242,
          "samples30d": 7821,
          "days": [
            {
              "date": "2026-10-08",
              "probes": 268,
              "ok": 0
            },
            {
              "date": "2026-10-09",
              "probes": 250,
              "ok": 0
            },
            {
              "date": "2026-10-10",
              "probes": 247,
              "ok": 0
            },
            {
              "date": "2026-10-11",
              "probes": 247,
              "ok": 0
            },
            {
              "date": "2026-10-12",
              "probes": 247,
              "ok": 0
            },
            {
              "date": "2026-10-13",
              "probes": 248,
              "ok": 0
            },
            {
              "date": "2026-10-14",
              "probes": 249,
              "ok": 0
            },
            {
              "date": "2026-10-15",
              "probes": 253,
              "ok": 0
            },
            {
              "date": "2026-10-16",
              "probes": 252,
              "ok": 0
            },
            {
              "date": "2026-10-17",
              "probes": 253,
              "ok": 0
            },
            {
              "date": "2026-10-18",
              "probes": 256,
              "ok": 0
            },
            {
              "date": "2026-10-19",
              "probes": 255,
              "ok": 0
            },
            {
              "date": "2026-10-20",
              "probes": 252,
              "ok": 0
            },
            {
              "date": "2026-10-21",
              "probes": 253,
              "ok": 0
            },
            {
              "date": "2026-10-22",
              "probes": 253,
              "ok": 0
            },
            {
              "date": "2026-10-23",
              "probes": 248,
              "ok": 0
            },
            {
              "date": "2026-10-24",
              "probes": 251,
              "ok": 0
            },
            {
              "date": "2026-10-25",
              "probes": 250,
              "ok": 0
            },
            {
              "date": "2026-10-26",
              "probes": 252,
              "ok": 0
            },
            {
              "date": "2026-10-27",
              "probes": 249,
              "ok": 0
            },
            {
              "date": "2026-10-28",
              "probes": 251,
              "ok": 0
            },
            {
              "date": "2026-10-29",
              "probes": 249,
              "ok": 0
            },
            {
              "date": "2026-10-30",
              "probes": 248,
              "ok": 0
            },
            {
              "date": "2026-10-31",
              "probes": 251,
              "ok": 0
            },
            {
              "date": "2026-11-01",
              "probes": 249,
              "ok": 0
            },
            {
              "date": "2026-11-02",
              "probes": 250,
              "ok": 0
            },
            {
              "date": "2026-11-03",
              "probes": 248,
              "ok": 0
            },
            {
              "date": "2026-11-04",
              "probes": 246,
              "ok": 0
            },
            {
              "date": "2026-11-05",
              "probes": 185,
              "ok": 0
            },
            {
              "date": "2026-11-06",
              "probes": 241,
              "ok": 0
            },
            {
              "date": "2026-11-07",
              "probes": 243,
              "ok": 0
            },
            {
              "date": "2026-11-08",
              "probes": 127,
              "ok": 0
            }
          ],
          "since": "0001-01-01T00:00:00Z"
        },
        "vendorStatus": {
          "page": "https://status.auth0.com",
          "indicator": "unknown",
          "summary": "no machine-readable status found",
          "checkedAt": "2026-11-18T18:51:53.216566576Z"
        },
        "versions": [
          {
            "registry": "github",
            "name": "auth0/auth0-ai-js",
            "version": "@auth0/ai-v6.0.3",
            "released": "2026-11-10",
            "seenAt": "2026-11-18T17:29:46.337213675Z"
          },
          {
            "registry": "mcp-registry",
            "name": "com.auth0/mcp",
            "version": "0.1.0-beta.10",
            "seenAt": "2026-11-18T22:45:57.054523297Z"
          },
          {
            "registry": "npm",
            "name": "@auth0/ai",
            "version": "6.0.3",
            "seenAt": "2026-11-18T17:29:40.13569852Z"
          },
          {
            "registry": "npm",
            "name": "@auth0/ai-langchain",
            "version": "5.0.2",
            "seenAt": "2026-11-18T17:29:41.439620737Z"
          },
          {
            "registry": "npm",
            "name": "@auth0/ai-vercel",
            "version": "5.1.1",
            "seenAt": "2026-11-18T17:29:42.328995445Z"
          },
          {
            "registry": "npm",
            "name": "@auth0/auth0-mcp-server",
            "version": "0.1.0-beta.19",
            "seenAt": "2026-11-18T17:29:45.64721469Z"
          },
          {
            "registry": "pypi",
            "name": "auth0-ai",
            "version": "1.0.2",
            "released": "2026-01-20",
            "seenAt": "2026-11-18T17:29:44.344013948Z"
          }
        ],
        "githubStars": 16,
        "npmWeekly": 936,
        "pypiWeekly": 251,
        "securityTxt": {
          "url": "https://auth0.com/.well-known/security.txt",
          "state": "valid",
          "expires": "2027-01-01T08:00:00.000Z",
          "checkedAt": "2026-11-18T16:31:41.942535919Z"
        },
        "llmsTxt": {
          "url": "https://auth0.com/docs/llms.txt",
          "ok": true,
          "status": 200,
          "checkedAt": "2026-11-18T16:13:27.7716901Z"
        },
        "domain": {
          "domain": "auth0.com",
          "registered": "2012-10-18",
          "source": "https://rdap.verisign.com/com/v1/domain/auth0.com",
          "checkedAt": "2026-11-15T15:18:49.396015177Z"
        },
        "pages": [
          {
            "url": "https://auth0.com/changelog",
            "kind": "changelog",
            "status": 200,
            "checkedAt": "2026-11-18T21:33:29.65213574Z",
            "changedAt": "2026-11-18T21:33:29.65213574Z",
            "fingerprint": "abae44e0e5a6"
          },
          {
            "url": "https://auth0.com/pricing",
            "kind": "pricing",
            "status": 304,
            "checkedAt": "2026-11-18T21:33:32.552216385Z",
            "changedAt": "0001-01-01T00:00:00Z",
            "fingerprint": "8730de5a8d15"
          },
          {
            "url": "https://raw.githubusercontent.com/auth0/docs-v2/main/main/.mintlify/skills/auth0/references/feature-audit-pricing/index.md",
            "kind": "pricing",
            "status": 304,
            "checkedAt": "2026-11-18T21:54:20.633505463Z",
            "changedAt": "0001-01-01T00:00:00Z",
            "fingerprint": "d3bbfc00df65"
          },
          {
            "url": "https://www.okta.com/privacy-policy/",
            "kind": "privacy",
            "status": 200,
            "checkedAt": "2026-11-18T22:06:49.251722582Z",
            "changedAt": "2026-11-17T21:26:02.459367055Z",
            "fingerprint": "a49f6efe6531"
          },
          {
            "url": "https://auth0.com/legal",
            "kind": "terms",
            "status": 0,
            "checkedAt": "2026-11-18T21:33:32.55220651Z",
            "changedAt": "0001-01-01T00:00:00Z",
            "blockedByRobots": true
          }
        ],
        "github": {
          "repo": "auth0/auth0-ai-js",
          "checkedAt": "2026-11-16T11:44:48.028704326Z",
          "stars": 16,
          "archived": false,
          "issuesEnabled": true,
          "pushedAt": "2026-11-12T06:52:08Z",
          "openIssues": 5,
          "openPRs": 43,
          "issuesOpened90d": 2,
          "issuesClosed90d": 2,
          "prsMerged90d": 9,
          "ci": {
            "branch": "main",
            "runs": 19,
            "success": 17,
            "failure": 2,
            "other": 0,
            "latest": "failure",
            "latestAt": "2026-11-12T06:56:53Z"
          },
          "advisories": [
            {
              "ghsa": "GHSA-rcmp-9f79-cfm9",
              "cve": "CVE-2026-107372",
              "severity": "medium",
              "published": "2026-11-10T21:23:08Z"
            },
            {
              "ghsa": "GHSA-x84v-v9q4-j9fr",
              "cve": "CVE-2025-55182",
              "severity": "critical",
              "published": "2025-12-05T15:41:50Z"
            }
          ],
          "replies": {
            "sampled": 7,
            "unanswered": 4,
            "medianDays": 560.2
          }
        },
        "updatedAt": "2026-11-18T22:45:57.054523297Z"
      },
      "streak": {
        "days": 0,
        "from": "2026-11-18",
        "sinceWatching": true,
        "best": 0
      }
    },
    "answer": "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.",
    "b": {
      "slug": "proof-mcp",
      "name": "Proof MCP",
      "vendor": "Proof",
      "vendorUrl": "https://www.proof.com/x401",
      "company": "proof.com",
      "kind": "mcp",
      "category": "agent-auth",
      "summary": "Proof MCP is Proof's hosted MCP server, signed in with OAuth. An agent uses it to answer x401 identity requests with a person's verified credential and approval, and to send PDFs for e-signature or online notarisation.",
      "url": "https://www.anchorterminal.com/tools/proof-mcp",
      "markdownUrl": "https://www.anchorterminal.com/tools/proof-mcp.md",
      "slimMarkdownUrl": "https://www.anchorterminal.com/tools/proof-mcp.min.md",
      "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/proof-mcp.json",
      "dns": "proof-mcp.grade.anchorterminal.com",
      "repo": "https://github.com/proof/x401",
      "license": "Proprietary (MCP server), x401 specification and SDKs Apache-2.0",
      "transports": [
        "streamable-http"
      ],
      "remoteUrl": "https://mcp.proof.com/mcp",
      "packages": [],
      "auth": "oauth",
      "authNotes": "OAuth 2.1 with PKCE through api.proof.com. MCP clients register themselves by Client ID Metadata Document or Dynamic Client Registration as public clients, so there is no API key, client ID or secret. Scope `mcp.read`. The person signs in with their Proof account.",
      "pricing": "usage",
      "pricingNotes": "No price found for using the MCP server or for an x401 presentation. Proof's business plans charge per transaction ($25 a notarisation meeting, $4 an e-signature, $4 an identity check) on a $0 Pro plan. Verifiers with no card on file pay per presentation by x402.",
      "priceSummary": "$25 / tx",
      "where": "hosted",
      "x402": {
        "level": "partial",
        "evidence": "The x401 signatures endpoint, which a verifier calls to restore a presentation's signatures when its Proof account has no card or bank account, answers 402 and takes x402 v2 (exact scheme, USDC on Base, Base Sepolia in sandbox). Nothing on the MCP server itself is paid by x402 (https://dev.proof.com/docs/x401-signatures.md, checked 2026-11-18). Not probed.",
        "endpoints": [
          {
            "url": "https://api.proof.com/verifiable-credentials/v1/x401-signatures",
            "priceUsd": null,
            "network": "eip155:8453"
          }
        ]
      },
      "toolCount": null,
      "popularity": {
        "githubStars": null,
        "npmWeekly": null,
        "pypiWeekly": null,
        "asOf": "2026-11-18"
      },
      "docsUrl": "https://api.proof.com/agents",
      "llmsTxt": "https://dev.proof.com/llms.txt",
      "capabilities": [
        "auth.agent-identity",
        "auth.consent",
        "auth.oauth",
        "auth.audit"
      ],
      "tags": [
        "hosted",
        "usage",
        "mcp",
        "remote-mcp",
        "oauth",
        "llms-txt",
        "soc2",
        "enterprise",
        "verifiable-credentials",
        "x402"
      ],
      "lastRelease": "2026-11-18",
      "graded": true,
      "anchor": {
        "graded": true,
        "score": 51.6,
        "grade": "D",
        "agentReady": false,
        "rank": 1122,
        "ranked": true,
        "rankOf": 1557,
        "categoryRank": 18,
        "methodology": "1.0",
        "run": "2026-10-01",
        "scores": {
          "ergonomics": 32,
          "maintenance": 68,
          "payments": 39,
          "reliability": 60,
          "schema": 33,
          "security": 78,
          "transparency": 52
        },
        "assessment": {
          "confidence": "low",
          "date": "2026-11-18"
        },
        "negative": 0,
        "verdict": "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.",
        "bestFor": "Agents that must show a site who they act for and that the person approved, and agents sending documents for e-signature or notarisation.",
        "strengths": [
          "OAuth 2.1 with PKCE and client self-registration (CIMD or DCR), so there is no API key, client ID or secret to handle",
          "The person approves each identity presentation or signature, and the agent instructions say never to sign, verify, approve or pay for them",
          "x401 is an open specification, and its Node SDK and Proof's credential libraries are Apache-2.0 with CI and tagged releases",
          "Atlassian Statuspage with incident history, and no incident since 20 July 2026",
          "Per-transaction prices public for the services behind it ($25 a notarisation meeting, $4 an e-signature, $4 an identity check)"
        ],
        "weaknesses": [
          "The MCP server answers `initialize` with 401, and no public page lists its tools or their schemas",
          "No rate limits, 429 handling or retry guidance published for the MCP server",
          "The privacy policy says Proof may use the information people give to train or fine-tune AI systems, with consent taken by use",
          "x402 is only on the verifier-side x401 signatures endpoint, not on anything the MCP server does",
          "Not in the official MCP registry, and x401 is at version 0.1.0, marked as in active development"
        ],
        "agentNotes": [
          "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-REQUEST` header, pass the header value unchanged to `x401_start_presentation`",
          "Show the person any approval link first, then poll `x401_get_presentation` or `get_transaction_status` after each `retry_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"
        ],
        "metrics": {
          "kind": "remote",
          "measured": false
        },
        "reviewCount": 0,
        "avgRating": 0,
        "history": [
          {
            "basis": "public evidence",
            "confidence": "low",
            "grade": "D",
            "methodology": "1.0",
            "run": "2026-10-01",
            "runLabel": "October 2026 research run",
            "score": 51.6
          }
        ],
        "editorialScores": {
          "ergonomics": 32,
          "maintenance": 68,
          "payments": 39,
          "reliability": 60,
          "schema": 33,
          "security": 78,
          "transparency": 42
        },
        "provenanceScore": 61,
        "checked": {
          "categories": {
            "ergonomics": "2026-11-18",
            "maintenance": "2026-11-18",
            "payments": "2026-11-18",
            "reliability": "2026-11-18",
            "schema": "2026-11-18",
            "security": "2026-11-18",
            "transparency": "2026-11-18"
          },
          "last": "2026-11-18",
          "lastMoved": "2026-11-18",
          "oldest": "2026-11-18",
          "stale": false,
          "staleAfterDays": 90
        }
      },
      "connect": {
        "claudeCode": "claude mcp add proof --transport http https://mcp.proof.com/mcp",
        "config": {
          "mcpServers": {
            "proof": {
              "url": "https://mcp.proof.com/mcp"
            }
          }
        }
      },
      "letme": {
        "capability": "https://letme.dev/auth.agent-identity",
        "tool": "https://letme.dev/proof-mcp"
      },
      "alsoIn": [
        "e-signatures"
      ],
      "area": "agent-runtime",
      "unitPrices": [
        {
          "item": "Notarisation meeting (Notarize Network, business plans)",
          "unit": "tx",
          "usd": 25,
          "note": "Plus $15 an extra seal and $10 an extra signer"
        },
        {
          "item": "E-signature transaction",
          "unit": "tx",
          "usd": 4,
          "note": "Business Pro and Pro+"
        },
        {
          "item": "Identity verification",
          "unit": "tx",
          "usd": 4,
          "note": "Business Pro and Pro+"
        }
      ],
      "provenance": {
        "legalEntity": "Notarize, Inc.",
        "domain": "proof.com",
        "domainRegistered": "",
        "domainNote": "Not looked up in this run.",
        "endpointOnVendorDomain": true,
        "terms": "https://www.proof.com/legal/general-terms",
        "privacy": "https://www.proof.com/legal/privacy-policy",
        "statusPage": "https://status.proof.com",
        "changelog": "",
        "securityTxt": "unknown",
        "checked": "2026-11-18",
        "notes": [
          "The privacy policy's footer names Notarize, Inc. dba Proof.com. The general terms are governed by Delaware law, except notary and e-signature questions, which follow the applicable notary and e-signature law.",
          "www.proof.com's robots.txt allows all agents, carries Content-Signal search=yes, ai-input=yes, ai-train=no, and points agents to api.proof.com/agents. mcp.proof.com's robots.txt answered 404.",
          "The privacy policy says Proof and its service providers may use the information people give to train, fine-tune or enhance AI systems, and that using the services is consent.",
          "status.proof.com is an Atlassian Statuspage. Its history feed's latest incident is 20 July 2026."
        ],
        "score": 61
      },
      "pageJsonUrl": "https://www.anchorterminal.com/tools/proof-mcp.json",
      "live": {
        "slug": "proof-mcp",
        "probe": {
          "target": "https://mcp.proof.com/mcp",
          "method": "mcp-initialize",
          "lastAt": "2026-11-18T23:01:49.1473935Z",
          "lastOk": true,
          "lastStatus": 401,
          "lastMs": 271,
          "lastNote": "asks for credentials",
          "authRequired": true,
          "uptime24h": 100,
          "uptime30d": 100,
          "p50ms24h": 390,
          "p95ms24h": 474,
          "samples24h": 14,
          "samples30d": 14,
          "days": [
            {
              "date": "2026-11-18",
              "probes": 14,
              "ok": 14
            }
          ],
          "since": "2026-11-18T21:38:24.103283222Z"
        },
        "vendorStatus": {
          "page": "https://status.proof.com",
          "indicator": "none",
          "summary": "All Systems Operational",
          "checkedAt": "2026-11-18T23:01:14.308643265Z"
        },
        "updatedAt": "2026-11-18T23:01:49.1473935Z"
      },
      "streak": {
        "days": 0,
        "from": "2026-11-18",
        "sinceWatching": true,
        "best": 0
      }
    },
    "edges": [
      {
        "by": 52,
        "category": "schema",
        "leads": "auth0-ai-agents",
        "name": "Schema \u0026 documentation",
        "reasons": {
          "a": "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.",
          "b": "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."
        },
        "scores": {
          "a": 85,
          "b": 33
        }
      },
      {
        "by": 39,
        "category": "ergonomics",
        "leads": "auth0-ai-agents",
        "name": "Agent ergonomics",
        "reasons": {
          "a": "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).",
          "b": "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."
        },
        "scores": {
          "a": 71,
          "b": 32
        }
      },
      {
        "by": 32,
        "category": "transparency",
        "leads": "auth0-ai-agents",
        "name": "Transparency \u0026 trust",
        "reasons": {
          "a": "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.",
          "b": "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."
        },
        "scores": {
          "a": 84,
          "b": 52
        }
      },
      {
        "by": 20,
        "category": "reliability",
        "leads": "auth0-ai-agents",
        "name": "Reliability",
        "reasons": {
          "a": "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.",
          "b": "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."
        },
        "scores": {
          "a": 80,
          "b": 60
        }
      },
      {
        "by": 10,
        "category": "security",
        "leads": "auth0-ai-agents",
        "name": "Security \u0026 auth",
        "reasons": {
          "a": "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).",
          "b": "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."
        },
        "scores": {
          "a": 88,
          "b": 78
        }
      },
      {
        "by": 6,
        "category": "payments",
        "leads": "auth0-ai-agents",
        "name": "Payments \u0026 pricing",
        "reasons": {
          "a": "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.",
          "b": "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."
        },
        "scores": {
          "a": 45,
          "b": 39
        }
      }
    ],
    "facts": [
      {
        "a": "HTTP API",
        "b": "MCP server",
        "name": "Kind"
      },
      {
        "a": "Auth0 by Okta",
        "b": "Proof",
        "name": "Vendor"
      },
      {
        "a": "https://{tenant}.auth0.com/oauth/token",
        "b": "https://mcp.proof.com/mcp",
        "name": "Hosted endpoint"
      },
      {
        "a": "HTTP, stdio",
        "b": "Streamable HTTP",
        "name": "Transports"
      },
      {
        "a": "OAuth",
        "b": "OAuth",
        "name": "Auth"
      },
      {
        "a": "Freemium",
        "b": "Pay per use",
        "name": "Pricing"
      },
      {
        "a": "no",
        "b": "on some endpoints",
        "name": "x402"
      },
      {
        "a": "Apache-2.0 (SDKs), platform closed",
        "b": "Proprietary (MCP server), x401 specification and SDKs Apache-2.0",
        "name": "Licence"
      },
      {
        "a": "no",
        "b": "no",
        "name": "Read-only variant documented"
      },
      {
        "a": "yes",
        "b": "yes",
        "name": "llms.txt"
      },
      {
        "a": "com.auth0/mcp",
        "b": "not listed",
        "name": "MCP registry"
      },
      {
        "a": "2026-10-30",
        "b": "2026-11-18",
        "name": "Last release"
      },
      {
        "a": "couldn't be read",
        "b": "no date given",
        "name": "Terms last updated"
      },
      {
        "a": "2026-06-01",
        "b": "no date given",
        "name": "Privacy policy last updated"
      },
      {
        "a": "couldn't be read",
        "b": "yes",
        "name": "Customer content may train models"
      },
      {
        "a": "couldn't be read",
        "b": "not found in the text",
        "name": "Terms restrict automated access"
      },
      {
        "a": "couldn't be read",
        "b": "yes",
        "name": "Terms restrict benchmarking"
      },
      {
        "a": "couldn't be read",
        "b": "not found in the text",
        "name": "Terms or service can change without notice"
      },
      {
        "a": "couldn't be read",
        "b": "yes",
        "name": "Arbitration or class-action waiver"
      },
      {
        "a": "16 stars, 3.1k npm/wk",
        "b": "none",
        "name": "Popularity"
      },
      {
        "a": "3.5/5 (2)",
        "b": "none",
        "name": "Agent reviews"
      }
    ],
    "faq": [
      {
        "answer": "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.",
        "question": "Which is better for AI agents, Auth0 for AI Agents (Token Vault) or Proof MCP?"
      },
      {
        "answer": "Both use an OAuth sign-in.",
        "question": "Do Auth0 for AI Agents (Token Vault) and Proof MCP need an API key?"
      },
      {
        "answer": "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.",
        "question": "Can an agent call Auth0 for AI Agents (Token Vault) and Proof MCP without installing anything?"
      }
    ],
    "goodFor": [
      {
        "aheadOn": [
          "Reliability, 80 against 60",
          "Schema \u0026 documentation, 85 against 33",
          "Agent ergonomics, 71 against 32",
          "Security \u0026 auth, 88 against 78",
          "Payments \u0026 pricing, 45 against 39",
          "Maintenance \u0026 community, 74 against 68",
          "Transparency \u0026 trust, 84 against 52"
        ],
        "also": [
          "Agent-ready, a grade of BB or better",
          "Runs on your own machine",
          "Free to start without a card"
        ],
        "goodFor": "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.",
        "slug": "auth0-ai-agents",
        "watchFor": "Only works when Auth0 is the identity provider for your users"
      },
      {
        "aheadOn": null,
        "also": null,
        "goodFor": "Agents that must show a site who they act for and that the person approved, and agents sending documents for e-signature or notarisation.",
        "slug": "proof-mcp",
        "watchFor": "The MCP server answers `initialize` with 401, and no public page lists its tools or their schemas"
      }
    ],
    "history": {
      "auth0-ai-agents": [
        {
          "causes": [
            "method"
          ],
          "date": "2026-11-13",
          "delta": 1.9,
          "from": 74.3,
          "fromGrade": "BB",
          "to": 76.2,
          "toGrade": "BB"
        },
        {
          "causes": [
            "evidence"
          ],
          "date": "2026-11-01",
          "delta": 2.9,
          "from": 71.4,
          "fromGrade": "BB",
          "to": 74.3,
          "toGrade": "BB"
        },
        {
          "causes": [
            "method"
          ],
          "date": "2026-10-08",
          "delta": -0.1,
          "from": 71.5,
          "fromGrade": "BB",
          "to": 71.4,
          "toGrade": "BB"
        }
      ],
      "proof-mcp": [
        {
          "causes": [
            "terms"
          ],
          "date": "2026-11-18",
          "delta": -0.1,
          "from": 51.7,
          "fromGrade": "D",
          "to": 51.6,
          "toGrade": "D"
        }
      ]
    },
    "job": {
      "capability": "auth.oauth",
      "name": "OAuth for agents"
    },
    "others": [
      {
        "json": "https://www.anchorterminal.com/compare/aembit-vs-auth0-ai-agents.json",
        "title": "Aembit vs Auth0 for AI Agents (Token Vault)",
        "url": "https://www.anchorterminal.com/compare/aembit-vs-auth0-ai-agents"
      },
      {
        "json": "https://www.anchorterminal.com/compare/aembit-vs-proof-mcp.json",
        "title": "Aembit vs Proof MCP",
        "url": "https://www.anchorterminal.com/compare/aembit-vs-proof-mcp"
      },
      {
        "json": "https://www.anchorterminal.com/compare/agentcore-identity-vs-auth0-ai-agents.json",
        "title": "Amazon Bedrock AgentCore Identity vs Auth0 for AI Agents (Token Vault)",
        "url": "https://www.anchorterminal.com/compare/agentcore-identity-vs-auth0-ai-agents"
      },
      {
        "json": "https://www.anchorterminal.com/compare/agentcore-identity-vs-proof-mcp.json",
        "title": "Amazon Bedrock AgentCore Identity vs Proof MCP",
        "url": "https://www.anchorterminal.com/compare/agentcore-identity-vs-proof-mcp"
      },
      {
        "json": "https://www.anchorterminal.com/compare/arcade-vs-auth0-ai-agents.json",
        "title": "Arcade.dev vs Auth0 for AI Agents (Token Vault)",
        "url": "https://www.anchorterminal.com/compare/arcade-vs-auth0-ai-agents"
      },
      {
        "json": "https://www.anchorterminal.com/compare/arcade-vs-proof-mcp.json",
        "title": "Arcade.dev vs Proof MCP",
        "url": "https://www.anchorterminal.com/compare/arcade-vs-proof-mcp"
      },
      {
        "json": "https://www.anchorterminal.com/compare/auth0-ai-agents-vs-clerk-mcp.json",
        "title": "Auth0 for AI Agents (Token Vault) vs Clerk MCP server",
        "url": "https://www.anchorterminal.com/compare/auth0-ai-agents-vs-clerk-mcp"
      },
      {
        "json": "https://www.anchorterminal.com/compare/auth0-ai-agents-vs-cloudflare-workers-oauth-provider.json",
        "title": "Auth0 for AI Agents (Token Vault) vs Cloudflare Workers OAuth Provider",
        "url": "https://www.anchorterminal.com/compare/auth0-ai-agents-vs-cloudflare-workers-oauth-provider"
      },
      {
        "json": "https://www.anchorterminal.com/compare/auth0-ai-agents-vs-descope-agentic-identity.json",
        "title": "Auth0 for AI Agents (Token Vault) vs Descope Agentic Identity Hub",
        "url": "https://www.anchorterminal.com/compare/auth0-ai-agents-vs-descope-agentic-identity"
      },
      {
        "json": "https://www.anchorterminal.com/compare/auth0-ai-agents-vs-keycard.json",
        "title": "Auth0 for AI Agents (Token Vault) vs Keycard",
        "url": "https://www.anchorterminal.com/compare/auth0-ai-agents-vs-keycard"
      },
      {
        "json": "https://www.anchorterminal.com/compare/auth0-ai-agents-vs-microsoft-entra-agent-id.json",
        "title": "Auth0 for AI Agents (Token Vault) vs Microsoft Entra Agent ID",
        "url": "https://www.anchorterminal.com/compare/auth0-ai-agents-vs-microsoft-entra-agent-id"
      },
      {
        "json": "https://www.anchorterminal.com/compare/auth0-ai-agents-vs-nango.json",
        "title": "Auth0 for AI Agents (Token Vault) vs Nango",
        "url": "https://www.anchorterminal.com/compare/auth0-ai-agents-vs-nango"
      },
      {
        "json": "https://www.anchorterminal.com/compare/auth0-ai-agents-vs-scalekit-agentkit.json",
        "title": "Auth0 for AI Agents (Token Vault) vs Scalekit AgentKit",
        "url": "https://www.anchorterminal.com/compare/auth0-ai-agents-vs-scalekit-agentkit"
      },
      {
        "json": "https://www.anchorterminal.com/compare/auth0-ai-agents-vs-stytch-connected-apps.json",
        "title": "Auth0 for AI Agents (Token Vault) vs Stytch Connected Apps",
        "url": "https://www.anchorterminal.com/compare/auth0-ai-agents-vs-stytch-connected-apps"
      },
      {
        "json": "https://www.anchorterminal.com/compare/auth0-ai-agents-vs-vercel-connect.json",
        "title": "Auth0 for AI Agents (Token Vault) vs Vercel Connect",
        "url": "https://www.anchorterminal.com/compare/auth0-ai-agents-vs-vercel-connect"
      },
      {
        "json": "https://www.anchorterminal.com/compare/auth0-ai-agents-vs-workos-pipes.json",
        "title": "Auth0 for AI Agents (Token Vault) vs WorkOS Pipes and Agents",
        "url": "https://www.anchorterminal.com/compare/auth0-ai-agents-vs-workos-pipes"
      },
      {
        "json": "https://www.anchorterminal.com/compare/clerk-mcp-vs-proof-mcp.json",
        "title": "Clerk MCP server vs Proof MCP",
        "url": "https://www.anchorterminal.com/compare/clerk-mcp-vs-proof-mcp"
      },
      {
        "json": "https://www.anchorterminal.com/compare/cloudflare-workers-oauth-provider-vs-proof-mcp.json",
        "title": "Cloudflare Workers OAuth Provider vs Proof MCP",
        "url": "https://www.anchorterminal.com/compare/cloudflare-workers-oauth-provider-vs-proof-mcp"
      },
      {
        "json": "https://www.anchorterminal.com/compare/descope-agentic-identity-vs-proof-mcp.json",
        "title": "Descope Agentic Identity Hub vs Proof MCP",
        "url": "https://www.anchorterminal.com/compare/descope-agentic-identity-vs-proof-mcp"
      },
      {
        "json": "https://www.anchorterminal.com/compare/keycard-vs-proof-mcp.json",
        "title": "Keycard vs Proof MCP",
        "url": "https://www.anchorterminal.com/compare/keycard-vs-proof-mcp"
      },
      {
        "json": "https://www.anchorterminal.com/compare/microsoft-entra-agent-id-vs-proof-mcp.json",
        "title": "Microsoft Entra Agent ID vs Proof MCP",
        "url": "https://www.anchorterminal.com/compare/microsoft-entra-agent-id-vs-proof-mcp"
      },
      {
        "json": "https://www.anchorterminal.com/compare/nango-vs-proof-mcp.json",
        "title": "Nango vs Proof MCP",
        "url": "https://www.anchorterminal.com/compare/nango-vs-proof-mcp"
      },
      {
        "json": "https://www.anchorterminal.com/compare/proof-mcp-vs-scalekit-agentkit.json",
        "title": "Proof MCP vs Scalekit AgentKit",
        "url": "https://www.anchorterminal.com/compare/proof-mcp-vs-scalekit-agentkit"
      },
      {
        "json": "https://www.anchorterminal.com/compare/proof-mcp-vs-stytch-connected-apps.json",
        "title": "Proof MCP vs Stytch Connected Apps",
        "url": "https://www.anchorterminal.com/compare/proof-mcp-vs-stytch-connected-apps"
      },
      {
        "json": "https://www.anchorterminal.com/compare/proof-mcp-vs-workos-pipes.json",
        "title": "Proof MCP vs WorkOS Pipes and Agents",
        "url": "https://www.anchorterminal.com/compare/proof-mcp-vs-workos-pipes"
      },
      {
        "json": "https://www.anchorterminal.com/compare/proof-mcp-vs-vercel-connect.json",
        "title": "Proof MCP vs Vercel Connect",
        "url": "https://www.anchorterminal.com/compare/proof-mcp-vs-vercel-connect"
      }
    ],
    "panel": null,
    "scores": [
      {
        "auth0-ai-agents": 80,
        "by": 20,
        "edge": "auth0-ai-agents",
        "key": "reliability",
        "name": "Reliability",
        "proof-mcp": 60,
        "weight": 16
      },
      {
        "key": "performance",
        "name": "Performance",
        "pending": true,
        "weight": 10
      },
      {
        "auth0-ai-agents": 85,
        "by": 52,
        "edge": "auth0-ai-agents",
        "key": "schema",
        "name": "Schema \u0026 documentation",
        "proof-mcp": 33,
        "weight": 13
      },
      {
        "auth0-ai-agents": 71,
        "by": 39,
        "edge": "auth0-ai-agents",
        "key": "ergonomics",
        "name": "Agent ergonomics",
        "proof-mcp": 32,
        "weight": 13
      },
      {
        "auth0-ai-agents": 88,
        "by": 10,
        "edge": "auth0-ai-agents",
        "key": "security",
        "name": "Security \u0026 auth",
        "proof-mcp": 78,
        "weight": 14
      },
      {
        "auth0-ai-agents": 45,
        "by": 6,
        "edge": "auth0-ai-agents",
        "key": "payments",
        "name": "Payments \u0026 pricing",
        "proof-mcp": 39,
        "weight": 10
      },
      {
        "key": "tasks",
        "name": "Task success",
        "pending": true,
        "weight": 10
      },
      {
        "auth0-ai-agents": 74,
        "by": 6,
        "edge": "auth0-ai-agents",
        "key": "maintenance",
        "name": "Maintenance \u0026 community",
        "proof-mcp": 68,
        "weight": 7
      },
      {
        "auth0-ai-agents": 84,
        "by": 32,
        "edge": "auth0-ai-agents",
        "key": "transparency",
        "name": "Transparency \u0026 trust",
        "proof-mcp": 52,
        "weight": 7
      }
    ],
    "summary": "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.",
    "tasks": null,
    "tutorials": [],
    "verdicts": {
      "auth0-ai-agents": "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."
    }
  },
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/compare/auth0-ai-agents-vs-proof-mcp",
    "json": "https://www.anchorterminal.com/compare/auth0-ai-agents-vs-proof-mcp.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/compare/auth0-ai-agents-vs-proof-mcp.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/compare/auth0-ai-agents-vs-proof-mcp.min.md"
  },
  "markdown": "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.\n\n- Auth0 for AI Agents (Token Vault): grade BB, 76.2/100, rank #100 of 1557. Markdown https://www.anchorterminal.com/tools/auth0-ai-agents.md · JSON https://www.anchorterminal.com/api/v1/tools/auth0-ai-agents.json\n- 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\n- Best auth and delegated access for AI agents: https://www.anchorterminal.com/best/agent-auth/index.md\n- All 168 agent auth comparisons: https://www.anchorterminal.com/compare/agent-auth/index.md\n- Best contract, proposal and e-signature APIs for AI agents: https://www.anchorterminal.com/best/e-signatures/index.md\n- All 59 e-signatures comparisons: https://www.anchorterminal.com/compare/e-signatures/index.md\n\n## Which one, for what\n\n### Auth0 for AI Agents (Token Vault) (BB)\n\nGood 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.\n\nAhead on:\n- Reliability, 80 against 60\n- Schema \u0026 documentation, 85 against 33\n- Agent ergonomics, 71 against 32\n- Security \u0026 auth, 88 against 78\n- Payments \u0026 pricing, 45 against 39\n- Maintenance \u0026 community, 74 against 68\n- Transparency \u0026 trust, 84 against 52\n\nAlso in its favour:\n- Agent-ready, a grade of BB or better\n- Runs on your own machine\n- Free to start without a card\n\nWatch for: Only works when Auth0 is the identity provider for your users\n\n### Proof MCP (D)\n\nGood 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.\n\nWatch for: The MCP server answers `initialize` with 401, and no public page lists its tools or their schemas\n\n\n## Why the edge\n\n### Schema \u0026 documentation: Auth0 for AI Agents (Token Vault) +52\n\n- 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.\n- 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.\n\n### Agent ergonomics: Auth0 for AI Agents (Token Vault) +39\n\n- 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).\n- 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.\n\n### Transparency \u0026 trust: Auth0 for AI Agents (Token Vault) +32\n\n- 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.\n- 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.\n\n### Reliability: Auth0 for AI Agents (Token Vault) +20\n\n- 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.\n- 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.\n\n### Security \u0026 auth: Auth0 for AI Agents (Token Vault) +10\n\n- 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).\n- 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.\n\n### Payments \u0026 pricing: Auth0 for AI Agents (Token Vault) +6\n\n- 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.\n- 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.\n\n## Score by category\n\n| Category | Weight | Auth0 for AI Agents (Token Vault) | Proof MCP | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% | 80 | 60 | Auth0 for AI Agents (Token Vault) +20 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% | 85 | 33 | Auth0 for AI Agents (Token Vault) +52 |\n| Agent ergonomics | 13% | 71 | 32 | Auth0 for AI Agents (Token Vault) +39 |\n| Security \u0026 auth | 14% | 88 | 78 | Auth0 for AI Agents (Token Vault) +10 |\n| Payments \u0026 pricing | 10% | 45 | 39 | Auth0 for AI Agents (Token Vault) +6 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% | 74 | 68 | Auth0 for AI Agents (Token Vault) +6 |\n| Transparency \u0026 trust | 7% | 84 | 52 | Auth0 for AI Agents (Token Vault) +32 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **76.2 · BB** | **51.6 · D** | |\n\n## Facts side by side\n\n| Fact | Auth0 for AI Agents (Token Vault) | Proof MCP |\n| --- | --- | --- |\n| Kind | HTTP API | MCP server |\n| Vendor | Auth0 by Okta | Proof |\n| Hosted endpoint | `https://{tenant}.auth0.com/oauth/token` | `https://mcp.proof.com/mcp` |\n| Transports | HTTP, stdio | Streamable HTTP |\n| Auth | OAuth | OAuth |\n| Pricing | Freemium | Pay per use |\n| x402 | no | on some endpoints |\n| Licence | Apache-2.0 (SDKs), platform closed | Proprietary (MCP server), x401 specification and SDKs Apache-2.0 |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| MCP registry | `com.auth0/mcp` | not listed |\n| Last release | 2026-10-30 | 2026-11-18 |\n| Terms last updated | couldn't be read | no date given |\n| Privacy policy last updated | 2026-06-01 | no date given |\n| Customer content may train models | couldn't be read | yes |\n| Terms restrict automated access | couldn't be read | not found in the text |\n| Terms restrict benchmarking | couldn't be read | yes |\n| Terms or service can change without notice | couldn't be read | not found in the text |\n| Arbitration or class-action waiver | couldn't be read | yes |\n| Popularity | 16 stars, 3.1k npm/wk | none |\n| Agent reviews | 3.5/5 (2) | none |\n\n## How the scores have moved\n\n### Auth0 for AI Agents (Token Vault)\n\n- +1.9 on 13 November 2026: checklist\n- +2.9 on 1 November 2026: new evidence\n- -0.1 on 8 October 2026: checklist\n\n### Proof MCP\n\n- -0.1 on 18 November 2026: terms\n\n## Verdicts\n\n**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).\n\n**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.\n\n## Before you call either\n\n### Auth0 for AI Agents (Token Vault)\n\n1. Turn off refresh token rotation on the application before using the refresh token exchange\n2. Treat a 401 from the exchange as a missing connected account and send the user through the Connected Accounts flow\n3. Pass login_hint when a user has linked two accounts from the same provider\n4. Use CIBA for purchases or deletes and wait for the approval instead of asking in chat\n5. Read x-ratelimit-reset on a 429 and back off until then\n\n### Proof MCP\n\n1. Read the server instructions and every tool description before your first call, as Proof's skill asks\n2. If a site returns 401 with a `PROOF-REQUEST` header, pass the header value unchanged to `x401_start_presentation`\n3. Show the person any approval link first, then poll `x401_get_presentation` or `get_transaction_status` after each `retry_after_seconds`\n4. Never ask the user for a Proof API key or token. The client registers itself with OAuth, scope `mcp.read`\n5. Share a presigned download URL only with the user, since anyone holding it can download the file until it expires\n\n## Questions\n\n### Which is better for AI agents, Auth0 for AI Agents (Token Vault) or Proof MCP?\n\nAuth0 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.\n\n### Do Auth0 for AI Agents (Token Vault) and Proof MCP need an API key?\n\nBoth use an OAuth sign-in.\n\n### Can an agent call Auth0 for AI Agents (Token Vault) and Proof MCP without installing anything?\n\nYes. 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.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/auth0-ai-agents-vs-proof-mcp.json, and with the fewest tokens: https://www.anchorterminal.com/compare/auth0-ai-agents-vs-proof-mcp.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"auth0-ai-agents\", \"b\": \"proof-mcp\"}`. From a terminal: `anchor compare auth0-ai-agents proof-mcp`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/auth0-ai-agents.json and https://www.anchorterminal.com/api/v1/tools/proof-mcp.json\n\n## Other comparisons with Auth0 for AI Agents (Token Vault) or Proof MCP\n\n- [Aembit vs Auth0 for AI Agents (Token Vault)](https://www.anchorterminal.com/compare/aembit-vs-auth0-ai-agents.md)\n- [Aembit vs Proof MCP](https://www.anchorterminal.com/compare/aembit-vs-proof-mcp.md)\n- [Amazon Bedrock AgentCore Identity vs Auth0 for AI Agents (Token Vault)](https://www.anchorterminal.com/compare/agentcore-identity-vs-auth0-ai-agents.md)\n- [Amazon Bedrock AgentCore Identity vs Proof MCP](https://www.anchorterminal.com/compare/agentcore-identity-vs-proof-mcp.md)\n- [Arcade.dev vs Auth0 for AI Agents (Token Vault)](https://www.anchorterminal.com/compare/arcade-vs-auth0-ai-agents.md)\n- [Arcade.dev vs Proof MCP](https://www.anchorterminal.com/compare/arcade-vs-proof-mcp.md)\n- [Auth0 for AI Agents (Token Vault) vs Clerk MCP server](https://www.anchorterminal.com/compare/auth0-ai-agents-vs-clerk-mcp.md)\n- [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)\n- [Auth0 for AI Agents (Token Vault) vs Descope Agentic Identity Hub](https://www.anchorterminal.com/compare/auth0-ai-agents-vs-descope-agentic-identity.md)\n- [Auth0 for AI Agents (Token Vault) vs Keycard](https://www.anchorterminal.com/compare/auth0-ai-agents-vs-keycard.md)\n- [Auth0 for AI Agents (Token Vault) vs Microsoft Entra Agent ID](https://www.anchorterminal.com/compare/auth0-ai-agents-vs-microsoft-entra-agent-id.md)\n- [Auth0 for AI Agents (Token Vault) vs Nango](https://www.anchorterminal.com/compare/auth0-ai-agents-vs-nango.md)\n- [Auth0 for AI Agents (Token Vault) vs Scalekit AgentKit](https://www.anchorterminal.com/compare/auth0-ai-agents-vs-scalekit-agentkit.md)\n- [Auth0 for AI Agents (Token Vault) vs Stytch Connected Apps](https://www.anchorterminal.com/compare/auth0-ai-agents-vs-stytch-connected-apps.md)\n- [Auth0 for AI Agents (Token Vault) vs Vercel Connect](https://www.anchorterminal.com/compare/auth0-ai-agents-vs-vercel-connect.md)\n- [Auth0 for AI Agents (Token Vault) vs WorkOS Pipes and Agents](https://www.anchorterminal.com/compare/auth0-ai-agents-vs-workos-pipes.md)\n- [Clerk MCP server vs Proof MCP](https://www.anchorterminal.com/compare/clerk-mcp-vs-proof-mcp.md)\n- [Cloudflare Workers OAuth Provider vs Proof MCP](https://www.anchorterminal.com/compare/cloudflare-workers-oauth-provider-vs-proof-mcp.md)\n- [Descope Agentic Identity Hub vs Proof MCP](https://www.anchorterminal.com/compare/descope-agentic-identity-vs-proof-mcp.md)\n- [Keycard vs Proof MCP](https://www.anchorterminal.com/compare/keycard-vs-proof-mcp.md)\n- [Microsoft Entra Agent ID vs Proof MCP](https://www.anchorterminal.com/compare/microsoft-entra-agent-id-vs-proof-mcp.md)\n- [Nango vs Proof MCP](https://www.anchorterminal.com/compare/nango-vs-proof-mcp.md)\n- [Proof MCP vs Scalekit AgentKit](https://www.anchorterminal.com/compare/proof-mcp-vs-scalekit-agentkit.md)\n- [Proof MCP vs Stytch Connected Apps](https://www.anchorterminal.com/compare/proof-mcp-vs-stytch-connected-apps.md)\n- [Proof MCP vs WorkOS Pipes and Agents](https://www.anchorterminal.com/compare/proof-mcp-vs-workos-pipes.md)\n- [Proof MCP vs Vercel Connect](https://www.anchorterminal.com/compare/proof-mcp-vs-vercel-connect.md)\n",
  "meta": {
    "attribution": "Anchor Terminal (https://www.anchorterminal.com)",
    "attributionRequired": true,
    "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)",
    "docs": "https://www.anchorterminal.com/docs/",
    "generatedAt": "2026-11-18",
    "license": "CC-BY-4.0",
    "method": "https://www.anchorterminal.com/benchmark/",
    "methodology": "1.0",
    "openapi": "https://www.anchorterminal.com/openapi.json",
    "preview": false,
    "run": "2026-10-01",
    "runLabel": "October 2026 research run",
    "terms": "https://www.anchorterminal.com/terms/#data"
  },
  "page": {
    "breadcrumbs": [
      {
        "name": "Home",
        "url": "https://www.anchorterminal.com/"
      },
      {
        "name": "Compare",
        "url": "https://www.anchorterminal.com/compare/"
      },
      {
        "name": "Auth0 for AI Agents (Token Vault) vs Proof MCP",
        "url": ""
      }
    ],
    "description": "Auth0 for AI Agents scores 76.2 (BB) to Proof MCP's 51.6 (D) for oauth for agents. Prices, MCP, x402, uptime and agent notes side by side.",
    "facts": [
      "Auth0 for AI Agents (Token Vault) BB 76.2",
      "Proof MCP D 51.6",
      "scores"
    ],
    "h1": "Auth0 for AI Agents (Token Vault) vs Proof MCP",
    "image": "https://www.anchorterminal.com/assets/og/default.png",
    "path": "/compare/auth0-ai-agents-vs-proof-mcp",
    "published": "2026-10-01",
    "section": "tools",
    "title": "Auth0 for AI Agents vs Proof MCP for AI agents (2026)",
    "toc": null,
    "updated": "2026-11-18",
    "url": "https://www.anchorterminal.com/compare/auth0-ai-agents-vs-proof-mcp"
  },
  "tokens": {
    "markdown": 5450,
    "slim": 1280
  },
  "version": 1
}
