qdrant-full-mcp@0.4.1
VERIFIED· not startedPublisher claims: "The complete Qdrant MCP server: manage Qdrant Cloud (clusters, backups, API keys) and your vector data (collections, hybrid search, text memory) from Claude Code, Codex, Cursor or any MCP client." 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
QDRANT_API_KEYQDRANT_CLOUD_API_KEYConfiguration, not credentials: COLLECTION_NAME, EMBEDDING_MODEL, QDRANT_CLOUD_ACCOUNT_ID, QDRANT_CLOUD_API_URL, QDRANT_LOCAL_PATH, QDRANT_MCP_KEY_FILE, QDRANT_MCP_MODULES, QDRANT_MCP_TRANSPORT, QDRANT_SEARCH_LIMIT, QDRANT_URL- Where it talks to
- qdrant.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 QDRANT_API_KEY, QDRANT_CLOUD_API_KEY and talks to qdrant.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-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
out = subprocess.run([sys.executable, "-c", code], capture_output=True, text=True, check=True, env=env).stdoutFix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.out = subprocess.run([sys.executable, "-c", code], capture_output=True, text=True, check=True,Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.&& mkdir /models && chown app /modelsFix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.<summary>From a local clone</summary> ```bash git clone https://github.com/Jeevav62/qdrant-full-mcp claude mcp add qdrant -e QDRANT_CLOUD_API_KEY=your-managemenFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.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 qdrant-full-mcp@0.4.1 as of 35 min ago. This is the package itself, not its dependencies.