C
Limited view
67/100
2 months ago

Qdrant RAG MCP Server

Enables context-aware semantic search across codebases using Qdrant vector database with intelligent GitHub issue resolution, Projects V2 management, and progressive context retrieval for 95%+ token reduction in AI-assisted development.

Limited view. Automated analysis covers part of this stack. Findings reflect what we verified. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

Limited view: static analysis for Python is partially covered.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

ancoleman

Source: Glama

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

Install from

M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.

// key findings
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
🔐
You'll be asked for 1 credential: GITHUB_TOKEN
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
configSENTENCE_TRANSFORMERS_HOME
configQDRANT_CODE_EMBEDDING_MODEL
configQDRANT_CONFIG_EMBEDDING_MODEL
configQDRANT_DOC_EMBEDDING_MODEL
configQDRANT_GENERAL_EMBEDDING_MODEL
configQDRANT_CODE_EMBEDDING_FALLBACK
configQDRANT_CONFIG_EMBEDDING_FALLBACK
configQDRANT_DOC_EMBEDDING_FALLBACK
configCONFIG_PATH
🔐 secretGITHUB_TOKEN
configHF_HOME
configHF_HUB_CACHE
configMCP_CLIENT_CWD"Get current directory with pwd, export to that value, then run health check"
configEMBEDDING_MODEL
configQDRANT_HOST
configQDRANT_PORT
configPYTORCH_ENABLE_MPS_FALLBACK
configPYTORCH_MPS_HIGH_WATERMARK_RATIO
configPYTORCH_MPS_LOW_WATERMARK_RATIO
configQDRANT_SPECIALIZED_EMBEDDINGS_ENABLED
configQDRANT_LOG_DIRexport =/custom/path # Custom log directory
configQDRANT_DOC_INSTRUCTION_PREFIX
configQDRANT_DISABLE_APPLE_SILICON_LIMITS
configQDRANT_MAX_MODELS_IN_MEMORY
configQDRANT_MEMORY_LIMIT_GB
configQDRANT_MODEL_CACHE_DIR
configQDRANT_CODE_QUERY_PREFIX
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

56/56 tools missing one or more hints — get_context (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_file_chunks (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); detect_changes (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +53 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Tool inputs are validated

49/56 tool handlers declare input schemas (88%)

Declare an inputSchema with zod/joi/yup on every tool definition.

Tool handlers catch errors

Only 22/56 tool handlers wrap calls in try/catch (39%)

Wrap each tool handler body in try/catch and return a structured error response.

License file

No license file

Add a LICENSE file (MIT, Apache-2.0, etc.).

Tests exist

No test files found

Add tests that exercise each declared tool.

Shell command execution

3 child_process calls — runs shell commands

Prefer library functions over shell-outs. If you must shell out, ensure all inputs are properly escaped.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 7 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Score](https://m8ven.ai/badge/mcp/ancoleman-qdrant-rag-mcp-ihaokj)](https://m8ven.ai/mcp/ancoleman-qdrant-rag-mcp-ihaokj)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 8f07ecdd2a92dab2455fa678fefc90d0ca6e2d61
code hash: a94cf51951adee7c6269f717e15281af6d9e10e4a6e158e540b3437531f8dc08
verified: 6/18/2026, 11:32:24 AM
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client