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/vaporif/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/vaporif/mcp-server-qdrant/mcp-server-qdrant-rs)<a href="https://agentmods.dev/mcp/vaporif/mcp-server-qdrant/mcp-server-qdrant-rs"><img src="https://agentmods.dev/badge/mcp/vaporif/mcp-server-qdrant/mcp-server-qdrant-rs/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/vaporif/mcp-server-qdrant/mcp-server-qdrant-rs"><img src="https://agentmods.dev/badge/mcp/vaporif/mcp-server-qdrant/mcp-server-qdrant-rs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
mcp-server-qdrant-rs 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 9d 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.
What it actually says
{ "mcp-server-qdrant-rs": { "command": "uvx", "args": [ "mcp-server-qdrant-rs" ] } }
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.
- 9d ago First seen · 8 lines scan A 0ac335df1858
mcp-server-qdrant-rs is an MCP server published in the GitHub repository vaporif/mcp-server-qdrant (0 stars, last pushed 3mo ago), licensed MIT. 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. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other mcp servers, from other repositories
qdrant-search-mcp
MCP server "qdrant-search-mcp" as configured in webtoolbox/qdrant-search-mcp. Runs locally from the qdrant-search-mcp Python package.
cortex
Local multi-client RAG server over the Model Context Protocol. Runs locally from the cortex-local-rag Python package. Needs 1 environment variable to run.
mad-mcp-qdrant
MCP server for retrieving context from a Qdrant vector database. Runs locally from the mad-mcp-qdrant Python package.
rag-mcp
Minimal, honest RAG-over-a-corpus MCP retrieval tool: searchknowledge(query, k) -> cited chunks. Local embeddings + embedded vector store. Auth-scoped, fail-soft, version-pinned. Runs locally from the jaimenbell-rag-mcp Python package.
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.
mcp-pgvector-search
MCP server "mcp-pgvector-search" as configured in JuanPinilla198/mcp-pgvector-search. Runs locally from the mcp-pgvector-search Python package.