No — it probes whether unauthenticated reads are possible; it does not keep content.

MCP Vector Store Scanner

MCP guide · Vector Store Scanner

@guardbee/mcp-vector-store-scanner probes your RAG embedding store from the outside without sending credentials. An unauthenticated vector store lets anyone read (and often write) every chunk your retrieval pipeline ever stored.

What does it do?

HTTP fingerprint → schema → data-read escalation for Weaviate, Qdrant, Chroma, and Elasticsearch/OpenSearch; Redis PING without AUTH; Postgres/pgvector AuthenticationOk without a password. Findings escalate from medium to critical.

Who is it for?

RAG / knowledge-base product teams
Security teams periodically scanning staging and prod vector stores
Developers asking Claude or Cursor about endpoint exposure

What it is not

Authorization bugs behind a working auth layer (overprivileged API keys)
Milvus gRPC (not in v1)
Unauthorized probing of endpoints you do not own

Features

Feature	Description
6 store types	Weaviate, Qdrant, Chroma, ES/OpenSearch, Redis, Postgres/pgvector
Escalation chain	info → schema → real data reads
Credential-less probes	Never sends credentials
SARIF 2.1.0	CI/CD integration
guardbee.yml	fail-on, timeout-ms

MCP tools

Tool	Description
`scan_endpoint`	Probe a single host/port for unauthenticated exposure
`list_patterns`	List supported store types and checks

Install with npm

Global install (handy for Claude Desktop / Cursor):

bash

npm install -g @guardbee/mcp-vector-store-scanner

or via npx (recommended with -y in config):

bash

npx -y @guardbee/mcp-vector-store-scanner

npm: @guardbee/mcp-vector-store-scanner

CLI: npx @guardbee/mcp-vector-store-scanner scan my-qdrant.internal --type=qdrant --fail-on=high --format=sarif > results.sarif. Only run against targets you own or are explicitly authorized to test.

Claude Desktop configuration

Config file paths:

macOS~/Library/Application Support/Claude/claude_desktop_config.json
Windows%APPDATA%\Claude\claude_desktop_config.json
Linux~/.config/Claude/claude_desktop_config.json

Merge this block, then restart Claude Desktop:

claude_desktop_config.json

{
  "mcpServers": {
    "guardbee-vector-store-scanner": {
      "command": "npx",
      "args": [
        "-y",
        "@guardbee/mcp-vector-store-scanner"
      ]
    }
  }
}

Cursor and other MCP clients

In Cursor, add the same command / args / env under Settings → MCP. stdio MCP servers use the same contract as Claude Desktop.

Example prompts in Claude

“Scan my Qdrant staging endpoint for unauthenticated access”
“Which vector store types do you support?”
“Is Weaviate /v1/objects readable without auth?”

See surface risk with Guardbee

MCP servers speed up security work in chat. Start a 14-day free trial for brand scans and BeeAI.

Start free MCP servers

Frequently asked questions

Does it steal data?

No — it probes whether unauthenticated reads are possible and reports findings; it does not keep content.

Milvus?

Not in v1 — gRPC does not fit a lightweight fingerprint probe.

API key required?

No — deliberately credential-less external probes.

MCP Vector Store Scanner: find open RAG databases