# Aembit vs Proof MCP (slim)

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

- Full: https://www.anchorterminal.com/compare/aembit-vs-proof-mcp.md (~5,050 tokens) · this version ~1,130 tokens · JSON https://www.anchorterminal.com/compare/aembit-vs-proof-mcp.json · canonical https://www.anchorterminal.com/compare/aembit-vs-proof-mcp
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-18
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

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: BB 70.9, rank #283 of 1557 · https://www.anchorterminal.com/tools/aembit.min.md
- Proof MCP: D 51.6, rank #1122 of 1557 · https://www.anchorterminal.com/tools/proof-mcp.min.md
- Aembit, 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 Agent-ready, a grade of BB or better.
- Proof MCP, 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 A hosted endpoint, with nothing to install; No incidents deducted, where Aembit loses 3 points for them.

| Category | Aembit | Proof MCP |
| --- | --- | --- |
| Reliability (16%) | 65 | 60 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 85 | 33 |
| Agent ergonomics (13%) | 75 | 32 |
| Security & auth (14%) | 84 | 78 |
| Payments & pricing (10%) | 60 | 39 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 83 | 68 |
| Transparency & trust (7%) | 62 | 52 |

| Fact (where they differ) | 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 |
| 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 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 |

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).); 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).)
- 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).); Proof MCP 32 (Tool count and size unknown, since the list is behind sign-in.)
- Payments & pricing, Aembit +21: Aembit 60 (No x402, MPP or L402 found in the docs, the OpenAPI files or the pricing page (0).); 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.)
- 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).); Proof MCP 68 (The Proof MCP's first release in ChatGPT was announced on 18 November 2026 (30).)
- 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).); Proof MCP 52 (The MCP server is closed, under Proof's general terms (Delaware law).)
- Security & auth, Aembit +6: Aembit 84 (The API accepts only Bearer access tokens and the docs say long-lived credentials aren't supported.); 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.)
