updated 2026-10-11 04:08 UTC

Qdrant MCP Server

Repository Website by qdrant

An official Qdrant Model Context Protocol (MCP) server implementation

MCP Servers Python Listed Apache-2.0

Is Qdrant MCP Server safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 4.2 / 10
Provenance None
Signed commits 64%
Last push 37d ago
Advisories None known
Compare Qdrant MCP Server

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →
Suggest a correction

In detail: Qdrant MCP Server scores 54.5/100 (Grade C), ranked #830 of 1371 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 4.2/10; 64% of recent commits are signed; no published advisory affects its latest release (mcp-server-qdrant); last pushed 2026-09-04. Every point is earned from checkable signals — never paid placement. How scoring works →

How Qdrant MCP Server could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Already done? Suggest a correctionAdd the trust badge

Chain of custody

Scanners check what the code says. This traces who ships Qdrant MCP Server and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

  1. Source Partly signed

    github.com/qdrant/mcp-server-qdrant, Apache-2.0, last pushed 2026-09-04. 64% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.

  2. Review and release Mixed

    OpenSSF Scorecard rates the repository's practices 4.2/10 (scanned Oct 3, 2026). The checks that decide who can get a change released:

    • Code Review6
    • Branch Protection5
    • Signed Releasesn/a
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies2
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 5
    CI-Tests 2
    CII-Best-Practices 0
    Code-Review 6
    Contributors 6
    Dangerous-Workflow 10
    Dependency-Update-Tool 10
    Fuzzing 0
    License 10
    Maintained 0
    Packaging -1
    Pinned-Dependencies 2
    SAST 0
    Security-Policy 0
    Signed-Releases -1
    Token-Permissions 0
    Vulnerabilities 0

  3. Published packages Not linked

    Without a build attestation, nothing proves the published files were built from this repository.

  4. What you install today No known advisories

    Latest release checked: mcp-server-qdrant 0.8.1. No published advisory affects it (OSV, checked 2026-10-10).

Changes to this chain

No change to package provenance, package source links, Scorecard coverage or license in HVTracker's daily snapshots of Qdrant MCP Server.

Evidence behind this score

Coverage B: 3 of 5 independent evidence types found.

  • GitHub repository data
  • Package downloads
  • Supply-chain checks
  • Public actions (missing)
  • Community mentions (missing)

Verify this score yourself

Every build re-issues Qdrant MCP Server’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

Signed credential (JSON) How to verify

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.

How Qdrant MCP Server compares in MCP Servers

  1. #456 Pgedge Postgres MCP 54.6 +0.1
  2. #457 Webull OpenAPI 54.5 ±0
  3. #458 Qdrant MCP Server 54.5 this agent
  4. #459 AgentPhone 54.5 ±0
  5. #460 Greptimedb MCP Server 54.4 −0.1

Bars show each HVTrust score; the tick marks Qdrant MCP Server’s 54.5.

Where the 54.5 comes from

HVTrust dimensions vs the MCP Servers average

54.5 / 100 · 100.0% confidence

