Is Qdrant MCP Server safe to use?

Qdrant MCP Server has an HVTrust score of 58.5/100 (Grade C), ranked #356 of 1283 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Qdrant MCP Server?

Qdrant MCP Server scores 58.5/100 on HVTracker's evidence-weighted HVTrust scale. It has 1.5k GitHub stars and is categorized under MCP Servers.

Qdrant MCP Server

qdrant/mcp-server-qdrant

An official Qdrant Model Context Protocol (MCP) server implementation

MCP Servers Python Grade C Listed Apache-2.0

58.5/100

Rank #356 of 1283

Compare Qdrant MCP Server

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Promising trust profile, but some evidence still deserves review.

Open compare tool Suggest correction

Listing state

Listed

Evidence coverage

Grade B · 3/5 signals

Last push

2026-08-11 · 0d ago

Recent change

Rank

Is Qdrant MCP Server safe? Qdrant MCP Server scores 58.5/100 (Grade C), ranked #356 of 1283 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; last pushed 2026-08-11. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in MCP Servers

#118 Codex Control Plane MCP — 58.9 (C) → #119 AntV Chart MCP Server — 58.6 (C) → #121 NetLogo MCP — 58.3 (C) → #122 Monarch MCP Server — 58.1 (C) →

Quick Trust Read

What Would Improve It

Publish package provenance or release attestations for stronger supply-chain evidence.

Recent Changes

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)

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.

Compare with another agent Get email alerts for Qdrant MCP Server View MCP Servers Report missing data

59.3

Activity sub-score · out of 100

#120

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 →

Activity & Reach

Stars

1.5k

Forks

293

Last Push

2026-08-11

today

Commits (4 wk)

Downloads (7d)

19,250

pypi

HN mentions (30d)

—

Open Issues

Rank Change

▲21

was #377

Analysis

HVTrust Dimensions vs MCP Servers

58.5 / 100 · 100.0% confidence

Qdrant MCP Server MCP Servers average (761 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

8.4 / 25

3.4 above avg 5.0

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

2.5 below avg 13.3

Transparency50% declared license · 50% OSSF Scorecard

12.1 / 17

3.3 above avg 8.8

Maintenance60% last-push freshness · 40% commit activity

13.2 / 20

0.7 above avg 12.5

AdoptionLog-scaled stars · package downloads

13.3 / 20

7.5 above avg 5.8

Activity Inputs

59.3 / 100

StarsRepository reach

19.0 / 30

FreshnessLast push recency

25.0 / 25

ActivityRecent commits

3.8 / 25

CommunityFork signal

11.5 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

4.2 / 10

OpenSSF Scorecard · scanned Aug 10, 2026

Signed Commits

64%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 5

CI-Tests 3

CII-Best-Practices 0

Code-Review 5

Contributors 6

Dangerous-Workflow 10

Dependency-Update-Tool 10

Fuzzing 0

License 10

Maintained 1

Packaging -1

Pinned-Dependencies 2

SAST 0

Security-Policy 0

Signed-Releases -1

Token-Permissions 0

Vulnerabilities 0

Is Qdrant MCP Server safe?

Qdrant MCP Server has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.

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?

Actively maintained. The repository was pushed to within the last 1 day(s).

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?

63% 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.

Qdrant

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

How this surface has changed

Detected changes to Qdrant MCP Server's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.

2026-07-13

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-07-13

Provider Added

Runtime surface grew — new detected provider dependency: Qdrant

2026-07-13

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-07-13

Activity Resumed

Activity resumed

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

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)

2026-07-13

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-07-13

Provider Added

Runtime surface grew — new detected provider dependency: Qdrant

2026-07-13

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-07-13

Activity Resumed

Activity resumed

2026-07-13

Grade Changed

Trust grade D → C

2026-07-13

Rank Moved

Rank rose 162 spots (#348 → #186)

2026-07-13

HVTrust Changed

HVTrust up 56.7pts (3.3 → 60.0)

2026-07-13

Activity Score Changed

Activity score up 55pts (0 → 55)

2026-07-12

Newly Listed

First tracked at rank #348

GitHub → PyPI: mcp-server-qdrant

Embed Badge Badge guide for maintainers →

For maintainers

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.3 · Raw JSON