Ext Ops Panel
Open dashboard
Comparison

com.datasparc/dbhawk vs io.github.bch1212/queryshield

com.datasparc/dbhawk is an MCP server published by datasparc.com. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.bch1212/queryshield is an MCP server published by bch1212. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-18. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
Marketplacecom.datasparc/dbhawkio.github.bch1212/queryshield
Official MCP Registry Listed
Version: 0.4.2
Downloads/month (npm): 237
Downloads/week (npm): 35
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 1.0.1
Downloads/month (PyPI): 58
Downloads/week (PyPI): 22
Forks (GitHub): 0
Stars (GitHub): 1
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

com.datasparc/dbhawk vs io.github.bch1212/queryshield
Factcom.datasparc/dbhawkio.github.bch1212/queryshield
Marketplaces that list it11
Stars (GitHub) (differs)0 (worse)1 (better)
Forks (GitHub)00
Last release (differs)2026-10-17Not published
Where it runs (differs)On your machine (@dbhawk/mcp)On your machine (queryshield-mcp)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)3, secrets among them: 12, secrets among them: 1
LicenceNot statedNot stated
Repository (differs)github.com/datasparc/dbhawk-mcp-plugingithub.com/bch1212/queryshield
Changes in the last 7 days (differs)20
First seen2026-10-112026-10-11

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

com.datasparc/dbhawk

In its own words, on Official MCP Registry:

Secure access to DBHawk datasources: browse schemas, run governed queries, DBHawk AI text-to-SQL.

io.github.bch1212/queryshield

In its own words, on Official MCP Registry:

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

How to run each

com.datasparc/dbhawk As a local MCP server: npm package

Claude Code
claude mcp add --env "DBHAWK_BASE_URL=<YOUR_DBHAWK_BASE_URL>" --env "DBHAWK_TOKEN=<YOUR_DBHAWK_TOKEN>" --transport stdio dbhawk -- npx -y @dbhawk/mcp

Requires: DBHAWK_BASE_URL, DBHAWK_TOKEN (secret)

io.github.bch1212/queryshield As a local MCP server: PyPI package

Claude Code
claude mcp add --env "QUERYSHIELD_API_KEY=<YOUR_QUERYSHIELD_API_KEY>" --transport stdio queryshield -- uvx queryshield-mcp

Requires: QUERYSHIELD_API_KEY (secret)

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Only com.datasparc/dbhawk asks for

  • DBHAWK_BASE_URL
  • DBHAWK_DEFAULT_DATASOURCE
  • DBHAWK_TOKEN (secret)

Only io.github.bch1212/queryshield asks for

  • QUERYSHIELD_API_KEY (secret)
  • QUERYSHIELD_BASE_URL

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: com.datasparc/dbhawk · What it can do: io.github.bch1212/queryshield · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built