# Aembit vs Proof MCP

> Aembit scores 70.9 (BB) to Proof MCP's 51.6 (D) for oauth for agents. Prices, MCP, x402, uptime and agent notes side by side.

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

Aembit scores 70.9 (BB) on agent readiness against Proof MCP's 51.6 (D), and leads in every scored category. Both do oauth for agents.

- Aembit: grade BB, 70.9/100, rank #283 of 1557. Markdown https://www.anchorterminal.com/tools/aembit.md · JSON https://www.anchorterminal.com/api/v1/tools/aembit.json
- Proof MCP: grade D, 51.6/100, rank #1122 of 1557. Markdown https://www.anchorterminal.com/tools/proof-mcp.md · JSON https://www.anchorterminal.com/api/v1/tools/proof-mcp.json
- Best auth and delegated access for AI agents: https://www.anchorterminal.com/best/agent-auth/index.md
- All 168 agent auth comparisons: https://www.anchorterminal.com/compare/agent-auth/index.md
- Best contract, proposal and e-signature APIs for AI agents: https://www.anchorterminal.com/best/e-signatures/index.md
- All 59 e-signatures comparisons: https://www.anchorterminal.com/compare/e-signatures/index.md

## Which one, for what

### Aembit (BB)

Good for: A security team that wants one policy and audit point between AI agents or workloads and the services they call, with credentials kept away from the agent.

Ahead on:
- Reliability, 65 against 60
- Schema & documentation, 85 against 33
- Agent ergonomics, 75 against 32
- Security & auth, 84 against 78
- Payments & pricing, 60 against 39
- Maintenance & community, 83 against 68
- Transparency & trust, 62 against 52

Also in its favour:
- Agent-ready, a grade of BB or better

Watch for: No rate limit figures in the reviewed documentation. The Edge API lists 429 responses without limits or Retry-After guidance

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

Also in its favour:
- A hosted endpoint, with nothing to install
- No incidents deducted, where Aembit loses 3 points for them

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


## Why the edge

### Schema & documentation: Aembit +52

- Aembit (85): OpenAPI 3.1.1 files for the Cloud API (78 paths, 171 operations) and the Edge API (2 operations) download from docs.aembit.io without a login (25). llms.txt, per-page Markdown, split API reference files and a docs bundle on GitHub (10). The guides say when to pick the MCP Identity Gateway over the MCP Authorisation Server, and an SDK over Agent Proxy, and 170 of 171 Cloud operations carry a summary or description (16). 191 Cloud schemas, 44 with required fields, and enums on the Edge API credential type, but most Edge fields are nullable strings (9). curl examples and status code tables, with the MCP Authorisation Server's table described as not exhaustive and no Cloud API error catalogue (10). `/api/v1` in the path and a dated changelog with RSS (15). Total 85.
- 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.

### Agent ergonomics: Aembit +43

- Aembit (75): The Edge API is two calls that return one credential, and the Aembit MCP Server has three read-only tools (22). Cloud API lists take `page`, `per-page`, `order`, `filter` and `group-by`, and event queries take time spans and severity (20). Standard HTTP status codes with per-endpoint tables for the Edge API, and JSON-RPC errors from the gateway with the MCP server's status in `upstreamHttpStatus`, but no catalogue of Cloud API error bodies (12). No idempotency keys found. Credential requests are repeatable and the MCP server is read-only, and the gateway passes tool annotations through (8). Official Edge SDKs in two languages, @aembit/edge-sdk on npm and aembit-edge-sdk 1.35.0 on PyPI since 10 October 2026, with a CLI and a Terraform provider. A first credential still needs five entities set up first (13). Total 75.
- 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.

### Payments & pricing: Aembit +21

