# Proof MCP vs Scalekit AgentKit

> Scalekit AgentKit scores 74.7 (BB) to Proof MCP's 51.6 (D) for auth agent identity. Prices, MCP, x402, uptime and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/proof-mcp-vs-scalekit-agentkit
- Markdown: https://www.anchorterminal.com/compare/proof-mcp-vs-scalekit-agentkit.md (~5,200 tokens)
- Slim: https://www.anchorterminal.com/compare/proof-mcp-vs-scalekit-agentkit.min.md (~1,180 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/proof-mcp-vs-scalekit-agentkit.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-18

Scalekit AgentKit scores 74.7 (BB) on agent readiness against Proof MCP's 51.6 (D), and leads in 6 of 7 scored categories. Proof MCP leads on security & auth. Both do auth agent identity.

- 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
- Scalekit AgentKit: grade BB, 74.7/100, rank #132 of 1557. Markdown https://www.anchorterminal.com/tools/scalekit-agentkit.md · JSON https://www.anchorterminal.com/api/v1/tools/scalekit-agentkit.json
- Best auth and delegated access for AI agents: https://www.anchorterminal.com/best/agent-auth/index.md
- All 168 agent auth comparisons: https://www.anchorterminal.com/compare/agent-auth/index.md
- Best contract, proposal and e-signature APIs for AI agents: https://www.anchorterminal.com/best/e-signatures/index.md
- All 59 e-signatures comparisons: https://www.anchorterminal.com/compare/e-signatures/index.md

## Which one, for what

### Proof MCP (D)

Good for: Agents that must show a site who they act for and that the person approved, and agents sending documents for e-signature or notarisation.

Ahead on:
- Security & auth, 78 against 66

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

### Scalekit AgentKit (BB)

Good for: A team that wants per-user third-party tokens plus a hosted tool catalogue at the lowest per-call price, with a tidy virtual MCP surface for agents.

Ahead on:
- Reliability, 72 against 60
- Schema & documentation, 87 against 33
- Agent ergonomics, 88 against 32
- Payments & pricing, 60 against 39
- Maintenance & community, 80 against 68
- Transparency & trust, 66 against 52

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

Watch for: No published rate-limit figure and no idempotency keys for Scalekit's own API


## Why the edge

### Agent ergonomics: Scalekit AgentKit +56

