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/mjdevaccount/AIStack-MCPWrote 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/mjdevaccount/aistack-mcp/qdrant)<a href="https://agentmods.dev/mcp/mjdevaccount/aistack-mcp/qdrant"><img src="https://agentmods.dev/badge/mcp/mjdevaccount/aistack-mcp/qdrant/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/mjdevaccount/aistack-mcp/qdrant"><img src="https://agentmods.dev/badge/mcp/mjdevaccount/aistack-mcp/qdrant.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
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 20d 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
{
"qdrant": {
"command": "npx",
"args": [
"-y",
"@rocklerson/openai-mcp-qdrant"
],
"env": {
"QDRANT_URL": "http://localhost:6333",
"OPENAI_API_KEY": "${OPENAI_API_KEY}"
}
}
}What else mcp.json configures
This page is one entry in a file that holds 5. Installing the file brings all of them; each is measured and scanned on its own page.
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.
- 20d ago First seen · 13 lines scan A bd3740699ab1
qdrant is an MCP server published in the GitHub repository mjdevaccount/AIStack-MCP (2 stars, last pushed 3d 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-09-27.
Other mcp servers, from other repositories
mad-mcp-qdrant
MCP server for retrieving context from a Qdrant vector database. Runs locally from the mad-mcp-qdrant 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.
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.
qdrant-search-mcp
MCP server "qdrant-search-mcp" as configured in webtoolbox/qdrant-search-mcp. Runs locally from the qdrant-search-mcp Python package.
mcp
Model Context Protocol server for RosalindDB - a cost-optimized, object-storage-first vector search database. Runs locally from the @rosalinddb/mcp npm package.
mcp-server-qdrant-rs
MCP server for Qdrant vector database with local embedding support. Runs locally from the mcp-server-qdrant-rs Python package.