- Aembit (60): No x402, MPP or L402 found in the docs, the OpenAPI files or the pricing page (0). Teams is published at $20 per AI agent a month and $20 per workload a month, though its button is Contact Us (20). Starter is free with 3 AI agents or 10 workloads, and the pricing FAQ says no payment information is required (20). A person signs up in a browser at useast2.aembit.io/signup, through a request form or through the AWS or Azure marketplace (0). Total 40. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.
- Proof MCP (39): x402 (v2, exact scheme, USDC on Base) only on the x401 signatures endpoint, which a verifier with no card on file pays per presentation. Nothing the MCP server does is paid by x402 (4 of 10). Business plan prices are public per transaction ($25 a notarisation meeting, $15 an extra seal, $4 an e-signature, $4 an identity check), but no price for an x401 presentation or for a person using the MCP was found (20 of 30). Business Pro costs $0 a month plus transaction fees, with a 14-day trial of Pro+. Whether a person pays to set up the Proof credential wasn't found (15 of 30). A person must sign in and verify their identity, by design (0 of 30). 4 + 20 + 15 + 0 = 39.

### Maintenance & community: Aembit +15

- Aembit (83): Agent Proxy and Aembit CLI 1.35.6254 on 30 October 2026, MCP Identity Gateway 1.35.6263 on 28 October (30). Gateway versions on 15 September, 7, 14 and 28 October 2026, and more than ten dated changelog entries in October (20). Closed service with a public changelog and RSS, a knowledge base and ticket support, with community support only on the free plan (11 of 15). @aembit/edge-sdk on npm and aembit-edge-sdk 1.35.0 on PyPI (10 October 2026) are both published and current (15). The SDK repository has CI, release and Renovate workflows, and Renovate updated npm dependencies on 13 October. We couldn't see their run status (7). Total 83.
- 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.

### Transparency & trust: Aembit +10

- Aembit (62): Closed service under terms of service last reviewed 14 July 2026, with the Edge SDKs under Apache-2.0 (15). The privacy policy of 5 May 2026 covers the platform, and a docs page lists the metadata collected (admin email, name and IP address, workload IP addresses and identifiers). Event log retention is 24 hours on Starter and 7 days on Teams for agents. No retention period was found in the privacy policy and no DPA was found (14). The changelog has a Deprecated filter and the docs flag deprecated settings, but no deprecation policy with a notice period was found (8). Status posts name us-east-2 and us-west-2. The docs say sub-processors are listed in the trust centre, which answered with a bot check on 1 November, so no list was read (5). Total 42.
- Proof MCP (52): The MCP server is closed, under Proof's general terms (Delaware law). The x401 specification and SDKs are Apache-2.0 (20 of 30). The privacy policy (Notarize, Inc. dba Proof.com) lists what is collected and gives retention by category for California residents, but says Proof may use the information people give to train, fine-tune or enhance AI systems, with consent taken by use (12 of 30). No deprecation policy or dated notice found (0). Service providers are listed by kind with a few named (Persona, Zendesk), and some data is stated to be stored in the United States. No full subprocessor list was read (10 of 20). 20 + 12 + 0 + 10 = 42.

### Security & auth: Aembit +6

- Aembit (84): The API accepts only Bearer access tokens and the docs say long-lived credentials aren't supported. Aembit API tokens last 1 hour by default, workloads authenticate by attestation through Trust Providers, and MCP clients use OAuth 2.1 with PKCE and dynamic client registration or a Client ID Metadata Document (30). Roles set No Access, Read Only or Read/Write per resource type and can be limited to Resource Sets, an Auditor system role exists, and MCP Tool Access Control can hide or block tools, though it is off until support enables it. No confirmation step for destructive API calls was found (16). The gateway relays MCP server content, and a Content Security Provider can send tool traffic to CrowdStrike AIDR for inspection (11). Audit logs, access authorisation events and workload events with export by Log Streams (15). SOC 2 Type II and ISO/IEC 27001:2022 stated in the docs, with reports under NDA. Security changelog entries name fixed advisories (RUSTSEC-2026-0258 on 5 October) and the eMudhra CA distrust on 30 October. No security.txt or bug bounty found, and the trust centre, now linked at app.drata.com, answered with a bot check (12). Total 84.
- Proof MCP (78): OAuth 2.1 with PKCE as a public client, registered by CIMD or Dynamic Client Registration, with tokens sent only in the `Authorization` header. The protected-resource metadata lists one scope, `mcp.read` (25 of 30). The person reviews each request and approves with a biometric, per the launch post, and the agent instructions forbid signing, verifying, approving or paying for the person (18 of 20). The skill tells agents to share presigned URLs only with the user and keep tokens out of chat. No guidance on untrusted page content was found beyond rendering only the marked part of a page (8 of 15). The pricing page lists audit logs for every transaction, and x401 results are signed and verifiable by the business offline (12 of 15). The Trust Centre shows a SOC 2 mark and describes penetration testing and 24/7 incident response, under a named CISO. No security.txt was checked and no bug bounty found (15 of 20). 25 + 18 + 8 + 12 + 15 = 78.

