# Amazon Bedrock AgentCore Identity vs Clerk MCP server (slim)

> Amazon Bedrock AgentCore Identity scores 76.4 (BB) 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/agentcore-identity-vs-clerk-mcp.md (~5,300 tokens) · this version ~3,180 tokens · JSON https://www.anchorterminal.com/compare/agentcore-identity-vs-clerk-mcp.json · canonical https://www.anchorterminal.com/compare/agentcore-identity-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)

Amazon Bedrock AgentCore Identity scores 76.4 (BB) on agent readiness against Clerk MCP server's 61.9 (C), and leads in 6 of 7 scored categories. Clerk MCP server leads on payments & pricing. Both do oauth for agents.

- Amazon Bedrock AgentCore Identity: BB 76.4, rank #44 of 1510 · https://www.anchorterminal.com/tools/agentcore-identity.min.md
- Clerk MCP server: C 61.9, rank #586 of 1510 · https://www.anchorterminal.com/tools/clerk-mcp.min.md
- Amazon Bedrock AgentCore Identity, good for Agents already built on AWS, above all those on AgentCore Runtime or Gateway, where token retrieval is automatic and free of extra charge. Ahead on Reliability, 85 against 65; Schema & documentation, 88 against 65; Agent ergonomics, 76 against 63; Security & auth, 84 against 65; Maintenance & community, 85 against 77; Transparency & trust, 78 against 57. Also Agent-ready, a grade of BB or better.
- Clerk MCP server, good for Developers building on Clerk who want a coding agent to set up applications, users, domains and production instances. Ahead on Payments & pricing, 40 against 30.

| Category | Amazon Bedrock AgentCore Identity | Clerk MCP server |
| --- | --- | --- |
| Reliability (16%) | 85 | 65 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 88 | 65 |
| Agent ergonomics (13%) | 76 | 63 |
| Security & auth (14%) | 84 | 65 |
| Payments & pricing (10%) | 30 | 40 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 85 | 77 |
| Transparency & trust (7%) | 78 | 57 |

| Fact (where they differ) | Amazon Bedrock AgentCore Identity | Clerk MCP server |
| --- | --- | --- |
| Kind | HTTP API | MCP server |
| Vendor | Amazon Web Services | Clerk, Inc. |
| Hosted endpoint | `https://bedrock-agentcore.us-east-1.amazonaws.com` | `https://mcp.clerk.com/mcp` |
| Transports | HTTP | Streamable HTTP |
| Auth | OAuth or key | OAuth |
| Pricing | Pay per use | Freemium |
| Price for oauth for agents | $0.01 per 1,000 requests | not published |
| Licence | Proprietary service under the AWS Customer Agreement and AWS Service Terms. The AgentCore SDKs for Python and TypeScript are Apache-2.0 | none |
| Tools exposed | none | 14 |
| MCP registry | not listed | `io.github.clerk/mcp-server` |
| Last release | 2026-10-27 | none |
| Terms last updated | 2026-10-01 | not read yet |
| Privacy policy last updated | 2026-05-18 | not read yet |
| Customer content may train models | yes, with an opt-out | not read yet |
| Terms restrict automated access | yes | 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 | 335k npm/wk, 1.4M PyPI/wk | none |
| Agent reviews | 3.3/5 (4) | none |

