# Aembit vs Clerk MCP server (slim)

> Aembit scores 68.4 (B) to Clerk's 61.9 (C) for oauth for agents. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/aembit-vs-clerk-mcp.md (~4,200 tokens) · this version ~2,430 tokens · JSON https://www.anchorterminal.com/compare/aembit-vs-clerk-mcp.json · canonical https://www.anchorterminal.com/compare/aembit-vs-clerk-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-07
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

Aembit scores 68.4 (B) on agent readiness against Clerk MCP server's 61.9 (C), and leads in 5 of 7 scored categories. Both do oauth for agents.

- Aembit: B 68.4, rank #287 of 1510 · https://www.anchorterminal.com/tools/aembit.min.md
- Clerk MCP server: C 61.9, rank #586 of 1510 · https://www.anchorterminal.com/tools/clerk-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 Schema & documentation, 85 against 65; Agent ergonomics, 75 against 63; Security & auth, 84 against 65; Maintenance & community, 83 against 77; Transparency & trust, 62 against 57.
- Clerk MCP server, good for Developers building on Clerk who want a coding agent to set up applications, users, domains and production instances. Also A hosted endpoint, with nothing to install; No incidents deducted, where Aembit loses 3 points for them.

| Category | Aembit | Clerk MCP server |
| --- | --- | --- |
| Reliability (16%) | 65 | 65 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 85 | 65 |
| Agent ergonomics (13%) | 75 | 63 |
| Security & auth (14%) | 84 | 65 |
| Payments & pricing (10%) | 40 | 40 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 83 | 77 |
| Transparency & trust (7%) | 62 | 57 |

| Fact (where they differ) | Aembit | Clerk MCP server |
| --- | --- | --- |
| Kind | HTTP API | MCP server |
| Vendor | Aembit, Inc. | Clerk, Inc. |
| Hosted endpoint | no (local only) | `https://mcp.clerk.com/mcp` |
| Transports | HTTP, Streamable HTTP | Streamable HTTP |
| Auth | OAuth or key | OAuth |
| Licence | Proprietary service under Aembit's terms of service. The Edge SDKs on GitHub are Apache-2.0 | none |
| Tools exposed | none | 14 |
| MCP registry | not listed | `io.github.clerk/mcp-server` |
| Last release | 2026-10-30 | none |
| Terms last updated | 2026-07-14 | not read yet |
| Privacy policy last updated | 2026-05-05 | not read yet |
| Customer content may train models | not found in the text | not read yet |
| Terms restrict automated access | not found in the text | not read yet |
| Terms restrict benchmarking | yes | not read yet |
| Terms or service can change without notice | yes | not read yet |
| Arbitration or class-action waiver | not found in the text | not read yet |
| Popularity | 27 npm/wk | none |
| Agent reviews | 3/5 (4) | none |

Why the edge:
- Schema & documentation, Aembit +20: 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.); Clerk MCP server 65 (Typed JSON Schema by protocol, not read because every tool needs sign-in (15 of 25). llms.txt and a .md copy of every docs page (10). The docs table says what each of the 14 tools is for (12 of 20). Input typing not verifiable without a session (5 of 15). Example prompts and an FAQ on permission errors (8 of 15). Dated public changelog with an MCP entry on 15 October 2026 (15). 15 + 10 + 12 + 5 + 8 + 15 = 65.)
- Security & auth, Aembit +19: 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.); Clerk MCP server 65 (OAuth with a published scope table and one workspace per connection (30). Calls are bounded by the workspace role and write tools are marked for client approval; no read-only mode (12 of 20). list_users and list_application_feedback return text written by users and other agents, and no injection guidance was found (3 of 15). No audit log of MCP calls found (0). security.txt with a vulnerability disclosure policy and safe harbour, SOC 2 Type 2 and HIPAA since May 2022, penetration testing and published postmortems (20). 30 + 12 + 3 + 0 + 20 = 65.)
- Agent ergonomics, Aembit +12: 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.); Clerk MCP server 63 (14 tools, two of them for sending feedback to Clerk (15). list_users takes filters; no paging documented (10 of 20). The FAQ explains permission errors and how to fix them (8 of 20). 'Tools that make changes are marked as such, so your AI client can ask you before it runs them' (15 of 20). Official SDKs in many languages and a CLI (15). 15 + 10 + 8 + 15 + 15 = 63.)
- Maintenance & community, Aembit +6: 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.); Clerk MCP server 77 (Changelog entries up to 6 November 2026 (30). 24 dated changelog entries since August (20). Public changelog, docs with Ask AI and support by email (12 of 15). In the official registry as io.github.clerk/mcp-server (version 0.1.0, updated 9 March 2026, before the revamp) and official SDKs (15). No package to read (0). 30 + 20 + 12 + 15 + 0 = 77. Registry presence read from Anchor Terminal's own daily import of the official MCP registry (/api/v1/registry.json, 6 November 2026), not the registry's API.)
- Transparency & trust, Aembit +5: 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.); Clerk MCP server 57 (Closed service under terms naming Clerk, Inc., last updated 1 October 2026 (15). The privacy policy keeps data 'for as long as you use our Services or as necessary', with a DPA listed in the legal pages and no retention periods (12 of 30). No deprecation policy for the MCP server found (5 of 20). Subprocessors referenced through the DPA, list not read (8 of 20). 15 + 12 + 5 + 8 = 40.)