Qdrant MCP Server MCP Servers average (781 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
8.5 / 25
1.9 below avg 10.4
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.7 below avg 13.5
Transparency50% declared license · 50% OSSF Scorecard
12.1 / 17
in line with avg 12.2
Maintenance60% last-push freshness · 40% commit activity
9.5 / 20
2.7 below avg 12.2
AdoptionLog-scaled stars · package downloads
12.9 / 20
5.5 above avg 7.4

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-10-07
Rank Moved
Rank dropped 10 spots (#798 → #808)
2026-09-23
Rank Moved
Rank dropped 486 spots (#285 → #771)
2026-09-21
Rank Moved
Rank rose 473 spots (#753 → #280)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 4.2/10. Tighten the weakest checks to improve public safety evidence.
Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.
Refresh maintenance signals The repo was last pushed 37 days ago. Fresh activity helps separate stable projects from stale ones.
Compare with another agent Get email alerts for Qdrant MCP Server View MCP Servers Report missing data
50.6
Activity sub-score · out of 100
#458
In MCP Servers

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade C reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-10-11 04:08 UTC · Repo last pushed 37 days ago

Rank Trend

2026-09-29 2026-10-11

Activity & Reach

Stars
1.5k
Forks
305
Last Push
2026-09-04
37 days ago
Commits (4 wk)
0
Downloads (7d)
8,769
pypi
HN mentions (30d)
—
Open Issues
29
Rank Change
▼4
was #826

Analysis

Activity Inputs

50.6 / 100
StarsRepository reach
19.1 / 30
FreshnessLast push recency
19.9 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
11.6 / 20

Common questions about Qdrant MCP Server

Public trust evidence for Qdrant MCP Server is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.
Does Qdrant MCP Server publish package provenance?
No published build provenance is currently detected for Qdrant MCP Server. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Qdrant MCP Server have an OpenSSF Scorecard?
Qdrant MCP Server has an OpenSSF Scorecard score of 4.2/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.
Is Qdrant MCP Server actively maintained?
Slowing down. Last push was 37 days ago — keep an eye on whether activity resumes.
What license does Qdrant MCP Server use?
Qdrant MCP Server ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Qdrant MCP Server's commits signed?
64% of the last 100 commits to Qdrant MCP Server are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

AI agent surface

MCP, providers, tool surface
Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support
high confidence
Implemented
Qdrant MCP Server appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
1 detected
Public provider/service dependencies detected.
Credential signal: API keys or service config markers documented.
Tool / Plugin Surface
high confidence
1 tags
Broad capability areas detected.
  • database
Detailed evidence is not shown in the public view.
Package Provenance Drift
low confidence
Unknown
Package source metadata is missing or inconclusive
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live

Maintain Qdrant MCP Server?

For maintainers

HVTrust scores Qdrant MCP Server from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history
Rank 26
2026-10-07
Rank Moved
Rank dropped 10 spots (#798 → #808)
2026-09-23
Rank Moved
Rank dropped 486 spots (#285 → #771)
2026-09-21
Rank Moved
Rank rose 473 spots (#753 → #280)
2026-09-11
Rank Moved
Rank dropped 11 spots (#711 → #722)
2026-09-10
Rank Moved
Rank dropped 21 spots (#690 → #711)
2026-09-07
Rank Moved
Rank dropped 46 spots (#630 → #676)
2026-09-06
Rank Moved
Rank dropped 13 spots (#617 → #630)
2026-09-05
Rank Moved
Rank dropped 76 spots (#541 → #617)
2026-09-03
Rank Moved
Rank dropped 56 spots (#488 → #544)
2026-09-02
Rank Moved
Rank dropped 14 spots (#474 → #488)
2026-09-01
Rank Moved
Rank dropped 14 spots (#460 → #474)
2026-08-31
Rank Moved
Rank dropped 33 spots (#427 → #460)
2026-08-30
Rank Moved
Rank rose 12 spots (#439 → #427)
2026-08-29
Rank Moved
Rank dropped 15 spots (#424 → #439)
2026-08-26
Rank Moved
Rank dropped 42 spots (#368 → #410)
2026-08-24
Rank Moved
Rank dropped 21 spots (#345 → #366)
2026-08-22
Rank Moved
Rank rose 19 spots (#365 → #346)
2026-08-19
Rank Moved
Rank dropped 12 spots (#350 → #362)
2026-08-17
Rank Moved
Rank rose 14 spots (#361 → #347)
2026-08-13
Rank Moved
Rank dropped 18 spots (#336 → #354)
2026-08-12
Rank Moved
Rank rose 20 spots (#356 → #336)
2026-08-08
Rank Moved
Rank dropped 90 spots (#274 → #364)
2026-07-24
Rank Moved
Rank rose 13 spots (#255 → #242)
2026-07-23
Rank Moved
Rank dropped 27 spots (#228 → #255)
2026-07-15
Rank Moved
Rank dropped 19 spots (#200 → #219)
2026-07-14
Rank Moved
Rank dropped 14 spots (#186 → #200)
GitHub → Website → PyPI: mcp-server-qdrant

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 54.5 Grade C
Markdown:
[![HVTrust](https://hvtracker.net/badge/qdrant-mcp-server.svg)](https://hvtracker.net/agents/qdrant-mcp-server)
HTML:
<a href="https://hvtracker.net/agents/qdrant-mcp-server"><img src="https://hvtracker.net/badge/qdrant-mcp-server.svg" alt="HVTrust"></a>

Other agents in MCP Servers

Data sources
GitHub REST API (repo, commits, stars, forks, license) · PyPI / pypistats (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON