Provenancewhere it came from, and what was verified
Published to the official MCP registry by github.com/bysergimm, which proved it owns this namespace.
🛡 Permissions & trustwhat this server can touch before you run it
No permission details are published for this server yet. Check the source before you run it.
About
Self-hosted NVIDIA NIM API-key manager with a Claude MCP connector; deploy your own instance.
Packages & transports
No packages or remotes listed.
Computed from the server's own data, not a hidden formula. This measures how much you can depend on it, not how popular it is. Stars are shown separately, on purpose. How it's scored →
Raise this grade
up to +20 on qualityOwn this server? Here's exactly what to change, biggest wins first. Every number below is a fixed point value, so you can see what each edit is worth before you make it.
Publish a package (npm, PyPI, and so on) or expose a remote endpoint so people can actually run it.
With no reviews this sits at a neutral 11. Reviews reporting it works push it toward the full 20.
Already earned (4) ▾Already earned (4) ▴
These are structural checks, so the fixes are exact. See the full formula →
Add a badge to your README
[](https://socketcat.com/servers/io.github.BySergiMM/nim-key-manager)Shows your live quality grade and links back here. It updates itself as the grade changes.
Reviews
Sign in to leave a reviewNo reviews yet. Be the first to say whether it worked.
{
"mcpServers": {
"nim_key_manager": {
"command": "npx",
"args": [
"-y",
"nim-key-manager"
]
}
}
}▶ Try itrun it locally
This is a local server, so it runs on your machine, not ours. Paste this to open it in the official MCP Inspector and poke at its tools:
npx @modelcontextprotocol/inspector npx -y nim-key-manager