HeyIdentity
Server Details
Create a fake Entra ID or OIDC tenant for testing in one call. No account needed.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 20 tools
Most tools map cleanly to a resource+action (client, user, custom claim, settings, keys, tenant). Minor overlap exists between edit_settings and set_standard_claims, and between get_tenant and get_configuration, but descriptions make the boundaries workable.
Nearly all tools follow a verb_noun snake_case pattern (add_client, edit_user, remove_custom_claim, rotate_signing_key). There are minor verb inconsistencies where 'add' and 'create' are both used for creation, but each verb maps predictably to a resource class.
At 20 tools the surface is on the heavier side, but the count follows directly from three entities (clients, users, custom claims) each needing add/edit/remove, plus tenant/configuration/settings/keys operations. Each tool covers a distinct operation rather than padding.
Full lifecycle coverage exists for clients, users, and custom claims, plus tenant creation, configuration inspection/validation, signing key rotation, and claim codes. The notable gap is removal of configurations or tenants (and no way to rename a configuration), which leaves cleanup as a dead end.
Available Tools
20 toolsadd_clientCInspect
Adds a client. client: { client_id, client_secret?, allow_all_return_urls?, redirect_uris?, allowed_scopes?, exposed_scopes?, access_token_audience? }.
Inputs: client (required), configuration_id (required).
add_custom_claimBInspect
Adds a custom claim emitted for every user. claim: { name, value, target?: both|id_token|access_token }.
Inputs: claim (required), configuration_id (required).
add_userBInspect
Adds a fictional test user. user: { key, display_name?, sub?, icon?, access_token_sub?, claims?: { name: string|number|boolean|string[] }, claim_targets?: { name: both|id_token|access_token }, sign_in_outcome?: normal|access_denied|temporarily_unavailable|interaction_required|refresh_revoked (Pro) }.
Inputs: user (required), configuration_id (required).
create_configurationAInspect
Creates another configuration in the tenant from the starter content (a demo user and a demo client), with a name unique in the tenant and a profile. Prefer a separate client per environment in one configuration; create a configuration for a different profile or a separate set of users. A retry with the same name answers configuration_exists with the existing configuration instead of creating a second one.
Inputs: name (required), profile.
create_tenantAInspect
Creates an unverified HeyIdentity test tenant with a working demo client and test user, accepting the current Terms of Use on behalf of the operator running the agent. Returns endpoints, an agent token, the fixed claim page URL, the expiry time and next_steps.
Inputs: accepted_terms_version (required), profile, display_name, idempotency_key.
edit_clientBInspect
Edits a client; fields left out keep their value. changes: { client_secret?, allow_all_return_urls?, redirect_uris?, allowed_scopes?, exposed_scopes?, access_token_audience? }.
Inputs: changes (required), client_id (required), configuration_id (required).
edit_custom_claimBInspect
Edits a custom claim's value or target; fields left out keep their value. changes: { value?, target? }.
Inputs: name (required), changes (required), configuration_id (required).
edit_settingsBInspect
Edits the settings; fields left out keep their value. settings: { profile?, b2c_policy_claim? (tfp or acr), validate_client_secrets?, token_lifetime_minutes?, token_shape?: { scope_claim_name?, scope_claim_format?, roles_claim_name?, roles_nested_key?, access_token_audience? } }.
Inputs: settings (required), configuration_id (required).
edit_userBInspect
Edits a user; fields left out keep their value, and claims, when given, replace the user's claims.
Inputs: key (required), changes (required), configuration_id (required).
get_catalogARead-onlyInspect
Describes the profiles (claims, URL shapes, protocol behaviors), token shape options, standard claims, limits, the current terms version and the rules agents must follow. Read it before configuring a tenant.
Inputs: no named parameters.
get_configurationBRead-onlyInspect
Returns one configuration of the tenant as items: clients, users, custom and standard claims, settings and endpoints.
Inputs: configuration_id (required).
get_tenantBRead-onlyInspect
Returns the tenant, its configurations and their endpoints, its limits and status.
Inputs: no named parameters.
list_signing_keysARead-onlyInspect
Lists a configuration's published key IDs, status, source and expiry. Available on every plan; returns no key material.
Inputs: configuration_id (required).
remove_clientCDestructiveInspect
Removes a client.
Inputs: client_id (required), configuration_id (required).
remove_custom_claimCDestructiveInspect
Removes a custom claim.
Inputs: name (required), configuration_id (required).
remove_userBDestructiveInspect
Removes a user (at least one must remain).
Inputs: key (required), configuration_id (required).
request_claim_codeAInspect
Issues a single-use claim code for an unclaimed tenant. It works for 15 minutes and replaces any earlier code. Show the code and claim_page_url to the user; never store the code.
Inputs: no named parameters.
rotate_signing_keyADestructiveInspect
Generates a new RSA signing key for this configuration. overlap=true keeps the previous key published for the configured window; false removes every earlier key immediately. Needs Pro or Enterprise (or Vetted assurance); rate limited per configuration. Returns the current kid and published keys.
Inputs: overlap (required), configuration_id (required).
set_standard_claimsCInspect
Sets which of the profile's generated standard claims are enabled (see get_configuration's standard_claims.available).
Inputs: enabled (required), configuration_id (required).
validate_configurationARead-onlyInspect
Reports problems (e.g. a client without a redirect URI) and warnings (e.g. a scope no client requests) without changing anything.
Inputs: configuration_id (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Mock REST APIs, fake OAuth2/OIDC provider, uptime monitors + heartbeats, live badge/QR images.
Give your agent its own cloud: Postgres, Redis, a sandbox or any Docker image, in one MCP call.
Hosted MCP endpoint with realistic fake data for prototyping agents. 12 tools, no setup.
Claim a working subdomain in one call — A, CNAME and TXT records. No domain to buy, no account.
Related MCP Servers
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients that can only send a fixed Authorization header to reach OAuth 2.1-protected MCP servers, by running a loopback proxy that handles RFC 9728 discovery, PKCE login, and silent token refresh so no pasted JWT is ever needed. The client keeps a stable local token while the rotating OAuth credentials stay in the gateway's state file.12 npmMIT
- FlicenseNot gradedqualityFmaintenanceEnables testing an MCP v2 streamable HTTP server protected by Supabase OAuth 2.1, including Dynamic Client Registration, consent flow, and token-based identity verification for Claude clients.-
- AlicenseNot gradedqualityBmaintenanceAdds a remote, OAuth 2.1-authenticated MCP endpoint to an app so Claude and ChatGPT connectors can register themselves, send a person through a consent screen, and call the app's tools as that person. It supplies discovery metadata, PKCE authorization with rotating refresh tokens, a bearer gate, and per-call auditing.226 npm1MIT
- AlicenseNot gradedqualityDmaintenanceEnables enterprise-managed authorization for MCP on Azure App Service, with deployable Entra OAuth and a local EMA ID-JAG lab exposing whoami and authorization_model tools.1MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.