io.github.GuardBee/vector-store-scanner
NPM · @GUARDBEE/MCP-VECTOR-STORE-SCANNER
Probes vector-database endpoints for unauthenticated exposure of embeddings/RAG data
Available components
Last scanned (20 hours ago)
Scores higher than 64% of npm servers
Category Security
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to GuardBee/guardbee-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 4 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability74
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 256 tokens (~128/item across 2 items; 2 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 14 Oct 26 +31
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- First check of Schema quality: fail functional
- First check of Destructive annotations: pass functional
- First check of Schema quality: pass functional
- First check of Schema quality: good functional
- First check of Tool coverage: 100 functional
- 13 Oct 26 49
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 16 Oct 2026 · Analysed npm/@guardbee/mcp-vector-store-scanner@0.1.2
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | GuardBee/guardbee-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/GuardBee/guardbee-mcp/.github/workflows/release.yml@refs/heads/main |
| Rekor log index | 3209956094 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:d5e6a7c7c2be39ef02263d889dd8e436404ce3544dea88a81aad1d94b97a96abf10400d35221f9613dbf8748ba9fabab2206f89bce789d323c0833367 |
Background: How many MCP packages publish verified provenance →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
list_patterns ~30
List the vector-store types this scanner can fingerprint, and what unauthenticated-access checks it runs for each
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
scan_endpoint ~226
Probe a vector-database (or vector-index-capable) endpoint for unauthenticated exposure — Weaviate, Qdrant, Chroma, Elasticsearch/OpenSearch (HTTP fingerprinting, escalating from instance info → collection/schema listing → actual stored data), Redis (RESP PING without AUTH), and Postgres/pgvector (wire-protocol SSLRequest + StartupMessage handshake, no real credentials sent). Read-only — never writes or authenticates with real credentials.
| Name | Type | Req | Description |
|---|---|---|---|
| host | string | yes | Hostname or IP of the endpoint to probe |
| port | number | – | Port to probe (defaults to the store type's conventional port, e.g. 6333 for Qdrant) |
| timeoutMs | number | – | Per-request timeout in milliseconds (default: 4000) |
| tls | boolean | – | Use https:// for HTTP-based probes (Weaviate/Qdrant/Chroma/Elasticsearch). Default: false |
| type | string | – | Store type to probe for. 'auto' (default) fingerprints the endpoint by trying each known type in turn. |
No output schema declared.
No examples provided.
How do I install the io.github.GuardBee/vector-store-scanner MCP server?
io.github.GuardBee/vector-store-scanner runs locally as an npm package, launched with npx -y @guardbee/mcp-vector-store-scanner. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @guardbee/mcp-vector-store-scanner
claude mcp add guardbee-vector-store-scanner -- npx -y @guardbee/mcp-vector-store-scanner
What is the io.github.GuardBee/vector-store-scanner MCP server?
io.github.GuardBee/vector-store-scanner is an MCP server listed in the public MCP registry as io.github.GuardBee/vector-store-scanner. Probes vector-database endpoints for unauthenticated exposure of embeddings/RAG data. This page covers its npm package (@guardbee/mcp-vector-store-scanner).
Is the io.github.GuardBee/vector-store-scanner MCP server safe to use?
io.github.GuardBee/vector-store-scanner scores 80 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 16 October 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.GuardBee/vector-store-scanner MCP server expose?
io.github.GuardBee/vector-store-scanner exposes 2 tools: scan_endpoint, list_patterns. Their descriptions and schemas cost roughly 256 tokens of context every time the server is loaded.
Is the io.github.GuardBee/vector-store-scanner MCP server still maintained?
io.github.GuardBee/vector-store-scanner is still listed as active in the MCP registry. We last reached this channel on 16 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.GuardBee/vector-store-scanner MCP server under?
io.github.GuardBee/vector-store-scanner declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.