Qdrant MCP Server (deveyus/qdrant-mcp-server) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 20 tools. No publisher has claimed this listing.

C
Emerging
74/100
6 days ago

Qdrant MCP Server

Provides semantic search capabilities using Qdrant vector database with multiple embedding providers, including hybrid search, code indexing, and git history search. Adds optional time-based recency scoring to search results.

Emerging. No concerning findings. Grades remain capped until the project builds reputation through adoption. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

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

deveyus

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.
Open source with a license and README
Anyone can audit the code, the license is declared, and the publisher documents what it does.
🔐
You'll be asked for 4 credentials: COHERE_API_KEY, OPENAI_API_KEY, QDRANT_API_KEY, VOYAGE_API_KEY
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.
configCODE_BATCH_SIZENumber of chunks to embed in one batch 100
configCODE_CHUNK_OVERLAPOverlap between chunks in characters 300
configCODE_CHUNK_SIZEMaximum chunk size in characters 2500
configCODE_ENABLE_ASTEnable AST-aware chunking (tree-sitter) true
configCODE_ENABLE_HYBRID
configCODE_SEARCH_LIMIT
🔐 secretCOHERE_API_KEYCohere API key -
configEMBEDDING_BASE_URLCustom API URL Provider-specific
configEMBEDDING_DIMENSIONS
configEMBEDDING_MAX_REQUESTS_PER_MINUTERate limit Provider-specific
configEMBEDDING_MODELModel name Provider-specific
configEMBEDDING_PROVIDER"": "openai", // or "cohere", "voyage"
configEMBEDDING_RETRY_ATTEMPTSRetry count 3
configEMBEDDING_RETRY_DELAYInitial retry delay (ms) 1000
configGIT_BATCH_RETRY_ATTEMPTSRetry attempts for failed batches 3
configGIT_BATCH_SIZENumber of chunks to embed in one batch 100
configGIT_ENABLE_HYBRIDEnable hybrid search with sparse vectors true
configGIT_INCLUDE_DIFFInclude truncated diff in chunks true
configGIT_INCLUDE_FILESInclude changed file list in chunks true
configGIT_MAX_CHUNK_SIZEMaximum characters per chunk 3000
configGIT_MAX_COMMITSMaximum commits to index per run 5000
configGIT_MAX_DIFF_SIZEMaximum diff size in bytes per commit 5000
configGIT_SEARCH_LIMITDefault search result limit 10
configGIT_TIMEOUTTimeout for git commands (ms) 300000
configHTTP_PORTTRANSPORT_MODE=http =3000 node build/index.js
configHTTP_REQUEST_TIMEOUT_MSRequest timeout for HTTP transport (ms) 300000
configLOG_LEVELLogging level (fatal/error/warn/info/debug/trace/silent) info
🔐 secretOPENAI_API_KEY"": "sk-...", // provider-specific API key
configPROMPTS_CONFIG_FILENote: By default, the server looks for prompts.json in the project root directory. If the file exists, prompts are automatically loaded. You can specify a custom path using the environment variable.
🔐 secretQDRANT_API_KEYFor Qdrant Cloud or secured instances, add --env =your-key or set in env config.
configQDRANT_URL"": "http://localhost:6333"
configTRANSPORT_MODEhttp HTTP_PORT=3000 node build/index.js
🔐 secretVOYAGE_API_KEYVoyage AI API key -
// 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

20/20 tools missing one or more hints — index_codebase (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); search_code (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); reindex_changes (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +17 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 test coverage

11/20 tools referenced in tests (55%)

Write tests that reference each tool by name so every tool has at least one test.

Dependency freshness

1/18 production deps stale: bottleneck@2023-02-22 (3.5y)

Domain consistency

npm scope @mhalder doesn't match GitHub owner deveyus

Use the same org name across GitHub, npm, and your homepage so users can verify the publisher.

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 4 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/deveyus-qdrant-mcp-server-1en6w3)](https://m8ven.ai/mcp/deveyus-qdrant-mcp-server-1en6w3)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 2e258c52386aa66fe244179e31c13e9db5760b69
code hash: 666a3c658d572bb0155e6ba2528e2068bd17631dd5d3b74041d86dd86ac114b4
verified: 8/18/2026, 9:56:15 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