unkey

Ingested from the official MCP Registry

FastDrop pulled this entry from the official MCP Registry as io.usefulapi/unkey and probed the endpoint. The maker did not submit it, so the outbound link is not endorsed and the description is not theirs.

If this is your server, claim the listing to edit it and take ownership. The registry index lists everything else still awaiting a probe.

Tools this endpoint exposes

Read directly from the endpoint on 29 Sept 2026. Not supplied by the maker.

• unkey_liveness

  Check that the Unkey API is reachable and the root key works. The only GET in the v2 surface. Unkey: GET /v2/liveness.

• unkey_get_key

  Fetch a key's metadata by its key id — name, owner, permissions, credits, rate limits and whether it is enabled. Read-only despite being a POST. Unkey: POST /v2/keys.getKey.

• unkey_whoami_key

  Given a plaintext API key, return which key it is and its metadata — without spending credits or recording a verification. This is the safe way to identify a key a customer sent you. Unkey: POST /v2/k

• unkey_get_api

  Fetch an API namespace by id. Read-only despite being a POST. Unkey: POST /v2/apis.getApi.

• unkey_list_api_keys

  List every key issued under one API, optionally narrowed to a single customer by externalId. Read-only despite being a POST. Unkey: POST /v2/apis.listKeys.

• unkey_list_identities

  List identities — the end users or organisations your keys belong to. Read-only despite being a POST. Unkey: POST /v2/identities.listIdentities.

• unkey_get_identity

  Fetch a single identity with its metadata and shared rate limits. Read-only despite being a POST. Unkey: POST /v2/identities.getIdentity.

• unkey_list_permissions

  List the permissions defined in the workspace. Read-only despite being a POST. Unkey: POST /v2/permissions.listPermissions.

Is this tool yours?

Claim this listing and we’ll verify ownership before handing it over.