{
  "data": {
    "a": {
      "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
      }
    },
    "answer": "Vercel Connect scores 73.3 (BB) on agent readiness against Proof MCP's 51.6 (D), and leads in every scored category.",
    "b": {
      "slug": "vercel-connect",
      "name": "Vercel Connect",
      "vendor": "Vercel",
      "vendorUrl": "https://vercel.com",
      "company": "vercel.com",
      "kind": "http-api",
      "category": "agent-auth",
      "summary": "Vercel Connect is a credential broker for apps and agents. Code asks it for a short-lived, scoped token for Slack, GitHub, Microsoft, Linear, Snowflake or any OAuth, API-key or MCP service, as the app or for a user.",
      "url": "https://www.anchorterminal.com/tools/vercel-connect",
      "markdownUrl": "https://www.anchorterminal.com/tools/vercel-connect.md",
      "slimMarkdownUrl": "https://www.anchorterminal.com/tools/vercel-connect.min.md",
      "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/vercel-connect.json",
      "dns": "vercel-connect.grade.anchorterminal.com",
      "repo": "https://github.com/vercel/vercel",
      "license": "Proprietary service under Vercel's Terms of Service and the Vercel Connect product terms. The `@vercel/connect` SDK and the Vercel CLI are Apache-2.0",
      "transports": [
        "http"
      ],
      "remoteUrl": "https://api.vercel.com",
      "packages": [
        {
          "registry": "npm",
          "name": "@vercel/connect"
        }
      ],
      "auth": "mixed",
      "authNotes": "Access is self-serve with a Vercel account, on every plan. A deployment calls Connect with its project OIDC token (`VERCEL_OIDC_TOKEN`), which Connect checks against the connector's project links and their environments. Locally, `vercel env pull` writes a development OIDC token that lasts about 12 hours. Outside Vercel, a Vercel access token goes in `vercelToken`, and it can request only the app subject or its own user. Connect then holds the provider side. Vercel registers the OAuth client for managed connectors (Slack, GitHub, Linear, Microsoft, Snowflake, Salesforce), and the customer supplies a client or an API key for the others. End users consent in a browser at a URL from `startAuthorization`.",
      "pricing": "freemium",
      "pricingNotes": "Billed per token request and per trigger. Hobby includes 500 token requests and 1,000 triggers a month at no extra charge, and Vercel's fair use guidelines limit Hobby to non-commercial, personal use. Pro is $3.00 per 1,000 token requests and $0.95 per 1,000 triggers on top of the plan. Enterprise is negotiated. A trigger is counted once per destination, and once per event when no destination is set. MCP Events deliveries (public beta) are billed as triggers, one per delivery forwarded. The SDK's in-process cache means many provider calls in one invocation cost one token request (https://vercel.com/docs/connect/pricing, checked 2026-10-17).",
      "priceSummary": "$3 / 1k req",
      "where": "hosted",
      "x402": {
        "level": "no",
        "evidence": "No x402, MPP or L402 in the Connect docs, the pricing page or the Connect operations of the OpenAPI document (checked 2026-10-08).",
        "endpoints": []
      },
      "toolCount": null,
      "popularity": {
        "githubStars": 16354,
        "npmWeekly": 738165,
        "pypiWeekly": null,
        "asOf": "2026-10-08"
      },
      "docsUrl": "https://vercel.com/docs/connect",
      "llmsTxt": "https://vercel.com/llms.txt",
      "openapi": "https://openapi.vercel.sh/",
      "capabilities": [
        "auth.tokens",
        "auth.oauth",
        "auth.consent",
        "auth.audit"
      ],
      "tags": [
        "hosted",
        "freemium",
        "free-tier",
        "oauth",
        "oidc",
        "openapi",
        "llms-txt",
        "typescript",
        "cli",
        "webhooks",
        "status-page",
        "soc2",
        "iso27001"
      ],
      "lastRelease": "2026-10-31",
      "graded": true,
      "anchor": {
        "graded": true,
        "score": 73.3,
        "grade": "BB",
        "agentReady": true,
        "rank": 181,
        "ranked": true,
        "rankOf": 1557,
        "categoryRank": 8,
        "methodology": "1.0",
        "run": "2026-10-01",
        "scores": {
          "ergonomics": 75,
          "maintenance": 81,
          "payments": 60,
          "reliability": 73,
          "schema": 84,
          "security": 83,
          "transparency": 77
        },
        "assessment": {
          "confidence": "medium",
          "date": "2026-11-01"
        },
        "negative": -3,
        "negativeNotes": [
          "April 2026. Vercel's security bulletin says an attacker took over an employee's account through a compromised third-party AI tool (Context.ai), reached internal systems and decrypted non-sensitive environment variables of a limited subset of customers, and a later review found a small number of further affected accounts. Vercel closed the incident on 16 October 2026 with all remediation complete. It predates Connect's general availability on 25 August 2026, but it reached customer secrets on the platform where Connect now keeps provider refresh tokens. A fixed and documented incident about six months old, so 3 of a possible 15 is taken. vercel-sandbox takes the same 3 for the same bulletin from 17 October (https://vercel.com/kb/bulletin/vercel-april-2026-security-incident)."
        ],
        "verdict": "Provider refresh tokens stay with Vercel, and code receives short-lived tokens tied to a project and environment through one call with a public OpenAPI definition. Vercel's SLA excludes its APIs, Connect had elevated errors for some customers on 10 and 18 September 2026, and the only SDK is TypeScript.",
        "bestFor": "Teams already deploying on Vercel whose agents need user or app tokens for Slack, GitHub, Microsoft, Linear, Snowflake or an MCP server without storing provider secrets, and providers behind IP allowlists through Secure Compute.",
        "strengths": [
          "Refresh tokens stay on Vercel's infrastructure. Code receives only short-lived access tokens, as the app or for a named user",
          "A deployment authenticates with its project OIDC token, checked against per-environment project links, so no provider secret sits in environment variables",
          "Public OpenAPI 3.0.3 document covers 14 Connect paths, including `/v1/connect/token/{connector}` and `/v1/connect/authorize/{connector}`",
          "Token requests, completed authorisations and revocations are logged with `tokenId` and `authorizationId`, and can be sent to a drain on Pro and Enterprise",
          "Rate limits are published with numbers, 200 reads and 50 writes a minute per team"
        ],
        "weaknesses": [
          "Vercel's SLA says it does not apply to the APIs or CLI, so token requests carry no uptime commitment",
          "Elevated Connect errors for some customers for 94 minutes on 10 September 2026, marked major, and again on 18 September, per the status page",
          "Event history is kept 12 hours on Hobby and 3 days on Pro. Connector audit logs and 30 days need Enterprise",
          "Revocation depends on the provider. Without a revocation endpoint the provider credential can work until it expires",
          "The SDK is TypeScript only, and the public repository's copy (2.5.6, synced 27 October 2026) lags npm's 2.7.0"
        ],
        "agentNotes": [
          "Call `getToken` at request time and don't store the result. The SDK caches up to 100 tokens in process and refreshes them 30 seconds before expiry",
          "Pass `scopes` on every request. Since SDK 1.0.0 an omitted `scopes` defaults to `['*']`, the connector's default scopes",
          "Catch `UserAuthorizationRequiredError`, call `startAuthorization` and send the user to the returned URL. Consent needs a person in a browser",
          "Outside Vercel, pass a Vercel access token as `vercelToken`. It can request only the app subject or its own user, not another user",
          "On a 429 wait one minute for the window to reset. Limits are 200 token requests a minute per team"
        ],
        "metrics": {
          "kind": "remote",
          "measured": false
        },
        "reviewCount": 4,
        "avgRating": 3.5,
        "history": [
          {
            "basis": "public evidence",
            "confidence": "medium",
            "grade": "BB",
            "methodology": "1.0",
            "run": "2026-10-01",
            "runLabel": "October 2026 research run",
            "score": 73.3
          }
        ],
        "editorialScores": {
          "ergonomics": 75,
          "maintenance": 81,
          "payments": 60,
          "reliability": 73,
          "schema": 84,
          "security": 83,
          "transparency": 55
        },
        "provenanceScore": 99,
        "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": "pnpm add @vercel/connect",
        "http": "curl -X POST https://api.vercel.com/v1/connect/token/slack%2Facme-slack \\\n  -H \"Authorization: Bearer $VERCEL_OIDC_TOKEN\" \\\n  -H \"Content-Type: application/json\" \\\n  -d '{\"subject\":{\"type\":\"app\"},\"scopes\":[\"chat:write\"]}'"
      },
      "letme": {
        "capability": "https://letme.dev/auth.tokens",
        "tool": "https://letme.dev/vercel-connect"
      },
      "sameCompany": [
        "vercel-ai-gateway",
        "vercel-ai-sdk",
        "vercel-sandbox",
        "agent-browser"
      ],
      "area": "agent-runtime",
      "unitPrices": [
        {
          "item": "Token request (Pro)",
          "unit": "1k-requests",
          "usd": 3,
          "note": "Hobby includes 500 a month. Enterprise negotiated"
        },
        {
          "item": "Trigger, a forwarded provider webhook (Pro)",
          "unit": "1k-requests",
          "usd": 0.95,
          "note": "Counted per destination. Hobby includes 1,000 a month"
        }
      ],
      "provenance": {
        "legalEntity": "Vercel Inc.",
        "domain": "vercel.com",
        "domainRegistered": "1999-10-04",
        "endpointOnVendorDomain": true,
        "terms": "https://vercel.com/legal/terms",
        "privacy": "https://vercel.com/legal/privacy-policy",
        "statusPage": "https://www.vercel-status.com",
        "changelog": "https://vercel.com/changelog",
        "securityTxt": "valid",
        "checked": "2026-11-01",
        "notes": [
          "The Terms of Service (last updated 19 October 2026, read on 1 November 2026) name Vercel Inc., 440 N Barranca Ave #4133, Covina, CA 91723, and California law. The DPA calls Vercel Inc. a Delaware corporation.",
          "Connect's product terms moved into Vercel's Service Terms (last updated 15 October 2026); https://vercel.com/docs/connect/legal now redirects to https://vercel.com/legal/service-terms#connect.",
          "The privacy URL redirects to https://vercel.com/legal/privacy-notice, last updated 1 June 2026, which says it does not apply to personal information Vercel processes as a processor for customers, which the DPA covers. The DPA (effective 31 March 2026) applies to Pro and Enterprise plans.",
          "https://vercel.com/.well-known/security.txt points to HackerOne and responsible.disclosure@vercel.com and expires 2027-09-28, re-read on 1 November 2026.",
          "RDAP gives vercel.com a registration date of 1999-10-04, long before Vercel, so the domain was bought later.",
          "The API answers at api.vercel.com and the OpenAPI document at openapi.vercel.sh."
        ],
        "score": 99
      },
      "pageJsonUrl": "https://www.anchorterminal.com/tools/vercel-connect.json",
      "live": {
        "slug": "vercel-connect",
        "probe": {
          "target": "https://api.vercel.com",
          "method": "get",
          "lastAt": "2026-11-18T23:02:03.000282394Z",
          "lastOk": true,
          "lastStatus": 200,
          "lastMs": 127,
          "authRequired": false,
          "uptime24h": 100,
          "uptime30d": 100,
          "p50ms24h": 174,
          "p95ms24h": 715,
          "samples24h": 241,
          "samples30d": 7840,
          "days": [
            {
              "date": "2026-10-18",
              "probes": 256,
              "ok": 256
            },
            {
              "date": "2026-10-19",
              "probes": 255,
              "ok": 255
            },
            {
              "date": "2026-10-20",
              "probes": 252,
              "ok": 252
            },
            {
              "date": "2026-10-21",
              "probes": 253,
              "ok": 253
            },
            {
              "date": "2026-10-22",
              "probes": 253,
              "ok": 253
            },
            {
              "date": "2026-10-23",
              "probes": 248,
              "ok": 248
            },
            {
              "date": "2026-10-24",
              "probes": 251,
              "ok": 251
            },
            {
              "date": "2026-10-25",
              "probes": 250,
              "ok": 250
            },
            {
              "date": "2026-10-26",
              "probes": 252,
              "ok": 252
            },
            {
              "date": "2026-10-27",
              "probes": 249,
              "ok": 249
            },
            {
              "date": "2026-10-28",
              "probes": 250,
              "ok": 250
            },
            {
              "date": "2026-10-29",
              "probes": 249,
              "ok": 249
            },
            {
              "date": "2026-10-30",
              "probes": 249,
              "ok": 249
            },
            {
              "date": "2026-10-31",
              "probes": 251,
              "ok": 251
            },
            {
              "date": "2026-11-01",
              "probes": 249,
              "ok": 249
            },
            {
              "date": "2026-11-02",
              "probes": 250,
              "ok": 250
            },
            {
              "date": "2026-11-03",
              "probes": 248,
              "ok": 248
            },
            {
              "date": "2026-11-04",
              "probes": 246,
              "ok": 246
            },
            {
              "date": "2026-11-05",
              "probes": 185,
              "ok": 185
            },
            {
              "date": "2026-11-06",
              "probes": 241,
              "ok": 241
            },
            {
              "date": "2026-11-07",
              "probes": 243,
              "ok": 243
            },
            {
              "date": "2026-11-08",
              "probes": 243,
              "ok": 243
            },
            {
              "date": "2026-11-09",
              "probes": 243,
              "ok": 243
            },
            {
              "date": "2026-11-10",
              "probes": 244,
              "ok": 244
            },
            {
              "date": "2026-11-11",
              "probes": 244,
              "ok": 244
            },
            {
              "date": "2026-11-12",
              "probes": 245,
              "ok": 245
            },
            {
              "date": "2026-11-13",
              "probes": 238,
              "ok": 238
            },
            {
              "date": "2026-11-14",
              "probes": 244,
              "ok": 244
            },
            {
              "date": "2026-11-15",
              "probes": 243,
              "ok": 243
            },
            {
              "date": "2026-11-16",
              "probes": 243,
              "ok": 243
            },
            {
              "date": "2026-11-17",
              "probes": 242,
              "ok": 242
            },
            {
              "date": "2026-11-18",
              "probes": 231,
              "ok": 231
            }
          ],
          "since": "2026-10-09T00:00:00Z"
        },
        "vendorStatus": {
          "page": "https://www.vercel-status.com",
          "indicator": "minor",
          "summary": "Minor Service Outage",
          "checkedAt": "2026-11-18T23:01:24.015566027Z"
        },
        "versions": [
          {
            "registry": "github",
            "name": "vercel/vercel",
            "version": "@vercel/static-build@2.11.13",
            "released": "2026-07-30",
            "seenAt": "2026-11-18T18:39:22.098744938Z"
          },
          {
            "registry": "npm",
            "name": "@vercel/connect",
            "version": "2.9.4",
            "seenAt": "2026-11-18T18:39:21.044532088Z"
          }
        ],
        "githubStars": 16622,
        "npmWeekly": 1897972,
        "securityTxt": {
          "url": "https://vercel.com/.well-known/security.txt",
          "state": "valid",
          "expires": "2027-09-28T12:00:00.000Z",
          "checkedAt": "2026-11-18T16:31:08.733177415Z"
        },
        "llmsTxt": {
          "url": "https://vercel.com/llms.txt",
          "ok": true,
          "status": 200,
          "checkedAt": "2026-11-18T16:16:39.393828262Z"
        },
        "domain": {
          "domain": "vercel.com",
          "registered": "1999-10-04",
          "source": "https://rdap.verisign.com/com/v1/domain/vercel.com",
          "checkedAt": "2026-11-15T15:15:18.264224016Z"
        },
        "pages": [
          {
            "url": "https://vercel.com/changelog",
            "kind": "changelog",
            "status": 200,
            "checkedAt": "2026-10-16T22:33:02.411577324Z",
            "changedAt": "2026-10-16T22:33:02.411577324Z",
            "fingerprint": "1bf6c6d68534"
          },
          {
            "url": "https://vercel.com/docs/connect/pricing",
            "kind": "pricing",
            "status": 200,
            "checkedAt": "2026-11-18T21:57:38.936706051Z",
            "changedAt": "2026-11-12T17:53:38.152370919Z",
            "fingerprint": "3e4c74d6c60b"
          },
          {
            "url": "https://vercel.com/legal/privacy-policy",
            "kind": "privacy",
            "status": 200,
            "checkedAt": "2026-10-16T22:33:09.129654005Z",
            "changedAt": "2026-10-06T16:13:29.92763016Z",
            "fingerprint": "7ab1f9d3393a"
          },
          {
            "url": "https://vercel.com/legal/terms",
            "kind": "terms",
            "status": 200,
            "checkedAt": "2026-10-16T22:33:10.564262216Z",
            "changedAt": "2026-10-06T16:13:31.349375221Z",
            "fingerprint": "35995712008a"
          }
        ],
        "github": {
          "repo": "vercel/vercel",
          "checkedAt": "2026-11-16T13:24:37.229305512Z",
          "stars": 16605,
          "archived": false,
          "issuesEnabled": true,
          "pushedAt": "2026-11-16T02:50:11Z",
          "openIssues": 373,
          "openPRs": 494,
          "issuesOpened90d": 81,
          "issuesClosed90d": 41,
          "prsMerged90d": 4,
          "ci": {
            "branch": "main",
            "runs": 50,
            "success": 15,
            "failure": 35,
            "other": 0,
            "latest": "failure",
            "latestAt": "2026-11-12T22:18:33Z"
          },
          "advisories": [
            {
              "ghsa": "GHSA-7wjf-49rm-77gx",
              "severity": "high",
              "published": "2026-08-28T20:11:19Z"
            },
            {
              "ghsa": "GHSA-pgf8-2hgj-grqg",
              "cve": "CVE-2026-44479",
              "severity": "medium",
              "published": "2026-04-30T13:43:32Z"
            }
          ],
          "replies": {
            "sampled": 25,
            "unanswered": 20,
            "medianDays": 0.6
          }
        },
        "updatedAt": "2026-11-18T23:02:03.000282394Z"
      },
      "streak": {
        "days": 40,
        "from": "2026-10-09",
        "sinceWatching": true,
        "best": 40
      }
    },
    "edges": [
      {
        "by": 51,
        "category": "schema",
        "leads": "vercel-connect",
        "name": "Schema \u0026 documentation",
        "reasons": {
          "a": "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.",
          "b": "Vercel's public OpenAPI 3.0.3 document, re-read on 1 November 2026, has 14 paths under `/v1/connect` and `/v2/connect`, the token and authorise calls, `/v1/connect/networks` for Secure Compute and a trigger-destinations path among them (25). Docs are served as Markdown on request and vercel.com/llms.txt exists (10). The docs say when to use Connect and when a Vercel Integration fits better, and give a use-when line for each subject type (16). The token body types the subject as a union with enums, but most variants allow extra properties, `authorizationDetails` is open and scopes are provider strings (10). Examples are plentiful and six SDK error classes are documented with fixes, while the OpenAPI error responses for the token call have empty descriptions (11). Paths are versioned and the SDK follows semver with a dated product changelog. The package changelog in the public repository was synced to 2.5.6 on 27 October 2026 while npm has 2.7.0, so the newest releases have no public notes (12)."
        },
        "scores": {
          "a": 33,
          "b": 84
        }
      },
      {
        "by": 43,
        "category": "ergonomics",
        "leads": "vercel-connect",
        "name": "Agent ergonomics",
        "reasons": {
          "a": "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.",
          "b": "A token call returns one token with its expiry and identifiers, so there is little to size (22). Listing connectors takes `limit`, `cursor`, `search`, `projectId` and `type` (18). Errors are typed and each maps to a next step, such as starting consent or attaching the project, but the 429 carries no documented wait header (17). Token requests are cached and safe to repeat, and we found no idempotency keys for create, attach or revoke (10). Only the connector and subject are required and scopes default to the connector's own, but the one official SDK is TypeScript, with a CLI and plain HTTP for everything else (8)."
        },
        "scores": {
          "a": 32,
          "b": 75
        }
      },
      {
        "by": 25,
        "category": "transparency",
        "leads": "vercel-connect",
        "name": "Transparency \u0026 trust",
        "reasons": {
          "a": "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.",
          "b": "Closed service under the Terms of Service last updated 19 October 2026, with the Connect product terms now in Vercel's Service Terms (last updated 15 October 2026), and an Apache-2.0 SDK and CLI (20). A privacy notice (last updated 1 June 2026) and a DPA exist. The DPA, read on 17 October, is effective 31 March 2026, covers Pro and Enterprise only and has customer data deleted within a commercially reasonable time after termination. The docs say refresh tokens are stored on Vercel's infrastructure and give event retention by plan. We found no retention period or encryption statement for stored provider credentials (18). No deprecation policy found. The Service Terms still let Vercel \"add or remove Third Party Platforms to Vercel Connect without notice\", though the beta price change was announced with a date of 25 September 2026 (5). The DPA points to a subprocessor list on security.vercel.com and says primary processing is in the United States. We saw the list's page but could not read its entries (12)."
        },
        "scores": {
          "a": 52,
          "b": 77
        }
      },
      {
        "by": 21,
        "category": "payments",
        "leads": "vercel-connect",
        "name": "Payments \u0026 pricing",
        "reasons": {
          "a": "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.",
          "b": "No x402, MPP or L402 (0). Unit prices are public without a login, re-read on 1 November 2026, $3.00 per 1,000 token requests and $0.95 per 1,000 triggers on Pro, and MCP Events deliveries are billed as triggers (20). Hobby includes 500 token requests and 1,000 triggers a month at no charge, for non-commercial use. The Hobby plan page, read on 17 October, calls the plan free with no billing cycles and asks for card details only when upgrading to Pro (20). A person signs up in a browser, and connectors and user consent also pass through a browser (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60."
        },
        "scores": {
          "a": 39,
          "b": 60
        }
      },
      {
        "by": 13,
        "category": "reliability",
        "leads": "vercel-connect",
        "name": "Reliability",
        "reasons": {
          "a": "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.",
          "b": "Graded on the hosted lines. Connect is a component on www.vercel-status.com with an incident history (20). The history feed, re-read on 1 November 2026, covers the whole 90 days from 3 August. It has two Connect incidents. On 10 September 2026 \"some customers may experience increased errors from Connect and Passport\" from 17:42 to 19:16 UTC, marked major by Vercel. On 18 September customers of KMS, Connect, Passport and the Snowflake V0 Integration \"may have experienced elevated errors\", posted once with no duration and no impact level. Errors for some customers are a partial incident, which this assessment reads as minor whatever the vendor's label, so the record is minor incidents only. None has been posted for Connect since 18 September (20). Rate limits published with numbers, 200 reads and 50 writes a minute per team and 6,000 a minute on the OAuth gateway and trigger endpoints, on a limits page last updated 26 August 2026 and re-read on 1 November (15). A 429 is documented with a one-minute wait and token requests are safe to repeat, but we found no Retry-After header or idempotency keys for writes. The MCP Events docs ask for a reused `requestId` when retrying a subscription, but that adapter is experimental and in public beta, so it isn't counted (8). Vercel's SLA, re-read on 1 November, says it does not apply to \"the API's or CLI\" (0). Generally available since 25 August 2026. MCP Events and Enterprise-Managed Authorization are in public beta and aren't the graded surface (10)."
        },
        "scores": {
          "a": 60,
          "b": 73
        }
      },
      {
        "by": 13,
        "category": "maintenance",
        "leads": "vercel-connect",
        "name": "Maintenance \u0026 community",
        "reasons": {
          "a": "The Proof MCP's first release in ChatGPT was announced on 18 November 2026 (30). x401-node has tags up to v0.3.4 (commit of 17 November 2026) and proof-vc-common up to v0.7.1, with 24 and 39 commits since 20 August 2026 (20). A support site and monthly product updates. GitHub issue response wasn't checked (8 of 25). Not in the official MCP registry (searches for `mcp.proof.com` and `com.proof` found nothing of Proof's) (0). x401-node and proof-vc-common run CI and Dependabot (10). 30 + 20 + 8 + 0 + 10 = 68.",
          "b": "`@vercel/connect` 2.7.0 was published on 31 October 2026, per npm's search API (30). The Vercel changelog has Connect entries on 11 and 25 August, 11, 21, 24 and 29 September, three on 15 October, and on 23, 26 and 29 October 2026 (managed Stripe API keys, service discovery in the CLI, webhook triggers for five more providers) (20). Closed service with a dated public changelog. The public copy of the SDK in vercel/vercel was synced from Vercel's internal repository on 27 October at 2.5.6, behind npm, and we didn't read issue replies (10). One current official SDK (15). One runtime dependency (`@vercel/oidc` 4.0.5 at 2.7.0) and a test folder in the package. We didn't confirm CI status on the default branch (6)."
        },
        "scores": {
          "a": 68,
          "b": 81
        }
      }
    ],
    "facts": [
      {
        "a": "MCP server",
        "b": "HTTP API",
        "name": "Kind"
      },
      {
        "a": "Proof",
        "b": "Vercel",
        "name": "Vendor"
      },
      {
        "a": "https://mcp.proof.com/mcp",
        "b": "https://api.vercel.com",
        "name": "Hosted endpoint"
      },
      {
        "a": "Streamable HTTP",
        "b": "HTTP",
        "name": "Transports"
      },
      {
        "a": "OAuth",
        "b": "OAuth or key",
        "name": "Auth"
      },
      {
        "a": "Pay per use",
        "b": "Freemium",
        "name": "Pricing"
      },
      {
        "a": "on some endpoints",
        "b": "no",
        "name": "x402"
      },
      {
        "a": "Proprietary (MCP server), x401 specification and SDKs Apache-2.0",
        "b": "Proprietary service under Vercel's Terms of Service and the Vercel Connect product terms. The `@vercel/connect` SDK and the Vercel CLI are Apache-2.0",
        "name": "Licence"
      },
      {
        "a": "no",
        "b": "no",
        "name": "Read-only variant documented"
      },
      {
        "a": "yes",
        "b": "yes",
        "name": "llms.txt"
      },
      {
        "a": "2026-11-18",
        "b": "2026-10-31",
        "name": "Last release"
      },
      {
        "a": "no date given",
        "b": "2026-06-01",
        "name": "Terms last updated"
      },
      {
        "a": "no date given",
        "b": "2026-06-01",
        "name": "Privacy policy last updated"
      },
      {
        "a": "yes",
        "b": "yes, with an opt-out",
        "name": "Customer content may train models"
      },
      {
        "a": "not found in the text",
        "b": "not found in the text",
        "name": "Terms restrict automated access"
      },
      {
        "a": "yes",
        "b": "not found in the text",
        "name": "Terms restrict benchmarking"
      },
      {
        "a": "not found in the text",
        "b": "not found in the text",
        "name": "Terms or service can change without notice"
      },
      {
        "a": "yes",
        "b": "yes",
        "name": "Arbitration or class-action waiver"
      },
      {
        "a": "none",
        "b": "16k stars, 738k npm/wk",
        "name": "Popularity"
      },
      {
        "a": "none",
        "b": "3.5/5 (4)",
        "name": "Agent reviews"
      }
    ],
    "faq": [
      {
        "answer": "Vercel Connect scores 73.3 (BB) on agent readiness against Proof MCP's 51.6 (D), and leads in every scored category.",
        "question": "Which is better for AI agents, Proof MCP or Vercel Connect?"
      },
      {
        "answer": "Proof MCP uses an OAuth sign-in. Vercel Connect takes an API key or an OAuth sign-in.",
        "question": "Do Proof MCP and Vercel Connect need an API key?"
      },
      {
        "answer": "Yes. Proof MCP has a hosted endpoint at https://mcp.proof.com/mcp and Vercel Connect at https://api.vercel.com.",
        "question": "Can an agent call Proof MCP and Vercel Connect without installing anything?"
      }
    ],
    "goodFor": [
      {
        "aheadOn": null,
        "also": [
          "No incidents deducted, where Vercel Connect loses 3 points for them"
        ],
        "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"
      },
      {
        "aheadOn": [
          "Reliability, 73 against 60",
          "Schema \u0026 documentation, 84 against 33",
          "Agent ergonomics, 75 against 32",
          "Security \u0026 auth, 83 against 78",
          "Payments \u0026 pricing, 60 against 39",
          "Maintenance \u0026 community, 81 against 68",
          "Transparency \u0026 trust, 77 against 52"
        ],
        "also": [
          "Agent-ready, a grade of BB or better"
        ],
        "goodFor": "Teams already deploying on Vercel whose agents need user or app tokens for Slack, GitHub, Microsoft, Linear, Snowflake or an MCP server without storing provider secrets, and providers behind IP allowlists through Secure Compute.",
        "slug": "vercel-connect",
        "watchFor": "Vercel's SLA says it does not apply to the APIs or CLI, so token requests carry no uptime commitment"
      }
    ],
    "history": {
      "proof-mcp": [
        {
          "causes": [
            "terms"
          ],
          "date": "2026-11-18",
          "delta": -0.1,
          "from": 51.7,
          "fromGrade": "D",
          "to": 51.6,
          "toGrade": "D"
        }
      ],
      "vercel-connect": [
        {
          "causes": [
            "method"
          ],
          "date": "2026-11-13",
          "delta": 2.5,
          "from": 70.8,
          "fromGrade": "BB",
          "to": 73.3,
          "toGrade": "BB"
        },
        {
          "causes": [
            "correction"
          ],
          "date": "2026-11-01",
          "delta": 2,
          "from": 68.8,
          "fromGrade": "B",
          "to": 70.8,
          "toGrade": "BB"
        }
      ]
    },
    "job": {
      "capability": "auth.consent",
      "name": "Auth consent"
    },
    "others": [
      {
        "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/aembit-vs-vercel-connect.json",
        "title": "Aembit vs Vercel Connect",
        "url": "https://www.anchorterminal.com/compare/aembit-vs-vercel-connect"
      },
      {
        "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/agentcore-identity-vs-vercel-connect.json",
        "title": "Amazon Bedrock AgentCore Identity vs Vercel Connect",
        "url": "https://www.anchorterminal.com/compare/agentcore-identity-vs-vercel-connect"
      },
      {
        "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/arcade-vs-vercel-connect.json",
        "title": "Arcade.dev vs Vercel Connect",
        "url": "https://www.anchorterminal.com/compare/arcade-vs-vercel-connect"
      },
      {
        "json": "https://www.anchorterminal.com/compare/auth0-ai-agents-vs-proof-mcp.json",
        "title": "Auth0 for AI Agents (Token Vault) vs Proof MCP",
        "url": "https://www.anchorterminal.com/compare/auth0-ai-agents-vs-proof-mcp"
      },
      {
        "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/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/clerk-mcp-vs-vercel-connect.json",
        "title": "Clerk MCP server vs Vercel Connect",
        "url": "https://www.anchorterminal.com/compare/clerk-mcp-vs-vercel-connect"
      },
      {
        "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/cloudflare-workers-oauth-provider-vs-vercel-connect.json",
        "title": "Cloudflare Workers OAuth Provider vs Vercel Connect",
        "url": "https://www.anchorterminal.com/compare/cloudflare-workers-oauth-provider-vs-vercel-connect"
      },
      {
        "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/descope-agentic-identity-vs-vercel-connect.json",
        "title": "Descope Agentic Identity Hub vs Vercel Connect",
        "url": "https://www.anchorterminal.com/compare/descope-agentic-identity-vs-vercel-connect"
      },
      {
        "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/keycard-vs-vercel-connect.json",
        "title": "Keycard vs Vercel Connect",
        "url": "https://www.anchorterminal.com/compare/keycard-vs-vercel-connect"
      },
      {
        "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/microsoft-entra-agent-id-vs-vercel-connect.json",
        "title": "Microsoft Entra Agent ID vs Vercel Connect",
        "url": "https://www.anchorterminal.com/compare/microsoft-entra-agent-id-vs-vercel-connect"
      },
      {
        "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/nango-vs-vercel-connect.json",
        "title": "Nango vs Vercel Connect",
        "url": "https://www.anchorterminal.com/compare/nango-vs-vercel-connect"
      },
      {
        "json": "https://www.anchorterminal.com/compare/scalekit-agentkit-vs-vercel-connect.json",
        "title": "Scalekit AgentKit vs Vercel Connect",
        "url": "https://www.anchorterminal.com/compare/scalekit-agentkit-vs-vercel-connect"
      },
      {
        "json": "https://www.anchorterminal.com/compare/stytch-connected-apps-vs-vercel-connect.json",
        "title": "Stytch Connected Apps vs Vercel Connect",
        "url": "https://www.anchorterminal.com/compare/stytch-connected-apps-vs-vercel-connect"
      },
      {
        "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/vercel-connect-vs-workos-pipes.json",
        "title": "Vercel Connect vs WorkOS Pipes and Agents",
        "url": "https://www.anchorterminal.com/compare/vercel-connect-vs-workos-pipes"
      }
    ],
    "panel": null,
    "scores": [
      {
        "by": 13,
        "edge": "vercel-connect",
        "key": "reliability",
        "name": "Reliability",
        "proof-mcp": 60,
        "vercel-connect": 73,
        "weight": 16
      },
      {
        "key": "performance",
        "name": "Performance",
        "pending": true,
        "weight": 10
      },
      {
        "by": 51,
        "edge": "vercel-connect",
        "key": "schema",
        "name": "Schema \u0026 documentation",
        "proof-mcp": 33,
        "vercel-connect": 84,
        "weight": 13
      },
      {
        "by": 43,
        "edge": "vercel-connect",
        "key": "ergonomics",
        "name": "Agent ergonomics",
        "proof-mcp": 32,
        "vercel-connect": 75,
        "weight": 13
      },
      {
        "by": 5,
        "edge": "vercel-connect",
        "key": "security",
        "name": "Security \u0026 auth",
        "proof-mcp": 78,
        "vercel-connect": 83,
        "weight": 14
      },
      {
        "by": 21,
        "edge": "vercel-connect",
        "key": "payments",
        "name": "Payments \u0026 pricing",
        "proof-mcp": 39,
        "vercel-connect": 60,
        "weight": 10
      },
      {
        "key": "tasks",
        "name": "Task success",
        "pending": true,
        "weight": 10
      },
      {
        "by": 13,
        "edge": "vercel-connect",
        "key": "maintenance",
        "name": "Maintenance \u0026 community",
        "proof-mcp": 68,
        "vercel-connect": 81,
        "weight": 7
      },
      {
        "by": 25,
        "edge": "vercel-connect",
        "key": "transparency",
        "name": "Transparency \u0026 trust",
        "proof-mcp": 52,
        "vercel-connect": 77,
        "weight": 7
      }
    ],
    "summary": "Vercel Connect scores 73.3 (BB) on agent readiness against Proof MCP's 51.6 (D), and leads in every scored category. Both do auth consent.",
    "tasks": null,
    "tutorials": [],
    "verdicts": {
      "proof-mcp": "Proof MCP lets an agent answer a site's x401 identity request with the person's verified credential and their approval, over OAuth with no API key, and Proof's status page shows no incident since 20 July 2026. Its tool list sits behind sign-in, no tool reference or rate limits are published, and the privacy policy allows training AI on user data.",
      "vercel-connect": "Provider refresh tokens stay with Vercel, and code receives short-lived tokens tied to a project and environment through one call with a public OpenAPI definition. Vercel's SLA excludes its APIs, Connect had elevated errors for some customers on 10 and 18 September 2026, and the only SDK is TypeScript."
    }
  },
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/compare/proof-mcp-vs-vercel-connect",
    "json": "https://www.anchorterminal.com/compare/proof-mcp-vs-vercel-connect.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/compare/proof-mcp-vs-vercel-connect.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/compare/proof-mcp-vs-vercel-connect.min.md"
  },
  "markdown": "Vercel Connect scores 73.3 (BB) on agent readiness against Proof MCP's 51.6 (D), and leads in every scored category. Both do auth consent.\n\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- Vercel Connect: grade BB, 73.3/100, rank #181 of 1557. Markdown https://www.anchorterminal.com/tools/vercel-connect.md · JSON https://www.anchorterminal.com/api/v1/tools/vercel-connect.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### 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\nAlso in its favour:\n- No incidents deducted, where Vercel Connect loses 3 points for them\n\nWatch for: The MCP server answers `initialize` with 401, and no public page lists its tools or their schemas\n\n### Vercel Connect (BB)\n\nGood for: Teams already deploying on Vercel whose agents need user or app tokens for Slack, GitHub, Microsoft, Linear, Snowflake or an MCP server without storing provider secrets, and providers behind IP allowlists through Secure Compute.\n\nAhead on:\n- Reliability, 73 against 60\n- Schema \u0026 documentation, 84 against 33\n- Agent ergonomics, 75 against 32\n- Security \u0026 auth, 83 against 78\n- Payments \u0026 pricing, 60 against 39\n- Maintenance \u0026 community, 81 against 68\n- Transparency \u0026 trust, 77 against 52\n\nAlso in its favour:\n- Agent-ready, a grade of BB or better\n\nWatch for: Vercel's SLA says it does not apply to the APIs or CLI, so token requests carry no uptime commitment\n\n\n## Why the edge\n\n### Schema \u0026 documentation: Vercel Connect +51\n\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- Vercel Connect (84): Vercel's public OpenAPI 3.0.3 document, re-read on 1 November 2026, has 14 paths under `/v1/connect` and `/v2/connect`, the token and authorise calls, `/v1/connect/networks` for Secure Compute and a trigger-destinations path among them (25). Docs are served as Markdown on request and vercel.com/llms.txt exists (10). The docs say when to use Connect and when a Vercel Integration fits better, and give a use-when line for each subject type (16). The token body types the subject as a union with enums, but most variants allow extra properties, `authorizationDetails` is open and scopes are provider strings (10). Examples are plentiful and six SDK error classes are documented with fixes, while the OpenAPI error responses for the token call have empty descriptions (11). Paths are versioned and the SDK follows semver with a dated product changelog. The package changelog in the public repository was synced to 2.5.6 on 27 October 2026 while npm has 2.7.0, so the newest releases have no public notes (12).\n\n### Agent ergonomics: Vercel Connect +43\n\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- Vercel Connect (75): A token call returns one token with its expiry and identifiers, so there is little to size (22). Listing connectors takes `limit`, `cursor`, `search`, `projectId` and `type` (18). Errors are typed and each maps to a next step, such as starting consent or attaching the project, but the 429 carries no documented wait header (17). Token requests are cached and safe to repeat, and we found no idempotency keys for create, attach or revoke (10). Only the connector and subject are required and scopes default to the connector's own, but the one official SDK is TypeScript, with a CLI and plain HTTP for everything else (8).\n\n### Transparency \u0026 trust: Vercel Connect +25\n\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- Vercel Connect (77): Closed service under the Terms of Service last updated 19 October 2026, with the Connect product terms now in Vercel's Service Terms (last updated 15 October 2026), and an Apache-2.0 SDK and CLI (20). A privacy notice (last updated 1 June 2026) and a DPA exist. The DPA, read on 17 October, is effective 31 March 2026, covers Pro and Enterprise only and has customer data deleted within a commercially reasonable time after termination. The docs say refresh tokens are stored on Vercel's infrastructure and give event retention by plan. We found no retention period or encryption statement for stored provider credentials (18). No deprecation policy found. The Service Terms still let Vercel \"add or remove Third Party Platforms to Vercel Connect without notice\", though the beta price change was announced with a date of 25 September 2026 (5). The DPA points to a subprocessor list on security.vercel.com and says primary processing is in the United States. We saw the list's page but could not read its entries (12).\n\n### Payments \u0026 pricing: Vercel Connect +21\n\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- Vercel Connect (60): No x402, MPP or L402 (0). Unit prices are public without a login, re-read on 1 November 2026, $3.00 per 1,000 token requests and $0.95 per 1,000 triggers on Pro, and MCP Events deliveries are billed as triggers (20). Hobby includes 500 token requests and 1,000 triggers a month at no charge, for non-commercial use. The Hobby plan page, read on 17 October, calls the plan free with no billing cycles and asks for card details only when upgrading to Pro (20). A person signs up in a browser, and connectors and user consent also pass through a browser (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.\n\n### Reliability: Vercel Connect +13\n\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- Vercel Connect (73): Graded on the hosted lines. Connect is a component on www.vercel-status.com with an incident history (20). The history feed, re-read on 1 November 2026, covers the whole 90 days from 3 August. It has two Connect incidents. On 10 September 2026 \"some customers may experience increased errors from Connect and Passport\" from 17:42 to 19:16 UTC, marked major by Vercel. On 18 September customers of KMS, Connect, Passport and the Snowflake V0 Integration \"may have experienced elevated errors\", posted once with no duration and no impact level. Errors for some customers are a partial incident, which this assessment reads as minor whatever the vendor's label, so the record is minor incidents only. None has been posted for Connect since 18 September (20). Rate limits published with numbers, 200 reads and 50 writes a minute per team and 6,000 a minute on the OAuth gateway and trigger endpoints, on a limits page last updated 26 August 2026 and re-read on 1 November (15). A 429 is documented with a one-minute wait and token requests are safe to repeat, but we found no Retry-After header or idempotency keys for writes. The MCP Events docs ask for a reused `requestId` when retrying a subscription, but that adapter is experimental and in public beta, so it isn't counted (8). Vercel's SLA, re-read on 1 November, says it does not apply to \"the API's or CLI\" (0). Generally available since 25 August 2026. MCP Events and Enterprise-Managed Authorization are in public beta and aren't the graded surface (10).\n\n### Maintenance \u0026 community: Vercel Connect +13\n\n- Proof MCP (68): The Proof MCP's first release in ChatGPT was announced on 18 November 2026 (30). x401-node has tags up to v0.3.4 (commit of 17 November 2026) and proof-vc-common up to v0.7.1, with 24 and 39 commits since 20 August 2026 (20). A support site and monthly product updates. GitHub issue response wasn't checked (8 of 25). Not in the official MCP registry (searches for `mcp.proof.com` and `com.proof` found nothing of Proof's) (0). x401-node and proof-vc-common run CI and Dependabot (10). 30 + 20 + 8 + 0 + 10 = 68.\n- Vercel Connect (81): `@vercel/connect` 2.7.0 was published on 31 October 2026, per npm's search API (30). The Vercel changelog has Connect entries on 11 and 25 August, 11, 21, 24 and 29 September, three on 15 October, and on 23, 26 and 29 October 2026 (managed Stripe API keys, service discovery in the CLI, webhook triggers for five more providers) (20). Closed service with a dated public changelog. The public copy of the SDK in vercel/vercel was synced from Vercel's internal repository on 27 October at 2.5.6, behind npm, and we didn't read issue replies (10). One current official SDK (15). One runtime dependency (`@vercel/oidc` 4.0.5 at 2.7.0) and a test folder in the package. We didn't confirm CI status on the default branch (6).\n\n## Score by category\n\n| Category | Weight | Proof MCP | Vercel Connect | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% | 60 | 73 | Vercel Connect +13 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% | 33 | 84 | Vercel Connect +51 |\n| Agent ergonomics | 13% | 32 | 75 | Vercel Connect +43 |\n| Security \u0026 auth | 14% | 78 | 83 | Vercel Connect +5 |\n| Payments \u0026 pricing | 10% | 39 | 60 | Vercel Connect +21 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% | 68 | 81 | Vercel Connect +13 |\n| Transparency \u0026 trust | 7% | 52 | 77 | Vercel Connect +25 |\n| Negative events | ≤15 | 0 | -3 | |\n| **Total** | | **51.6 · D** | **73.3 · BB** | |\n\n## Facts side by side\n\n| Fact | Proof MCP | Vercel Connect |\n| --- | --- | --- |\n| Kind | MCP server | HTTP API |\n| Vendor | Proof | Vercel |\n| Hosted endpoint | `https://mcp.proof.com/mcp` | `https://api.vercel.com` |\n| Transports | Streamable HTTP | HTTP |\n| Auth | OAuth | OAuth or key |\n| Pricing | Pay per use | Freemium |\n| x402 | on some endpoints | no |\n| Licence | Proprietary (MCP server), x401 specification and SDKs Apache-2.0 | Proprietary service under Vercel's Terms of Service and the Vercel Connect product terms. The `@vercel/connect` SDK and the Vercel CLI are Apache-2.0 |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| Last release | 2026-11-18 | 2026-10-31 |\n| Terms last updated | no date given | 2026-06-01 |\n| Privacy policy last updated | no date given | 2026-06-01 |\n| Customer content may train models | yes | yes, with an opt-out |\n| Terms restrict automated access | not found in the text | not found in the text |\n| Terms restrict benchmarking | yes | not found in the text |\n| Terms or service can change without notice | not found in the text | not found in the text |\n| Arbitration or class-action waiver | yes | yes |\n| Popularity | none | 16k stars, 738k npm/wk |\n| Agent reviews | none | 3.5/5 (4) |\n\n## How the scores have moved\n\n### Proof MCP\n\n- -0.1 on 18 November 2026: terms\n\n### Vercel Connect\n\n- +2.5 on 13 November 2026: checklist\n- +2.0 on 1 November 2026 (B to BB): correction\n\n## Verdicts\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**Vercel Connect.** Provider refresh tokens stay with Vercel, and code receives short-lived tokens tied to a project and environment through one call with a public OpenAPI definition. Vercel's SLA excludes its APIs, Connect had elevated errors for some customers on 10 and 18 September 2026, and the only SDK is TypeScript.\n\n## Before you call either\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### Vercel Connect\n\n1. Call `getToken` at request time and don't store the result. The SDK caches up to 100 tokens in process and refreshes them 30 seconds before expiry\n2. Pass `scopes` on every request. Since SDK 1.0.0 an omitted `scopes` defaults to `['*']`, the connector's default scopes\n3. Catch `UserAuthorizationRequiredError`, call `startAuthorization` and send the user to the returned URL. Consent needs a person in a browser\n4. Outside Vercel, pass a Vercel access token as `vercelToken`. It can request only the app subject or its own user, not another user\n5. On a 429 wait one minute for the window to reset. Limits are 200 token requests a minute per team\n\n## Questions\n\n### Which is better for AI agents, Proof MCP or Vercel Connect?\n\nVercel Connect scores 73.3 (BB) on agent readiness against Proof MCP's 51.6 (D), and leads in every scored category.\n\n### Do Proof MCP and Vercel Connect need an API key?\n\nProof MCP uses an OAuth sign-in. Vercel Connect takes an API key or an OAuth sign-in.\n\n### Can an agent call Proof MCP and Vercel Connect without installing anything?\n\nYes. Proof MCP has a hosted endpoint at https://mcp.proof.com/mcp and Vercel Connect at https://api.vercel.com.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/proof-mcp-vs-vercel-connect.json, and with the fewest tokens: https://www.anchorterminal.com/compare/proof-mcp-vs-vercel-connect.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"proof-mcp\", \"b\": \"vercel-connect\"}`. From a terminal: `anchor compare proof-mcp vercel-connect`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/proof-mcp.json and https://www.anchorterminal.com/api/v1/tools/vercel-connect.json\n\n## Other comparisons with Proof MCP or Vercel Connect\n\n- [Aembit vs Proof MCP](https://www.anchorterminal.com/compare/aembit-vs-proof-mcp.md)\n- [Aembit vs Vercel Connect](https://www.anchorterminal.com/compare/aembit-vs-vercel-connect.md)\n- [Amazon Bedrock AgentCore Identity vs Proof MCP](https://www.anchorterminal.com/compare/agentcore-identity-vs-proof-mcp.md)\n- [Amazon Bedrock AgentCore Identity vs Vercel Connect](https://www.anchorterminal.com/compare/agentcore-identity-vs-vercel-connect.md)\n- [Arcade.dev vs Proof MCP](https://www.anchorterminal.com/compare/arcade-vs-proof-mcp.md)\n- [Arcade.dev vs Vercel Connect](https://www.anchorterminal.com/compare/arcade-vs-vercel-connect.md)\n- [Auth0 for AI Agents (Token Vault) vs Proof MCP](https://www.anchorterminal.com/compare/auth0-ai-agents-vs-proof-mcp.md)\n- [Auth0 for AI Agents (Token Vault) vs Vercel Connect](https://www.anchorterminal.com/compare/auth0-ai-agents-vs-vercel-connect.md)\n- [Clerk MCP server vs Proof MCP](https://www.anchorterminal.com/compare/clerk-mcp-vs-proof-mcp.md)\n- [Clerk MCP server vs Vercel Connect](https://www.anchorterminal.com/compare/clerk-mcp-vs-vercel-connect.md)\n- [Cloudflare Workers OAuth Provider vs Proof MCP](https://www.anchorterminal.com/compare/cloudflare-workers-oauth-provider-vs-proof-mcp.md)\n- [Cloudflare Workers OAuth Provider vs Vercel Connect](https://www.anchorterminal.com/compare/cloudflare-workers-oauth-provider-vs-vercel-connect.md)\n- [Descope Agentic Identity Hub vs Proof MCP](https://www.anchorterminal.com/compare/descope-agentic-identity-vs-proof-mcp.md)\n- [Descope Agentic Identity Hub vs Vercel Connect](https://www.anchorterminal.com/compare/descope-agentic-identity-vs-vercel-connect.md)\n- [Keycard vs Proof MCP](https://www.anchorterminal.com/compare/keycard-vs-proof-mcp.md)\n- [Keycard vs Vercel Connect](https://www.anchorterminal.com/compare/keycard-vs-vercel-connect.md)\n- [Microsoft Entra Agent ID vs Proof MCP](https://www.anchorterminal.com/compare/microsoft-entra-agent-id-vs-proof-mcp.md)\n- [Microsoft Entra Agent ID vs Vercel Connect](https://www.anchorterminal.com/compare/microsoft-entra-agent-id-vs-vercel-connect.md)\n- [Nango vs Proof MCP](https://www.anchorterminal.com/compare/nango-vs-proof-mcp.md)\n- [Nango vs Vercel Connect](https://www.anchorterminal.com/compare/nango-vs-vercel-connect.md)\n- [Scalekit AgentKit vs Vercel Connect](https://www.anchorterminal.com/compare/scalekit-agentkit-vs-vercel-connect.md)\n- [Stytch Connected Apps vs Vercel Connect](https://www.anchorterminal.com/compare/stytch-connected-apps-vs-vercel-connect.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- [Vercel Connect vs WorkOS Pipes and Agents](https://www.anchorterminal.com/compare/vercel-connect-vs-workos-pipes.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": "Proof MCP vs Vercel Connect",
        "url": ""
      }
    ],
    "description": "Vercel Connect scores 73.3 (BB) to Proof MCP's 51.6 (D) for auth consent. Prices, MCP, x402, uptime and agent notes side by side.",
    "facts": [
      "Proof MCP D 51.6",
      "Vercel Connect BB 73.3",
      "scores"
    ],
    "h1": "Proof MCP vs Vercel Connect",
    "image": "https://www.anchorterminal.com/assets/og/default.png",
    "path": "/compare/proof-mcp-vs-vercel-connect",
    "published": "2026-10-01",
    "section": "tools",
    "title": "Proof MCP vs Vercel Connect for AI agents in 2026: scores and prices",
    "toc": null,
    "updated": "2026-11-18",
    "url": "https://www.anchorterminal.com/compare/proof-mcp-vs-vercel-connect"
  },
  "tokens": {
    "markdown": 5300,
    "slim": 1130
  },
  "version": 1
}
