mcp-neo4j-aura-manager@0.4.8
VERIFIED· not startedPublisher claims: "MCP Neo4j Aura Database Instance Manager" 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
NEO4J_AURA_CLIENT_SECRETor--client-secretConfiguration, not credentials: NEO4J_AURA_CLIENT_ID, NEO4J_MCP_SERVER_ALLOW_ORIGINS, NEO4J_MCP_SERVER_ALLOWED_HOSTS, NEO4J_MCP_SERVER_HOST, NEO4J_MCP_SERVER_PATH, NEO4J_MCP_SERVER_PORT, NEO4J_MCP_SERVER_STATELESS, NEO4J_NAMESPACE, NEO4J_TRANSPORT- Where it talks to
- no vendor host named in the codeAlso neo4j.io, neo4j.com — not the publisher's domain; check what for before connecting.
- 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, and read the third-party hosts first. The code names neo4j.io, neo4j.com as well as its own vendor. The guard injects NEO4J_AURA_CLIENT_SECRET only into requests to the host you bind (and its subdomains) and refuses the rest.
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 88/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
if [ -f .env ]; thenFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.uv run --env-file .env pytest testsFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.os.environ["NEO4J_MCP_SERVER_ALLOW_ORIGINS"] = "http://env-site.com"Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.os.environ["NEO4J_MCP_SERVER_ALLOW_ORIGINS"] = "http://env.com,https://env.com"Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.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-neo4j-aura-manager@0.4.8 as of 6d ago. This is the package itself, not its dependencies.