Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/bartest5/qdrant_mcp-server-qdrantWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/bartest5/qdrant_mcp-server-qdrant/mcp-server-qdrant)<a href="https://agentmods.dev/mcp/bartest5/qdrant_mcp-server-qdrant/mcp-server-qdrant"><img src="https://agentmods.dev/badge/mcp/bartest5/qdrant_mcp-server-qdrant/mcp-server-qdrant.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
mcp-server-qdrant scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 6d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
This is a copy
100% identical to mcp-server-qdrant — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
{ "mcp-server-qdrant": { "command": "uvx", "args": [ "mcp-server-qdrant" ] } }
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 6d ago First seen · 8 lines scan A 70cb98d888da
mcp-server-qdrant is an MCP server published in the GitHub repository bartest5/qdrant_mcp-server-qdrant (0 stars, last pushed 18d ago), licensed Apache-2.0. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. It is 100% identical to mcp-server-qdrant, differing in 0 lines, and is treated as a copy.
Other mcp servers, from other repositories
haiku-rag
Local-first agentic RAG with citations - hybrid search, reranking and multimodal retrieval over your own documents, no database server required. Runs locally from the haiku-rag Python package.
chromadb-remote-mcp
MCP server "chromadb-remote-mcp" as configured in meloncafe/chromadb-remote-mcp. Runs in Docker (devsaurus/chromadb-remote-mcp:latest). Needs 2 environment variables to run.
mcp-neo4j-knowledge-graph
Neo4j-based knowledge graph MCP server with temporal versioning and semantic search. Runs locally from the @henrychong-ai/mcp-neo4j-knowledge-graph npm package.
toolbelt
A collaborative substrate over your data: vector, knowledge graph, SQL, geospatial, streaming. Remote server at mcp.toolbelt.ai.
local-knowledge-rag
MCP server "local-knowledge-rag" as configured in patakuti/local-knowledge-rag-mcp. Runs /path/to/local-knowledge-rag-mcp/dist/mcp-server.js with node. Needs 3 environment variables to run.
datris
MCP server for AI-driven data pipeline operations — ingest, validate, transform, analyze, and query data. Tools covering ETL, AI data quality, vector search, PostgreSQL, MongoDB, Snowflake, Databricks, Kafka, S3/MinIO, HashiCorp Vault, Qdrant, Weaviate, Milvus, Chroma, pgvector. Runs locally from the datris-mcp-server…