mcp-nacos@0.7.0
VERIFIED· not startedPublisher claims: "MCP Server for Nacos configuration management" 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: Verified 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
MCP_AUTH_TOKENNACOS_PASSWORDConfiguration, not credentials: MCP_HOST, MCP_LOG_LEVEL, MCP_PORT, MCP_STATELESS_HTTP, MCP_TRANSPORT, NACOS_BASE_URL, NACOS_INSECURE, NACOS_NAMESPACE, NACOS_READ_ONLY, NACOS_USERNAME, NACOS_VERSION- Where it talks to
- nacos.io (its own)
- What the honeypot saw
- no credential files read · no network
- What we could not test
- server startup · the tool list · tool behavior
Connect it with a scoped credential, under the guard. It asks for MCP_AUTH_TOKEN, NACOS_PASSWORD and talks to nacos.io. Give the credential to the guard, not the server: the value never enters the server's environment and only travels to the host you bind. What the tools do with a real credential was not observed.
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 92/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 0 s · 2 scenarios · 0 deviationsStatic findings
# MCPServer 原生 app 仅暴露 /mcp 与 /sse。Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.No other findings across 5,481 lines in 30 files.
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-nacos@0.7.0 as of 6d ago. This is the package itself, not its dependencies.