Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.bch1212/queryshield

PYPI · QUERYSHIELD-MCP · SCANNED SEP 20

Secure SQL proxy for AI agents — NL→SQL, AST safety, per-agent RLS, audit log.

Available components

−1 this week 80 Trust /100
Trust breakdown (7 categories)

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 Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
  • 1 of 23 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability74
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 192 tokens (~64/item across 3 items; 3 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management80
  • Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage84
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 43% of tool parameters carry a description.Partial
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Install

How do I install the io.github.bch1212/queryshield MCP server?

io.github.bch1212/queryshield runs locally as a PyPI package, launched with uvx queryshield-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · queryshield-mcp

# add to Claude Code
claude mcp add bch1212-queryshield -- uvx queryshield-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "bch1212-queryshield": {
      "command": "uvx",
      "args": [
        "queryshield-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "bch1212-queryshield": {
      "command": "uvx",
      "args": [
        "queryshield-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add bch1212-queryshield -- uvx queryshield-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "bch1212-queryshield": {
      "type": "local",
      "command": [
        "uvx",
        "queryshield-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add bch1212-queryshield --command uvx --arg queryshield-mcp
# ~/.hermes/config.yaml
mcp_servers:
  bch1212-queryshield:
    command: "uvx"
    args: ["queryshield-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "bch1212-queryshield": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "queryshield-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add bch1212-queryshield -t stdio -c uvx -a queryshield-mcp
// mcp.json
{
  "mcpServers": {
    "bch1212-queryshield": {
      "command": "uvx",
      "args": [
        "queryshield-mcp"
      ]
    }
  }
}
Changelog

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.

  • 19 Sept 26 +12
    • Malware scan: unverified → pass security
    • Stability: pass → 0.77 functional
  • 18 Sept 26 0
    • Stability: 0.97 → pass security
  • 17 Sept 26 −14
    • Malware scan: pass → unverified security
  • 15 Sept 26 +16
    • Malware scan: unverified → pass security
  • 14 Sept 26 −15
    • Malware scan: pass → unverified security
  • 13 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

  • 12 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 11 Sept 26 0
    • Stability: 0.97 → pass security
Diagnostics

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 20 Sept 2026 · Analysed pypi/queryshield-mcp@1.0.1

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem pypi

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend allowlisted hatchling.build

Background: Why install scripts are a supply-chain risk →

Dependencies 23 packages
Packages resolved 23
Stale 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 3 exposed · ~192 tokens

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 →

Tool Tokens
get_audit_log ~25

Recent audit entries for the calling agent.

NameTypeReqDescription
limitinteger

Structured output declared, but exposes no named fields.

No examples provided.

query_database ~86

Run a natural-language question against a registered database. QueryShield translates to safe SQL, applies row-level security, and audit-logs the call.

NameTypeReqDescription
database_aliasstringyesalias of a database registered for this tenant.
max_rowsintegercap on returned rows (default 100, hard cap 5000).
questionstringyesnatural-language question.

Structured output declared, but exposes no named fields.

No examples provided.

query_database_sql ~81

Run a structured SELECT statement against a registered database. Useful when the agent already knows the schema and wants deterministic SQL (no LLM translation step). The same safety + RLS pipeline still applies — non-SELECTs are rejected.

NameTypeReqDescription
database_aliasstringyes
max_rowsinteger
sqlstringyes

Structured output declared, but exposes no named fields.

No examples provided.

Common questions

What is the io.github.bch1212/queryshield MCP server?

io.github.bch1212/queryshield is an MCP server listed in the public MCP registry as io.github.bch1212/queryshield. Secure SQL proxy for AI agents, NL→SQL, AST safety, per-agent RLS, audit log. This page covers its PyPI package (queryshield-mcp).

Is the io.github.bch1212/queryshield MCP server safe to use?

io.github.bch1212/queryshield scores 80 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. 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.bch1212/queryshield MCP server expose?

io.github.bch1212/queryshield exposes 3 tools: query_database, query_database_sql, get_audit_log. Their descriptions and schemas cost roughly 192 tokens of context every time the server is loaded.

Is the io.github.bch1212/queryshield MCP server still maintained?

io.github.bch1212/queryshield is still listed as active in the MCP registry. We last reached this channel on 20 September 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.bch1212/queryshield MCP server under?

io.github.bch1212/queryshield declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.