mcp-server-qdrant

1 of its last 1 updates changed what the agent reads: 0 tool descriptions rewritten, up to 0.8.1.

PyPI package · PyPI page · recorded on 24 October 2026 on a clean machine with placeholder settings; only tools/list was sent. A changed description is not a vulnerability. Method and limits.

Release by release

0.8.0 → 0.8.1

patch release, 10 December 2025

qdrant-find: input schema changed

qdrant-store: input schema changed

Releases tried: 0.5.2 (2024-12-13), did not start; 0.6.0 (2025-03-05), did not start; 0.7.0 (2025-03-10), did not start; 0.7.1 (2025-03-11), did not start; 0.8.0 (2025-06-27); 0.8.1 (2025-12-10).

Tools in 0.8.1

The pin is the SHA-256 of the tool's name, description and input schema, as verfy.lock records it. The same pin in your lock means your agent reads this exact definition.

Tools in 0.8.1
Tool	Description	Pin
qdrant-find	Look up memories in Qdrant. Use this tool when you need to: - Find memories by their content - Access memories for further analysis - Get some personal information about the user	161eeca4600b
qdrant-store	Keep the memory for later use, when you are asked to remember something.	ac13db230bc0

Lock these tools

Pin what mcp-server-qdrant serves you today, commit the lock, and a pull request fails when a tool changes, with the text before and after. Pin the package version in your MCP config as well.

$ pip install verfy
$ verfy lock check --update   # shows each tool, then writes verfy.lock
$ git add verfy.lock

# .github/workflows/verfy.yml, after actions/checkout
- uses: anvarbekovjavohir277-dot/verfy-action@v1

Maintain this server? Run the same check on your releases and add the Locked by Verfy badge to your README.