mseep-mcp-neocoder@0.1.1
VERIFIED· not startedPublisher claims: "Neo4j-guided AI coding workflow for MCP" 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_PASSWORDQDRANT_API_KEYConfiguration, not credentials: MCP_TRANSPORT, NEO4J_DATABASE, NEO4J_MAX_CONNECTIONS, NEO4J_URL, NEO4J_USERNAME, QDRANT_HOST, QDRANT_HTTPS, QDRANT_PORT- 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 with a scoped credential, under the guard. It asks for NEO4J_PASSWORD, QDRANT_API_KEY and talks to its vendor. 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-12 and scored it 80/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
# 2. Load configuration from .env file if availableFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.subprocess.run([Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.logger.info("Loaded environment variables from .env file")Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.cleanup_parser.add_argument("--force", action="store_true", help="Force kill all instances")Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.response += "1. Verify Neo4j is running: `sudo systemctl status neo4j`\n"Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.response += "3. Try restarting Neo4j: `sudo systemctl restart neo4j`\n"Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.result = subprocess.run([Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.response += "4. Check Neo4j logs: `sudo journalctl -u neo4j`\n"Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.process = subprocess.Popen(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 mseep-mcp-neocoder@0.1.1 as of 2d ago. This is the package itself, not its dependencies.