Qdrant MCP
PYPI · MCP-QDRANT · SCANNED SEP 21
MCP server that wraps the Qdrant vector database API as tools.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security44
- Malware scan not yet available for this package.Unverified
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs a script at install time (build_backend) that we could not recognise. It may be perfectly ordinary, but we do not read the published tarball, so we cannot say what it does. View diagnostics → Partial
- 1 of 40 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency32
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: the license (MIT License) isn't a recognized OSI-approved license. See how to fix → Fail
- Actively maintained (last published 20 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability74
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1576 tokens (~121/item across 13 items; 13 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management70
- Stability observed for 21 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the Qdrant MCP server?
Qdrant MCP runs locally as a PyPI package, launched with uvx mcp-qdrant. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · mcp-qdrant
claude mcp add avaazquezz-mcp-qdrant -- uvx mcp-qdrant
{
"mcpServers": {
"avaazquezz-mcp-qdrant": {
"command": "uvx",
"args": [
"mcp-qdrant"
]
}
}
} {
"servers": {
"avaazquezz-mcp-qdrant": {
"command": "uvx",
"args": [
"mcp-qdrant"
]
}
}
} codex mcp add avaazquezz-mcp-qdrant -- uvx mcp-qdrant
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"avaazquezz-mcp-qdrant": {
"type": "local",
"command": [
"uvx",
"mcp-qdrant"
],
"enabled": true
}
}
} openclaw mcp add avaazquezz-mcp-qdrant --command uvx --arg mcp-qdrant
mcp_servers:
avaazquezz-mcp-qdrant:
command: "uvx"
args: ["mcp-qdrant"] {
"McpServers": {
"avaazquezz-mcp-qdrant": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"mcp-qdrant"
]
}
}
} assistant mcp add avaazquezz-mcp-qdrant -t stdio -c uvx -a mcp-qdrant
{
"mcpServers": {
"avaazquezz-mcp-qdrant": {
"command": "uvx",
"args": [
"mcp-qdrant"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 −14
- Malware scan: pass → unverified ▼ security
- 15 Sept 26 +16
- Malware scan: unverified → pass ▲ security
- 14 Sept 26 −15
- Malware scan: pass → unverified ▼ security
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +15
- Malware scan: unverified → pass ▲ security
- 11 Sept 26 −14
- Malware scan: pass → unverified ▼ security
- 9 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Sept 2026 · Analysed pypi/mcp-qdrant@1.0.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | unreviewed | uv_build |
Background: Why install scripts are a supply-chain risk →
Dependencies 40 packages
| Packages resolved | 40 |
|---|---|
| No linked repository | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
qdrant_collection_create ~260
Create a collection: either a single unnamed vector (`vector_size` + `distance`), or one or more named vectors (`vectors`, each a full `VectorParams` — size, distance, and optionally its own `multivector_config` for ColBERT-style multi-vectors or `quantization_config`) — exactly one of the two. `sparse_vectors` defines sparse (keyword-style) vectors at creation time. `quantization_config` (scalar/product/binary) and `strict_mode_config` apply to the whole collection. Fails with a clear error if a collection with this name already exists. Example (simple): {"collection_name": "docs", "vector_size": 4, "distance": "Cosine"} Example (hybrid): {"collection_name": "docs", "vectors": { "dense": {"size": 4, "distance": "Cosine"} }, "sparse_vectors": {"sparse": {}}}
| Name | Type | Req | Description |
|---|---|---|---|
| collection_name | string | yes | – |
| distance | string | – | – |
| metadata | – | – | – |
| quantization_config | – | – | – |
| sparse_vectors | – | – | – |
| strict_mode_config | – | – | – |
| vector_size | – | – | – |
| vectors | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| config | – | yes | Current statistics and configuration of the collection |
| indexed_vectors_count | – | – | Approximate number of indexed vectors in the collection. Indexed vectors in large segments are faster to query, as it is stored in a specialized vector index. |
| optimizer_status | – | yes | Current statistics and configuration of the collection |
| payload_schema | object | yes | Types of stored payload |
| points_count | – | – | Approximate number of points (vectors + payloads) in collection. Each point could be accessed by unique id. |
| segments_count | integer | yes | Number of segments in collection. Each segment has independent vector as payload indexes |
| status | – | yes | Current statistics and configuration of the collection |
| update_queue | – | – | Update queue info |
| warnings | – | – | Warnings related to the collection |
No examples provided.
qdrant_collection_delete ~44
Delete a collection and all its points; a no-op if it doesn't exist. Example: {"collection_name": "docs"}
| Name | Type | Req | Description |
|---|---|---|---|
| collection_name | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| deleted | boolean | yes | – |
No examples provided.
qdrant_collection_exists ~40
Check whether a collection exists, without raising if it doesn't. Example: {"collection_name": "docs"}
| Name | Type | Req | Description |
|---|---|---|---|
| collection_name | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| exists | boolean | yes | – |
No examples provided.
qdrant_collection_info ~48
Return full config and status of one collection. Fails with a clear error if the collection doesn't exist. Example: {"collection_name": "docs"}
| Name | Type | Req | Description |
|---|---|---|---|
| collection_name | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| config | – | yes | Current statistics and configuration of the collection |
| indexed_vectors_count | – | – | Approximate number of indexed vectors in the collection. Indexed vectors in large segments are faster to query, as it is stored in a specialized vector index. |
| optimizer_status | – | yes | Current statistics and configuration of the collection |
| payload_schema | object | yes | Types of stored payload |
| points_count | – | – | Approximate number of points (vectors + payloads) in collection. Each point could be accessed by unique id. |
| segments_count | integer | yes | Number of segments in collection. Each segment has independent vector as payload indexes |
| status | – | yes | Current statistics and configuration of the collection |
| update_queue | – | – | Update queue info |
| warnings | – | – | Warnings related to the collection |
No examples provided.
qdrant_collection_list ~26
List every collection name in the configured Qdrant instance. Example: {}
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| collections | array | yes | – |
No examples provided.
qdrant_collection_update ~215
Update optimizer/HNSW/collection/vector params on an existing collection. Only the fields you pass are changed; omitted ones keep their current value. `quantization_config="disabled"` turns quantization off. `vectors_config`/`sparse_vectors_config` only **adjust** named vectors that already exist (HNSW/quantization/index tuning) — they cannot add a new one; use `qdrant_collection_vector_create` for that, or this fails with Qdrant's own "Not existing vector name" error. Fails with a clear error if the collection doesn't exist. Example: {"collection_name": "docs", "optimizers_config": {"indexing_threshold": 10000}}
| Name | Type | Req | Description |
|---|---|---|---|
| collection_name | string | yes | – |
| collection_params | – | – | – |
| hnsw_config | – | – | – |
| optimizers_config | – | – | – |
| quantization_config | – | – | – |
| sparse_vectors_config | – | – | – |
| strict_mode_config | – | – | – |
| vectors_config | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| config | – | yes | Current statistics and configuration of the collection |
| indexed_vectors_count | – | – | Approximate number of indexed vectors in the collection. Indexed vectors in large segments are faster to query, as it is stored in a specialized vector index. |
| optimizer_status | – | yes | Current statistics and configuration of the collection |
| payload_schema | object | yes | Types of stored payload |
| points_count | – | – | Approximate number of points (vectors + payloads) in collection. Each point could be accessed by unique id. |
| segments_count | integer | yes | Number of segments in collection. Each segment has independent vector as payload indexes |
| status | – | yes | Current statistics and configuration of the collection |
| update_queue | – | – | Update queue info |
| warnings | – | – | Warnings related to the collection |
No examples provided.
qdrant_health_check ~79
Confirm the configured Qdrant instance is reachable and responding. Never raises to the caller: a health check that raises on the exact condition it exists to detect defeats its own purpose. Connection failures are logged and reported in the result's ok/error fields instead, so a client renders them without a tool-call error round-trip.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| collection_count | – | – | – |
| error | – | – | – |
| ok | boolean | yes | – |
No examples provided.
qdrant_points_count ~52
Count points in a collection, optionally matching a filter. Example: {"collection_name": "docs"}
| Name | Type | Req | Description |
|---|---|---|---|
| collection_name | string | yes | – |
| count_filter | – | – | – |
| exact | boolean | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | yes | Number of points which satisfy the conditions |
No examples provided.
qdrant_points_delete ~147
Delete points by id list or by payload filter — exactly one of the two. Deleting an id that doesn't exist is not an error (Qdrant treats it as a no-op); this only fails if the collection itself is missing, or if you provide zero or both selectors. Example (by id): {"collection_name": "docs", "ids": [1, 2]} Example (by filter): {"collection_name": "docs", "points_filter": { "must": [{"key": "city", "match": {"value": "ny"}}] }}
| Name | Type | Req | Description |
|---|---|---|---|
| collection_name | string | yes | – |
| ids | – | – | – |
| points_filter | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| operation_id | – | – | Sequential number of the operation |
| status | – | yes | – |
No examples provided.
qdrant_points_get ~85
Retrieve points by id; unknown ids are simply omitted, not an error. Fails only if the collection itself doesn't exist. Example: {"collection_name": "docs", "ids": [1, 2]}
| Name | Type | Req | Description |
|---|---|---|---|
| collection_name | string | yes | – |
| ids | array | yes | – |
| with_payload | boolean | – | – |
| with_vectors | boolean | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| points | array | yes | – |
No examples provided.
qdrant_points_scroll ~108
Page through all points in a collection, optionally filtered. Pass the returned `next_page_offset` as `offset` to fetch the next page; `null` means there are no more pages. Example: {"collection_name": "docs", "limit": 50}
| Name | Type | Req | Description |
|---|---|---|---|
| collection_name | string | yes | – |
| limit | integer | – | – |
| offset | – | – | – |
| scroll_filter | – | – | – |
| with_payload | boolean | – | – |
| with_vectors | boolean | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| next_page_offset | – | yes | – |
| points | array | yes | – |
No examples provided.
qdrant_points_upsert ~108
Insert or replace points (id + vector + payload) in a collection. Fails with a clear error if the collection doesn't exist. Example: {"collection_name": "docs", "points": [ {"id": 1, "vector": [0.1, 0.2, 0.3, 0.4], "payload": {"city": "ny"}} ]}
| Name | Type | Req | Description |
|---|---|---|---|
| collection_name | string | yes | – |
| points | array | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| operation_id | – | – | Sequential number of the operation |
| status | – | yes | – |
No examples provided.
qdrant_query ~364
Vector similarity search, with optional hybrid search over multiple prefetch stages. Pass `query_vector` (a literal vector, or a point id to reuse an existing point's vector) for a plain nearest-vector query, or `fusion` + 2+ `prefetch` stages to combine multiple retrieval strategies via Reciprocal Rank Fusion (`fusion="rrf"`) or Distribution-Based Score Fusion (`fusion="dbsf"`) — exactly one of `query_vector`/`fusion` is required. `using` selects a named vector; `lookup_from` resolves `query_vector` from a point id in another collection instead of the current one. Fails with a clear error if the collection doesn't exist. Example (plain): {"collection_name": "docs", "query_vector": [0.1, 0.2, 0.3, 0.4], "limit": 5} Example (hybrid): {"collection_name": "docs", "fusion": "rrf", "prefetch": [ {"query_vector": [0.1, 0.2, 0.3, 0.4], "using": "dense", "limit": 20}, {"query_vector": [0.5, 0.5], "using": "sparse", "limit": 20} ], "limit": 5}
| Name | Type | Req | Description |
|---|---|---|---|
| collection_name | string | yes | – |
| fusion | – | – | – |
| limit | integer | – | – |
| lookup_from | – | – | – |
| prefetch | – | – | – |
| query_filter | – | – | – |
| query_vector | – | – | – |
| using | – | – | – |
| with_payload | boolean | – | – |
| with_vectors | boolean | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| points | array | yes | – |
No examples provided.
What is the Qdrant MCP server?
Qdrant MCP is listed in the public MCP registry as io.github.avaazquezz/mcp-qdrant. MCP server that wraps the Qdrant vector database API as tools. This page covers its PyPI package (mcp-qdrant).
Is the Qdrant MCP server safe to use?
Qdrant MCP scores 58 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 September 2026. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Qdrant MCP server expose?
Qdrant MCP exposes 13 tools: qdrant_health_check, qdrant_collection_create, qdrant_collection_list, qdrant_collection_info, qdrant_collection_update, and 8 more. Their descriptions and schemas cost roughly 1,576 tokens of context every time the server is loaded.
Is the Qdrant MCP server still maintained?
Qdrant MCP is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.