mcp-registry@0.9.2
CAUTION· not startedPublisher claims: "A tool for managing and interacting with multiple MCP servers" Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Not started: dependency install failed; the server itself was not observed.- Tested
- the dependency install step · every file read, file written and host contacted by what ran
- Not tested
- server startup · the tool list · tool behavior
What this means for the label: Caution here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.
Before you give it your token
- It will ask for
- no credential variables read in the code
- Where it talks to
- no vendor host named in the code
- What the honeypot saw
- no credential files read · no network
- What we could not test
- server startup · the tool list · tool behavior
Connect it under the guard. Not started: dependency install failed; the server itself was not observed. The code names no credential variable; the guard pins the network to what the honeypot saw and logs every call.
Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; not started: dependency install failed; the server itself was not observed) on 2026-11-08 and scored it 77/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Notable findings: Access to sensitive file paths; Access to sensitive file paths; Access to sensitive file paths. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 0 s · 2 scenarios · 0 deviationsStatic findings
logger.error(f"Failed to load .env file: {e}")Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.help="Load environment variables from a .env file",Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.# Load from .env file if specifiedFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.mcp-registry add filesystem npx -y @modelcontextprotocol/server-filesystemFix: Pin versions and sources; vendor anything fetched at install time.# Get the correct npx commandFix: Pin versions and sources; vendor anything fetched at install time.full_command = subprocess.check_output([shell, "-c", f"which {command}"], text=True).strip()Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.mcp-registry add memory npx -y @modelcontextprotocol/server-memoryFix: Pin versions and sources; vendor anything fetched at install time.return "npx" # On Unix-like systems, just use npxFix: Pin versions and sources; vendor anything fetched at install time.process = subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out."npx not found. Please ensure Node.js and npm are properly installed "Fix: Pin versions and sources; vendor anything fetched at install time."npx not found. Please ensure Node.js and npm are properly installed "Fix: Pin versions and sources; vendor anything fetched at install time.logger.error("python-dotenv is not installed. Cannot load .env file.")Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.with tools from different servers namespaced by their server name. It supports twoFix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them."""Get the correct npx command for the current platform."""Fix: Pin versions and sources; vendor anything fetched at install time.subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.assert config["mcpServers"]["remote-server"]["url"] == "http://localhost:8000/sse"Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.assert config["mcpServers"]["remote-server"]["type"] == "sse"Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.result = subprocess.run([editor, str(config_path)], check=True)Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.subprocess.run(['which', potential_editor],Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.Cost to the agent
Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.
Known vulnerabilities
No advisories in OSV for mcp-registry@0.9.2 as of 6d ago. This is the package itself, not its dependencies.
What would make this Verified
3 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Unclaimed publisher≈ +8 on the totalClaim cccntu: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
- Access to sensitive file paths≈ +4 on the totalStop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
- Cross-server tool reference≈ +4 on the totalNamespace tool names and keep tool descriptions literal; no instructions to the agent inside them.
- npx invocation of non-well-known package≈ +2 on the totalPin versions and sources; vendor anything fetched at install time.
- Python subprocess execution detected≈ +2 on the totalBuild commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.
- MCP server using network transport (SSE/HTTP)≈ +2 on the totalNamespace tool names and keep tool descriptions literal; no instructions to the agent inside them.