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/nick-pape/grackleWrote 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/nick-pape/grackle/qdrant-search)<a href="https://agentmods.dev/mcp/nick-pape/grackle/qdrant-search"><img src="https://agentmods.dev/badge/mcp/nick-pape/grackle/qdrant-search.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
qdrant-search 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 8d 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-search": {
"type": "http",
"url": "http://${QDRANT_MCP_HOST:-127.0.0.1}:7436/mcp"
}
}What else .mcp.json configures
This page is one entry in a file that holds 3. 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.
- 8d ago First seen · 6 lines scan A 2c2549259f67
qdrant-search is an MCP server published in the GitHub repository nick-pape/grackle (21 stars, last pushed 2mo 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-30.
Other mcp servers, from other repositories
rag-db-advisor
MCP server "rag-db-advisor" as configured in kenimo49/rag-db-advisor. Runs locally from the rag-db-advisor Python package.
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.
AWSBedrock
MCP server "AWSBedrock" as configured in spacehendrix/clauder. Runs locally from the awslabs.bedrock-kb-retrieval-mcp-server@latest Python package. Needs 4 environment variables to run.
Pinecone
Model Context Protocol server for Pinecone - enables AI assistants to interact with Pinecone indexes and documentation. Runs locally from the @pinecone-database/mcp npm package. Needs 1 environment variable to run.