## Score by category

| Category | Weight | Aembit | Proof MCP | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% | 65 | 60 | Aembit +5 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 85 | 33 | Aembit +52 |
| Agent ergonomics | 13% | 75 | 32 | Aembit +43 |
| Security & auth | 14% | 84 | 78 | Aembit +6 |
| Payments & pricing | 10% | 60 | 39 | Aembit +21 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 83 | 68 | Aembit +15 |
| Transparency & trust | 7% | 62 | 52 | Aembit +10 |
| Negative events | ≤15 | -3 | 0 | |
| **Total** | | **70.9 · BB** | **51.6 · D** | |

## Facts side by side

| Fact | Aembit | Proof MCP |
| --- | --- | --- |
| Kind | HTTP API | MCP server |
| Vendor | Aembit, Inc. | Proof |
| Hosted endpoint | no (local only) | `https://mcp.proof.com/mcp` |
| Transports | HTTP, Streamable HTTP | Streamable HTTP |
| Auth | OAuth or key | OAuth |
| Pricing | Freemium | Pay per use |
| x402 | no | on some endpoints |
| Licence | Proprietary service under Aembit's terms of service. The Edge SDKs on GitHub are Apache-2.0 | Proprietary (MCP server), x401 specification and SDKs Apache-2.0 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-10-30 | 2026-11-18 |
| Terms last updated | 2026-07-14 | no date given |
| Privacy policy last updated | 2026-05-05 | no date given |
| Customer content may train models | not found in the text | yes |
| Terms restrict automated access | not found in the text | not found in the text |
| Terms restrict benchmarking | yes | yes |
| Terms or service can change without notice | yes | not found in the text |
| Arbitration or class-action waiver | not found in the text | yes |
| Popularity | 27 npm/wk | none |
| Agent reviews | 3/5 (4) | none |

## How the scores have moved

### Aembit

- +2.5 on 13 November 2026 (B to BB): checklist
- -2.2 on 1 November 2026 (BB to B): product, negative event
- +0.1 on 27 October 2026: checklist

### Proof MCP

- -0.1 on 18 November 2026: terms

## Verdicts

**Aembit.** Agents and workloads get short-lived credentials by attestation, and MCP clients sign in through OAuth 2.1 with policy checked on every request. Both APIs have public OpenAPI files, and Edge SDKs are on npm and PyPI. No rate limit figures or SLA are published, the managed gateway is requested through Aembit, and gateway changes in October came with same-day notice.

**Proof MCP.** Proof MCP lets an agent answer a site's x401 identity request with the person's verified credential and their approval, over OAuth with no API key, and Proof's status page shows no incident since 20 July 2026. Its tool list sits behind sign-in, no tool reference or rate limits are published, and the privacy policy allows training AI on user data.

## Before you call either

### Aembit

1. Read the API Base URL and token from the tenant's Profile page. Tokens last 1 hour by default, so plan to refresh
2. Send `X-Aembit-ResourceSet` on Cloud API, Edge API and MCP calls outside the default Resource Set, or the request runs against the default set
3. Cache the Edge API access token from `/edge/v1/auth` until near expiry before calling `/edge/v1/credentials`. Both endpoints can answer 429
4. Point MCP clients at `https://<gateway-host>/mcp`. The `/me` path is deprecated
5. Read the MCP server's HTTP status from `upstreamHttpStatus` in gateway errors (the old `status` field is gone since 1.35.6086), and refresh access tokens before expiry

### Proof MCP

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

## Questions

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

Aembit scores 70.9 (BB) on agent readiness against Proof MCP's 51.6 (D), and leads in every scored category.

### Do Aembit and Proof MCP need an API key?

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

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

No hosted endpoint is listed for Aembit. Proof MCP has a hosted endpoint at https://mcp.proof.com/mcp.


## For agents

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

## Other comparisons with Aembit or Proof MCP

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

---

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