registry / record
mcp-server-qdrant
Does mcp-server-qdrant MCP work in Claude Code and Cursor? Throne executed mcp-server-qdrant mcp in a single-use Firecracker microVM and replayed both recorded client behaviours. Compatibility verdict: inconclusive. Is mcp-server-qdrant mcp safe? Static security scan: no findings under security ruleset v1. The full per-step results, security findings, scan date, and evidence hash are below.
> throne registry mcp-server-qdrant
sealed
- scan id
- d93414bb65d14f8bb19a48248049cfcf
- target
- uvx mcp-server-qdrant
- sealed at
- 2026-06-16 22:10:33Z
- evidence hash
- sha256:76205dfb42f7491134119f3e1618dad7ec9af7507465811100887565a1592a47
RuntimeError: connect failed: McpError: Connection closed
not run, connect failed
not run, connect failed
not run, connect failed
not run, connect failed
not run, connect failed
not run, connect failed
not run, connect failed
not run, connect failed
RuntimeError: connect failed: McpError: Connection closed
not run, connect failed
not run, connect failed
not run, connect failed
not run, connect failed
not run, connect failed
not run, connect failed
not run, connect failed
not run, connect failed
- target
- uvx mcp-server-qdrant pypi
- engine
- sandboxed
- claude code
- calibration: partial recorded=9,spec=0,assumed=9
- cursor
- calibration: partial recorded=11,spec=0,assumed=7
- chatgpt desktop
- calibration: unavailable recorded=0,spec=2,assumed=16
- steps exercised
- 18 of 18
- test suite
- v1.0.0
- security ruleset
- v1.0.0
- sealed at
- 2026-06-16 22:10:33Z
- evidence hash
- sha256:76205dfb42f7491134119f3e1618dad7ec9af7507465811100887565a1592a47
- valid until
- 2026-09-14
maintainer of this server? challenge this record: hello@usethrone.dev. tell us what we got wrong and we re-run it in the open.
this page renders the stored record of a real run. nothing on it is asserted without the execution that proved it.