Case file No.065 · pypi · stdio

Qdrant Memory

io.github.cnkang/qdrant-memory · v0.2.2

Persistent scoped Qdrant memory for agents, through four explicit stdio MCP tools.

Package ↗GitHub ↗

Security score

96/100

Strong

Normalized over 100 points of available evidence.

Score breakdown

Known advisories40/40

0 affecting current version, 0 historical

Maintenance20/20

last push 0 days ago

Source transparency15/15

public repo, license MIT

Metadata stability15/15

0 risky metadata change(s) without a version bump

Adoption6/10

1553 weekly downloads

Known advisories

source: OSV.dev

No advisories found in OSV for this package name. (Not proof of safety.)

Metadata change timeline

rug-pull detection

v0.2.1 → v0.2.2Oct 20, 2026
- version changed version bump
```
"0.2.1" → "0.2.2"
```
- packages.0.version changed package version bump
```
"0.2.1" → "0.2.2"
```
v0.1.4 → v0.2.1Oct 19, 2026
- version changed version bump
```
"0.1.4" → "0.2.1"
```
- packages.0.version changed package version bump
```
"0.1.4" → "0.2.1"
```
First snapshot (v0.1.4)Oct 17, 2026

Tool lists: not published by the registry — unknown.

FAQ

auto-generated from the data above

Is Qdrant Memory safe?

MCPWatch gives Qdrant Memory a heuristic security score of 96/100 (strong), based on 100 points of available evidence. This is an automated heuristic, not an audit.

Does Qdrant Memory have known CVEs or vulnerabilities?

No advisories were found in OSV.dev for the pypi package qdrant-memory-mcp. That is not proof of safety.

When was Qdrant Memory last updated?

The latest registry version is 0.2.2, published Oct 19, 2026. The last push to cnkang/qdrant-memory-mcp was on Oct 20, 2026. MCPWatch last checked it on Oct 20, 2026.

What license does Qdrant Memory use?

GitHub reports the license of cnkang/qdrant-memory-mcp as MIT.

Related servers

same publisher / similar score