io.github.GuardBee/db-gateway
NPM · @GUARDBEE/MCP-DB-GATEWAY
KVKK/GDPR-compliant LLM-to-database gateway: PII masking, RBAC, rate limiting, audit log
Available components
Last scanned (10 hours ago)
Scores higher than 88% of npm servers
Category Databases
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
- 30 of 94 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
- 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 2 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability74
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 349 tokens (~69/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management37
- Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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
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.
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Oct 26 +46
- Injection markers: unverified → pass ▲ security
- Known CVEs: unverified → pass ▲ security
- Tool coverage: unverified → 100 ▲ functional
- Dependency health: unverified → 0.86 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Stability: unverified → 0.30 ▲ functional
- Package version: 0.5.4 → 0.6.1 functional
- 22 Oct 26 −44
- Known CVEs: partial → unverified ▼ security
- Stability: 0.23 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Dependency health: partial → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Security disclosure: fail → pass ▲ functional
- Package version: 0.5.4 → 0.6.1 functional
- Package version: 0.5.4 → 0.6.0 functional
- Package version: 0.5.4 → 0.5.5 functional
- 21 Oct 26 +11
- Known CVEs: unverified → partial ▲ security
- Dependency health: unverified → partial ▲ functional
- Package version: 0.5.3 → 0.5.4 functional
- 20 Oct 26 −11
- Known CVEs: pass → unverified ▼ security
- Dependency health: 0.85 → unverified ▼ functional
- Package version: 0.5.1 → 0.5.3 functional
- Package version: 0.5.1 → 0.5.2 functional
- 19 Oct 26 +1
- Package version: 0.5.0 → 0.5.1 functional
- 17 Oct 26 +33
- Injection markers: unverified → pass ▲ security
- Tool coverage: unverified → 100 ▲ functional
- Stability: unverified → 0.10 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Package version: 0.3.6 → 0.5.0 functional
- 16 Oct 26 +11
- Known CVEs: unverified → pass ▲ security
- Dependency health: unverified → 0.85 ▲ functional
- Package version: 0.4.0 → 0.5.0 functional
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 25 Oct 2026 · Analysed npm/@guardbee/mcp-db-gateway@0.6.1
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 | 3386359971 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:25936674baa6be1f4aaaa8f498c1c6eda7ddedab740da22a2ade8663a0af657de913644b7e92796bffd85c6aca580d499e2dd8de654e7125c02844ba5 |
Background: How many MCP packages publish verified provenance →
Dependencies 94 packages
| Packages resolved | 94 |
|---|---|
| Stale | 30 |
| 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 →
describe_table ~40
Get the column names and gateway masking policy for a table — helps the LLM understand what data it can access.
| Name | Type | Req | Description |
|---|---|---|---|
| table | string | yes | Table name |
No output schema declared.
No examples provided.
gateway_status ~25
Show the active gateway configuration: field masking rules, table policies, and audit settings.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_tables ~26
List all available database tables. Tables marked as 'deny' in gateway policy are omitted.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
query_audit_log ~170
Query the gateway's own audit log — inspect which tools were called, on which tables, whether they were allowed or denied (and why), and which fields were redacted/written. Covers events since this server process started; count is capped by the gateway's audit.bufferSize (default 200).
| Name | Type | Req | Description |
|---|---|---|---|
| deniedOnly | boolean | – | Only return calls the gateway denied/blocked |
| limit | integer | – | Max events to return, most recent first (default 50) |
| operation | string | – | Filter by operation type |
| since | string | – | ISO 8601 timestamp — only events at or after this time |
| table | string | – | Filter by table name |
| tool | string | – | Filter by MCP tool name, e.g. 'query_table', 'update_row' |
No output schema declared.
No examples provided.
query_table ~88
Query rows from a database table with optional filters. All results pass through the KVKK/GDPR gateway — sensitive fields are automatically masked.
| Name | Type | Req | Description |
|---|---|---|---|
| filter | object | – | Key-value filter pairs, e.g. { status: 'active' } |
| limit | integer | – | Max rows to fetch before gateway limit is applied (default 50) |
| table | string | yes | Table name to query |
No output schema declared.
No examples provided.
How do I install the io.github.GuardBee/db-gateway MCP server?
io.github.GuardBee/db-gateway runs locally as an npm package, launched with npx -y @guardbee/mcp-db-gateway. 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-db-gateway
claude mcp add guardbee-db-gateway -- npx -y @guardbee/mcp-db-gateway
What is the io.github.GuardBee/db-gateway MCP server?
io.github.GuardBee/db-gateway is an MCP server listed in the public MCP registry as io.github.GuardBee/db-gateway. KVKK/GDPR-compliant LLM-to-database gateway: PII masking, RBAC, rate limiting, audit log. This page covers its npm package (@guardbee/mcp-db-gateway).
Is the io.github.GuardBee/db-gateway MCP server safe to use?
io.github.GuardBee/db-gateway scores 86 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 25 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/db-gateway MCP server expose?
io.github.GuardBee/db-gateway exposes 5 tools: query_table, list_tables, describe_table, query_audit_log, gateway_status. Their descriptions and schemas cost roughly 349 tokens of context every time the server is loaded.
Is the io.github.GuardBee/db-gateway MCP server still maintained?
io.github.GuardBee/db-gateway is still listed as active in the MCP registry. We last reached this channel on 25 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/db-gateway MCP server under?
io.github.GuardBee/db-gateway declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.