qmcp-qdrant@0.3.3
VERIFIED· not startedPublisher claims: "Qdrant MCP Server for OpenCode - semantic search for code and documentation" 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
- 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-15 and scored it 83/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
- **Never** store PyPI tokens in AGENTS.md, .env, or any git-tracked files —Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.- Environment files (`.env`, `.env.local`)Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.1. Add environment variable to `.env.example`Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.ПotentialныеFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.Hidden files (``.env``, ``.DS_Store``, ...) and files withFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.1. Verify Qdrant is running: `curl http://192.168.218.190:6333`Fix: Replace encoded or assembled strings with plain literals and remove undeclared network calls."""HTTP/SSE servers must never kill themselves on parent death."""Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.env_file=".env",Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose."QDRANT_URL": "http://192.168.218.190:6333",Fix: Replace encoded or assembled strings with plain literals and remove undeclared network calls.kill the server.Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.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 qmcp-qdrant@0.3.3 as of 49 min ago. This is the package itself, not its dependencies.