What it does
NIM Key Manager stores the API keys of your own NVIDIA Build/NIM account in encrypted form (AES-256-GCM) and tracks their status. It supports assisted rotation with an atomic swap and a lineage link to the revoked key, expiry detection, and periodic validation against NVIDIA's models endpoint every six hours by default. Keys can be dispensed on a least-recently-used basis, globally or per project, and the tool provides projects, usage statistics, roles (admin, manager, viewer), an audit log, a web dashboard and a REST API documented at /docs.
Use it when you want one place to manage your own keys across several workloads or consumers. A Model Context Protocol server lets Claude list, inspect, dispense, register, rotate and revoke keys and manage projects, under the same role checks and audit trail as the REST API.
The software is deployed as your own instance and configured through environment variables. The included Render Blueprint provisions a managed PostgreSQL database, a Docker web service and generated secrets, and you set the first administrator's credentials; any host that runs a Docker container and PostgreSQL can also be used. The Claude connector is optional and needs a GitHub OAuth App and an allow-list of identities.
Limitations and requirements
NVIDIA Build offers no public API to create or rotate keys, so new keys are generated manually and pasted in. API keys must not be shared or redistributed to other people; the tool is designed for managing your own keys on your own instance. The only outbound call is the read-only validation request to NVIDIA's models endpoint. The project is independent and not affiliated with NVIDIA. The first administrator must be set through environment variables. The Claude connector stays disabled until its OAuth credentials are set, and only identities in MCP_ALLOWED_IDENTITIES may connect. Deployment requires Docker and PostgreSQL, either through Render or another host.
Safety
Our team has not reviewed this resource. Only automated rules checked it; resources with high-risk signals are not published. These are signals, not a guarantee that installing it is safe. Try it in a sandbox project first.
- Runs code or changes an assistant's behaviour
Sources
- Official MCP Registry first seen 13 Nov 2026 · last seen 13 Nov 2026 · its page on the source
NIM Key Manager
Self-hosted NVIDIA NIM API-key manager with a Claude MCP connector; deploy your own instance.
v1.0.0As shown on registry.modelcontextprotocol.io when we last read it