com.datasparc/dbhawk vs io.github.cyanheads/epa-mcp-server
com.datasparc/dbhawk is an MCP server published by datasparc.com. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.cyanheads/epa-mcp-server is an MCP server published by cyanheads. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-10-27. 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
| Marketplace |  com.datasparc/dbhawk |  io.github.cyanheads/epa-mcp-server |
|---|---|---|
| Official MCP Registry | Listed Version: 0.4.2 Downloads/month (npm): 470 Downloads/week (npm): 233 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 0.6.0 Downloads/month (npm): 1 265 Downloads/week (npm): 409 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
| npm registry (MCP servers) | Not listed | Listed Version: 0.6.0 Downloads/month (npm): 1 265 Downloads/week (npm): 409 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
| Fact | com.datasparc/dbhawk | io.github.cyanheads/epa-mcp-server |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 0 (worse) | 1 (better) |
| Forks (GitHub) | 0 | 0 |
| Last release (differs) | 2026-10-17 (worse) | 2026-10-24 (better) |
| Where it runs (differs) | On your machine (@dbhawk/mcp) | Remote server or your machine |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 3, secrets among them: 1 | 8, secrets among them: 0 |
| Licence (differs) | Not stated | Apache-2.0 |
| Repository (differs) | github.com/datasparc/dbhawk-mcp-plugin | github.com/cyanheads/epa-mcp-server |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 4 days ago |
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
Secure access to DBHawk datasources: browse schemas, run governed queries, DBHawk AI text-to-SQL.
io.github.cyanheads/epa-mcp-server
Search EPA compliance, TRI, Superfund, drinking-water, EJScreen, and AirNow data.
How to run each
com.datasparc/dbhawk As a local MCP server: npm package
claude mcp add --env "DBHAWK_BASE_URL=<YOUR_DBHAWK_BASE_URL>" --env "DBHAWK_TOKEN=<YOUR_DBHAWK_TOKEN>" --transport stdio dbhawk -- npx -y @dbhawk/mcpRequires: DBHAWK_BASE_URL, DBHAWK_TOKEN (secret)
io.github.cyanheads/epa-mcp-server As a remote MCP server
claude mcp add --transport http epa-mcp-server https://epa.caseyjhand.com/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only io.github.cyanheads/epa-mcp-server has a remote endpoint we check. How we check endpoints
Tools each declares
Neither the marketplaces of com.datasparc/dbhawk nor its endpoint list any tools, so we do not compare tools.
Settings each asks for
Only com.datasparc/dbhawk asks for
DBHAWK_BASE_URLDBHAWK_DEFAULT_DATASOURCEDBHAWK_TOKEN (secret)
Only io.github.cyanheads/epa-mcp-server asks for
AIRNOW_API_KEYEJSCREEN_API_BASE_URLMCP_AUTH_MODEMCP_HTTP_ENDPOINT_PATHMCP_HTTP_HOSTMCP_HTTP_PORTMCP_LOG_LEVELMCP_TRANSPORT_TYPE
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.cyanheads/epa-mcp-server · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.