Qdrant (official)

100/100
Last tested 2026-11-10 (Fresh: tested within 30 days) Working (tool call tested 2026-11-10) No key needed for the tools we called

No advisories in range for tested 0.8.1 (checked 2026-11-09)

Security review: not tested

Score = points from our five tests (install, handshake, maintenance, docs, license). Not a quality or security rating. Methodology

  • Install20/20
  • Handshake30/30
  • Maintenance25/25
  • Docs15/15
  • License10/10

Tool-call test (2026-11-10, direct MCP stdio client, no LLM): pass. 2 of 2 real function calls passed in the 2026-11-10 stale retest. Evidence: local test run, Nov 10, 2026.

Transport (tested 2026-10-22): stdio

Tested version: 0.8.1 · tested 2026-10-22

Token cost (estimate): approx. 226 tokens, cl100k estimate (2 tools, measured 2026-11-11, version 0.8.1). This is an estimate from our testing of the tool names, descriptions and input schemas, counted with cl100k_base.

Permissions: 1 read, 0 write (state-changing), 1 unclassified · Auth: none · Rate limit: unknown · Pricing unit: unknown

Auth: none. Rate limit: unknown. Pricing unit: unknown.

  • qdrant-find — read
  • qdrant-store — unclassified

handshake and tools listed without a recorded key or OAuth

Score 100/100 · Tools 2 · Token cost approx. 226 tokens · Compare · Last tested 2026-11-10 · Version tested 0.8.1 · Package mcp-server-qdrant · Repo qdrant/mcp-server-qdrant

Summary: Qdrant (official) completed an MCP handshake without credentials and exposed 2 tools.

Evidence summary

Handshake
pass
Tools listed
2
Context cost
approx. 226 tokens, cl100k estimate (2 tools, measured 2026-11-11, version 0.8.1; an estimate) ranking · add up your servers' context cost
API key
No key needed for the tools we called
Tested
2026-11-10

Test results

TestResultPointsEvidence
installpass20uv pip install mcp-server-qdrant (Python venv, Linux) succeeded in 0s.
handshakepass30MCP initialize + tools/list over stdio succeeded with no credentials; 2 tools listed in 3.3s.
maintenancepass25Repo pushed 0 days before test; 1,567 GitHub stars.
docspass15README over 3,000 chars; install instructions present; mcpServers config example present. Check of the package's own README (PyPI long_description (package README)).
licensepass10Apache-2.0 (OSI-approved).

Local-model readiness

Token cost (estimate): approx. 226 tokens, cl100k estimate for 2 tools · about 3% of an 8k context. This is an estimate from our testing (counted with cl100k_base).

Small-model friendly (schema heuristic, not a model result): high.

Not tested

Small-model task runs: Not yet tested.

Functional tasks (2/2 passed, tested 2026-10-28)

TaskToolResultEvidence
store entityqdrant-storepass[{"type":"text","text":"Remembered: TestedMCPProbe1793193457246 likes-qnnl0i in collection testedmcp"}]
retrieve entityqdrant-findpass[{"type":"text","text":"[\n \"Results for the query 'TestedMCPProbe1793193457246'\",\n \"<entry><content>TestedMCPProbe1793193457246 likes-qnnl0i</content><me

What we tested and what we didn't

Tested on 2026-11-10

  • Install from the registry
  • We connected with no credentials and asked for its tool list: it listed 2 tools (Method details: MCP initialize then tools/list)
  • Maintenance signals (last push, archived/deprecated status)
  • Docs (README length, install and config example)
  • License (OSI-approved or not)
  • Functional tasks: 2/2 passed
  • Token cost (estimate)

Not tested

  • Security: not audited (no code review, no permission or data-flow analysis)
  • Behaviour with real credentials or a real account
  • Performance, rate limits or load
  • Correctness of results beyond the listed tasks

Methodology: how we test. A high score means it installs and responds, not that giving it access to your data carries no risk.

Known security issues

Checked on 2026-11-09 for version 0.8.1 against OSV, GitHub advisories, GitHub repository advisories. Scope: the package itself; dependencies not scanned.

No published advisories found in OSV and GitHub advisories for mcp-server-qdrant 0.8.1 as of 2026-11-09. This is not a security audit.

Monthly roundup: MCP security issues, October 2026.

Tool list changes

Unchanged since the previous snapshot (latest 2026-11-11).

Snapshot hash (fingerprint of the tool list)

4e5cf43dfaa0: SHA-256 of the canonical tool names, descriptions and input schemas. If it changes, the tool list changed.

Feeds: RSS · JSON.

Raw test record (JSON)
{
  "name": "mcp-server-qdrant",
  "version": "0.8.1",
  "registry": "pypi",
  "status": "working",
  "tested": "2026-11-10",
  "tools_count": 2,
  "deprecated": false,
  "archived": false,
  "tests": {
    "install": [
      "pass",
      20,
      "`uv pip install mcp-server-qdrant` (Python venv, Linux) succeeded in 0s."
    ],
    "handshake": [
      "pass",
      30,
      "MCP `initialize` + `tools/list` over stdio succeeded with no credentials; 2 tools listed in 3.3s."
    ],
    "maintenance": [
      "pass",
      25,
      "Repo pushed 0 days before test; 1,567 GitHub stars."
    ],
    "docs": [
      "pass",
      15,
      "README over 3,000 chars; install instructions present; `mcpServers` config example present. Check of the package's own README (PyPI long_description (package README))."
    ],
    "license": [
      "pass",
      10,
      "Apache-2.0 (OSI-approved)."
    ]
  }
}

Install

uvx mcp-server-qdrant

Pin the version we tested

uvx mcp-server-qdrant==0.8.1

pip install mcp-server-qdrant==0.8.1

tested 2026-11-10. Newer versions may differ and were not tested by us.

{
  "mcpServers": {
    "qdrant": {
      "command": "uvx",
      "args": [
        "mcp-server-qdrant==0.8.1"
      ]
    }
  }
}

Tools listed

qdrant-find, qdrant-store

Tool history: captured Nov 11, 2026. All tool history.

Quick config

{
  "mcpServers": {
    "qdrant": {
      "command": "uvx",
      "args": [
        "mcp-server-qdrant"
      ]
    }
  }
}

Add to config Opens the config generator with this server selected.

Setup

  1. Install. Run uv pip install mcp-server-qdrant (Python venv). This is the exact command we ran on 2026-11-10.
  2. Configure. Add the mcpServers entry below to your MCP client config.
  3. Verify. Restart the client and check that tools/list returns tools (2 in our test).
{
  "mcpServers": {
    "qdrant": {
      "command": "uvx",
      "args": [
        "mcp-server-qdrant"
      ]
    }
  }
}

Test history

Follow this server (RSS) · Monthly changelog

Related: Best memory MCP servers

FAQ

Is Qdrant deprecated?

No. mcp-server-qdrant was not deprecated or archived when we last tested it on 2026-11-10.

What replaces Qdrant?

Nothing; Qdrant (official) is not deprecated as of 2026-11-10.

Does Qdrant need an API key?

No. It completed an MCP handshake with no credentials and listed 2 tools.

Embed the badge

TestedMCP: 100/100, tested 2026-11-10

Every tested server gets a free embeddable badge. It shows the current score and test date and expires after 90 days. Testing is free; payment never changes a score.

Claim this listing · Report an issue