Home / MCP registry index / io.usefulapi/unkey
Unkey MCP by usefulapi
io.usefulapi/unkey in the official MCP registry.
Endpoint https://unkey.usefulapi.io/mcp. Source: github.com/m190/usefulapi-mcp.
The registry describes it as: Manage API keys, identities, permissions, rate-limit overrides and verification analytics.
We read its 19 tools on 2026-10-21. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
unkey_liveness unkey_get_key unkey_whoami_key unkey_get_api unkey_list_api_keys unkey_list_identities unkey_get_identity unkey_list_permissions unkey_list_roles unkey_list_ratelimit_overrides unkey_get_ratelimit_override unkey_query_verification_analytics unkey_create_api unkey_create_key unkey_update_key unkey_update_key_credits unkey_delete_key unkey_create_identity unkey_set_ratelimit_override
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-usefulapi-unkey)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.