- 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.
- Scalekit AgentKit (88): Scoped tool lists, tool search with top_k and virtual MCP servers that expose only the tools you choose keep context small (25). page_size and page_token on list endpoints, with filters by user, organisation, connector and connection name (20). Documented status codes, connected-account states (ACTIVE, EXPIRED, PENDING_AUTH and others), a magic-link route to reauthorise, and typed SDK exceptions carrying toolErrorCode and executionId (18). No idempotency keys. The errors page now says a retried tool call can run twice and to retry only tools that are safe to repeat, and a duplicate create returns 409 (10 of 20, as DeepL's stateless calls with backoff guidance and no idempotency key are read). Official Node and Python SDKs and few required fields (15).

### Schema & documentation: Scalekit AgentKit +54

- 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.
- Scalekit AgentKit (87): OpenAPI 3.1.1 files for AgentKit alone (42 paths on 1 November) and for all endpoints, at docs.scalekit.com/api/agentkit.scalar.json (25). llms.txt with full and small variants, and a Markdown twin for each page (10). Connector pages and the API reference say what each endpoint and connector type is for (15). Filters are typed and constraints stated, for example a search query of at least 3 characters, top_k up to 50 and MCP session tokens from 60 seconds to 24 hours (13). Status codes 400, 401, 403, 404, 409 and 500 are documented, but many response examples are null placeholders (9). Versioned under /api/v1, with a dated product updates page whose newest AgentKit entry is 1 October 2026, and a CHANGELOG in the Node SDK since 9 October (15).

### Payments & pricing: Scalekit AgentKit +21

- 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.
- Scalekit AgentKit (60): No x402, MPP or L402 (0). Per-call price published, $0.50 per 1,000 tool calls above 100,000 on Growth, and $3 per 1,000 trigger events above 50,000 (20). Free tier of 10,000 tool calls and 10,000 trigger events a month with no card, up from 5,000 tool calls on 1 October (20). A person creates an account and copies API credentials from the dashboard (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.

### Transparency & trust: Scalekit AgentKit +14

- 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.
- Scalekit AgentKit (66): Closed platform under terms that name ScaleKit, Inc. and Delaware law (effective 1 January 2026), with MIT SDKs (15). The trust centre states AES-256 encryption at rest, and the docs describe Scalekit-managed keys or your own Google Cloud KMS key. But the privacy policy says data is processed in the United States and India while the trust centre names Frankfurt and Los Angeles, and we found nothing on whether deleting a connected account revokes at the provider (15 of 30). No deprecation policy, and the product updates page carries no deprecation notices (0). Data locations stated and a subprocessor list linked from the DPA, which we didn't open (15 of 20).

### Reliability: Scalekit AgentKit +12

- 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.
- Scalekit AgentKit (72): The status page is scalekit.statuspage.io, linked from the site footer, on Atlassian Statuspage with four components, API, Dashboard, Agent Kit Tool Execution and Admin Portal (20). The history page was readable on 1 November. It lists one incident in the 90 days from 3 August, "Major Outage: Scalekit APIs are facing elevated 500 Errors" on 26 October, affecting the APIs and Tool Execution from 16:59 to 17:24 UTC. Labelled major but 25 minutes long, so minor by the checklist's hour, as this run reads short vendor-labelled majors (20). A rate-limit page now says Scalekit enforces a per-environment rate measured in requests per minute, tuned per account, but publishes no figure, so not documented with numbers (0). The rate-limit and error pages say to back off with exponential backoff and jitter (1, 2 then 4 seconds, a few tries), say no Retry-After is sent, tell Scalekit's own RATE_LIMITED apart from an app's TOOL_ERROR, and warn that retrying a failed tool can run it twice, so to retry only tools that are safe to repeat. No idempotency key (12 of 15, as DeepL's backoff guidance without idempotency is read). Enterprise lists a 99.99 per cent uptime SLA on the pricing page (10). No beta labels on the AgentKit endpoints (10). 20+20+0+12+10+10 = 72.

### Security & auth: Proof MCP +12

- 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.
- Scalekit AgentKit (66): Your backend trades a client ID and secret for a short-lived bearer token, and virtual MCP session tokens are per user with a one-hour default, but `GET /api/v1/connected_accounts/auth` returns a user's full OAuth tokens to any holder of the API credential (26). Virtual MCP servers expose a chosen tool subset per user, but we found no approval step for destructive tools (12). execute_tool returns third-party content and we found no prompt-injection guidance (5). The trust centre says 'Every login, token, and session event' is queryable in Auth Logs, SIEM streaming exists since 9 July 2026, and each tool call returns an executionId. We found no AgentKit-specific audit log (8 of 15). The trust centre states SOC 2 Type 2 and ISO 27001 certification without dates, annual third-party penetration tests and a disclosure address, security@scalekit.com. /.well-known/security.txt returns 404 and we found no bug bounty (15 of 20).

## Score by category

| Category | Weight | Proof MCP | Scalekit AgentKit | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% | 60 | 72 | Scalekit AgentKit +12 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 33 | 87 | Scalekit AgentKit +54 |
| Agent ergonomics | 13% | 32 | 88 | Scalekit AgentKit +56 |
| Security & auth | 14% | 78 | 66 | Proof MCP +12 |
| Payments & pricing | 10% | 39 | 60 | Scalekit AgentKit +21 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 68 | 80 | Scalekit AgentKit +12 |
| Transparency & trust | 7% | 52 | 66 | Scalekit AgentKit +14 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **51.6 · D** | **74.7 · BB** | |

## Facts side by side

| Fact | Proof MCP | Scalekit AgentKit |
| --- | --- | --- |
| Kind | MCP server | HTTP API |
| Vendor | Proof | Scalekit |
| Hosted endpoint | `https://mcp.proof.com/mcp` | `https://{env}.scalekit.com` |
| Transports | Streamable HTTP | HTTP, Streamable HTTP |
| Auth | OAuth | OAuth or key |
| Pricing | Pay per use | Freemium |
| x402 | on some endpoints | no |
| Licence | Proprietary (MCP server), x401 specification and SDKs Apache-2.0 | MIT (SDKs), platform closed, self-hosted on Enterprise |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-11-18 | 2026-10-30 |
| Terms last updated | no date given | 2026-01-01 |
| Privacy policy last updated | no date given | 2026-01-01 |
| Customer content may train models | yes | not found in the text |
| Terms restrict automated access | not found in the text | yes |
| Terms restrict benchmarking | yes | yes |
| Terms or service can change without notice | not found in the text | not found in the text |
| Arbitration or class-action waiver | yes | yes |
| Popularity | none | 6 stars, 11k npm/wk |
| Agent reviews | none | 2.5/5 (2) |

## How the scores have moved

### Proof MCP

- -0.1 on 18 November 2026: terms

### Scalekit AgentKit

- +2.5 on 13 November 2026: checklist
- +0.2 on 1 November 2026: reliability, product
- +0.1 on 27 October 2026: checklist

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

**Scalekit AgentKit.** 600+ connectors, including remote MCP servers over OAuth 2.1 with DCR, and a free tier of 10,000 tool calls a month without a card. Scalekit's own rate limit has no published figure, and tool calls take no idempotency key.

## Before you call either

### Proof MCP

1. Read the server instructions and every tool description before your first call, as Proof's skill asks
2. If a site returns 401 with a `PROOF-REQUEST` header, pass the header value unchanged to `x401_start_presentation`
3. Show the person any approval link first, then poll `x401_get_presentation` or `get_transaction_status` after each `retry_after_seconds`
4. Never ask the user for a Proof API key or token. The client registers itself with OAuth, scope `mcp.read`
5. Share a presigned download URL only with the user, since anyone holding it can download the file until it expires

### Scalekit AgentKit

1. Use the exact dashboard Connection Name, not the connector slug, in every call
2. Call `POST /api/v1/tools:search` with top_k instead of listing every tool
3. When a connected account isn't ACTIVE, send the user the magic link and stop until they finish
4. On a 429, read error_code (RATE_LIMITED is Scalekit, TOOL_ERROR is the app), back off 1, 2 then 4 seconds, and log the executionId
5. Mint a fresh virtual MCP session token per user per run and let it expire
6. Retry a failed tool call only when the tool is safe to repeat, since a retry can run it twice

## Questions

### Which is better for AI agents, Proof MCP or Scalekit AgentKit?

Scalekit AgentKit scores 74.7 (BB) on agent readiness against Proof MCP's 51.6 (D), and leads in 6 of 7 scored categories. Proof MCP leads on security & auth.

### Do Proof MCP and Scalekit AgentKit need an API key?

Proof MCP uses an OAuth sign-in. Scalekit AgentKit takes an API key or an OAuth sign-in.

### Can an agent call Proof MCP and Scalekit AgentKit without installing anything?

Yes. Proof MCP has a hosted endpoint at https://mcp.proof.com/mcp and Scalekit AgentKit at https://{env}.scalekit.com.


## For agents

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

## Other comparisons with Proof MCP or Scalekit AgentKit

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

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