Why the edge:
- Schema & documentation, Amazon Bedrock AgentCore Identity +23: Amazon Bedrock AgentCore Identity 88 (Service models for `bedrock-agentcore` and `bedrock-agentcore-control` are public in aws/api-models-aws and ship in the AWS SDKs. Read on 1 November, the data plane has seven Identity operations and the control plane 28 under `/identities` (25). llms.txt for the developer guide and for the API reference, with a Markdown twin of every page (10). API reference descriptions are one line each, while the guide says when to use the JWT route and when the user ID route (15 of 20). Typed members with enums, patterns and length limits, such as `oauth2Flow` and `credentialProviderVendor`, and one string map, `customParameters` (14 of 15). Named errors with HTTP codes on every operation and CLI and Python examples in the guide, but no examples on the API reference pages we read (12 of 15). Release notes by month without days, SDK changelogs with dates, and the notes' RSS feed was not found at the address we tried, per the 17 October check (12 of 15). 25 + 10 + 15 + 14 + 12 + 12 = 88.); 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.)
- Transparency & trust, Amazon Bedrock AgentCore Identity +21: Amazon Bedrock AgentCore Identity 78 (Closed service under the AWS Service Terms, last updated 30 October 2026 and re-read on 1 November, with Apache-2.0 SDKs (15 of 30). The Identity data protection pages state KMS encryption at rest with an optional customer managed key and warn that names and free-text fields can reach diagnostic logs. The privacy notice is dated 18 May 2026 (re-read). No retention period for stored tokens or request metadata was found (20 of 30). No deprecation policy for the service found. The one dated notice we saw is the starter toolkit's deprecation on 27 March 2026, in a security bulletin (8 of 20). A sub-processor list updated 30 October 2026 and regional endpoints in 21 Regions, with the vault held in the Region the owner picks (18 of 20). 15 + 20 + 8 + 18 = 61.); 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.)
- Reliability, Amazon Bedrock AgentCore Identity +20: Amazon Bedrock AgentCore Identity 85 (AWS Health Dashboard with a per-service, per-Region feed for Bedrock AgentCore (20). The us-east-1 and us-west-2 AgentCore feeds had no items on 1 November 2026 (last built 31 October). The dashboard's history file, re-read on 1 November, still lists one event naming AgentCore in the 90 days from 3 August, elevated packet loss in one Availability Zone of eu-south-2 on 4 October 2026 from 8:48 to 11:28 AM PDT, at informational status and shared with 31 other services. The only later entry is an API Gateway HTTP API error event in us-west-2 posted on 30 October, which doesn't name AgentCore. Minor only (20 of 30). Quotas published per operation, re-read on 1 November, 200 requests a second for `GetResourceOauth2Token` and the workload access token calls and 20 for management calls (15). The API reference documents `ThrottlingException` (429) and `InternalServerException` (500) with advice to retry with exponential backoff, but `CreateWorkloadIdentity` still takes no idempotency token in the service model read on 1 November (12 of 15). The AgentCore FAQ says the Amazon Bedrock SLA applies, 99.9 per cent a Region, though that SLA's definitions speak of model APIs and do not name AgentCore, per the 17 October check (8 of 10, our call). Generally available since October 2025, and the consent portal carries no preview label (10). 20 + 20 + 15 + 12 + 8 + 10 = 85.); Clerk MCP server 65 (Graded as a hosted service. incident.io status page at status.clerk.com with components for authentication, sessions, webhooks and SCIM, but none for the MCP server (15). The feed shows several resolved incidents since August (an upstream SMS issue on 29 October, Apple sign-in for development instances, an incident across all components on 3 November, resolved), none read as a long core outage (20). Backend API limits published with numbers (1,000 requests per 10 seconds in production), not for the MCP server itself (10 of 15). 429 with Retry-After documented, no idempotency guidance for writes (10 of 15). No SLA found; Business support has 'No response-time SLA' (0). The MCP server isn't labelled beta (10). 15 + 20 + 10 + 10 + 0 + 10 = 65.)
- Security & auth, Amazon Bedrock AgentCore Identity +19: Amazon Bedrock AgentCore Identity 84 (IAM with SigV4 and short-lived role credentials, plus a workload access token that carries the agent's identity and the user's, and policies that name one workload identity and one credential provider ARN (30). Users consent through the provider's own OAuth screen with session binding, but AWS says the service enforces no binding between workload identities and credential providers beyond the owner's IAM policy, the user ID route is unverified, and no call to revoke one user's grant was found. `ResetTokenVaultKeyMaterial`, added on 27 October 2026, deletes every stored token in a vault and works only after its customer managed key is deleted, so it isn't a per-user revoke (15 of 20). The service returns tokens and keys, not untrusted content (10). The guide points to CloudTrail for `GetWorkloadAccessTokenForUserId` calls and KMS signing, but the developer guide's llms.txt, re-read on 1 November, still has CloudTrail pages for Gateway and none for Identity (11 of 15). A disclosure programme on HackerOne, public bulletins (none in the feed on 1 November names Identity), AgentCore in SOC 1, 2 and 3 scope on the list of 11 August 2026 (re-read on 1 November) and ISO 27001 per the compliance page. The aws.amazon.com security.txt, re-read on 1 November, expires on 16 October 2027, but the VDP names no paid bounty, so 2 points stay held back, as on the Secrets Manager, SES and Polly re-checks of 17 October (18 of 20). 30 + 15 + 10 + 11 + 18 = 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, Amazon Bedrock AgentCore Identity +13: Amazon Bedrock AgentCore Identity 76 (Responses are small, a token or an authorisation URL with a session status, and list calls take `maxResults`. There is no MCP server for Identity to weigh (20 of 25). List operations page with `nextToken` and `maxResults`, and no filters were found (15 of 20). Named exceptions with recovery advice, and a missing consent comes back as `authorizationUrl` and `sessionUri` in a 200 response, which an agent can act on (18 of 20). Token reads are safe to repeat and `forceAuthentication` restarts consent, but no client token for idempotent creates was found and there are no MCP annotations (10 of 20). AWS SDKs in nine languages plus AgentCore SDKs for Python and TypeScript with `@requires_access_token` and `@requires_api_key` decorators. `GetResourceOauth2Token` has four required members, and user-delegated flows need the owner to host a callback endpoint (13 of 15).); 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.)
- Payments & pricing, Clerk MCP server +10: Amazon Bedrock AgentCore Identity 30 (No x402, MPP or L402 for paying AWS. AgentCore payments is a separate capability for agents paying third parties (0). $0.010 per 1,000 token or API key requests on the public pricing page, re-read on 1 November, with no extra charge through AgentCore Runtime or Gateway (20). No Identity free tier, but new accounts get up to $200 of Free Tier credit and the Free Tier FAQ, re-read on 1 November, says most new customers need no payment method, while AWS may still ask for one, so half, as on our other AWS listings (10). A person creates the AWS account and registers an OAuth client with each provider (0). 0 + 20 + 10 + 0 = 30.); Clerk MCP server 40 (No x402, MPP or L402 (0). Per-unit prices are public ($0.02 per retained user over the included 50,000, $0.01 per SMS) (20). Hobby is free with no card (20). A person signs up and approves OAuth in a browser (0). 0 + 20 + 20 + 0 + 0 = 40.)