Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/lzinga/us-gov-open-data-mcpWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/lzinga/us-gov-open-data-mcp/us-gov-open-data)<a href="https://agentmods.dev/mcp/lzinga/us-gov-open-data-mcp/us-gov-open-data"><img src="https://agentmods.dev/badge/mcp/lzinga/us-gov-open-data-mcp/us-gov-open-data/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/lzinga/us-gov-open-data-mcp/us-gov-open-data"><img src="https://agentmods.dev/badge/mcp/lzinga/us-gov-open-data-mcp/us-gov-open-data.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
us-gov-open-data scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"us-gov-open-data": {
"command": "node",
"args": [
"dist/server.js"
],
"cwd": "${workspaceFolder}"
}
}What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- yesterday First seen · 9 lines scan A 204f99ec623a
us-gov-open-data is an MCP server published in the GitHub repository lzinga/us-gov-open-data-mcp (109 stars, last pushed yesterday), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-11.
Other mcp servers, from other repositories
dbconvert-streams
Read-only SQL across PostgreSQL, MySQL, S3 buckets and local data files — one query can join across all of them. MCP server. Runs locally from the @dbconvert/stream-mcp npm package. Needs 1 environment variable to run.
tako-mcp
Search, answer, and fetch Tako's knowledge base of 100K+ data charts, plus deep research agents. Remote server at mcp.tako.com.
dingdawg-data-agent
AI data agent — schema analysis, query optimization, PII detection, pipelines. Runs locally from the dingdawg-data-agent npm package. Needs 1 environment variable to run.
foundry-api
Bounded tools for rendering, extraction, RAG, enrichment, local discovery and review analysis. Remote server at prodapi.live.
zkshare
ZKshare stdio MCP: store/prove/share, semantic search, sandbox proxy to HTTPS /api/v1/context. Runs locally from the zkshare-mcp npm package. Needs 2 environment variables to run.
lightrag_mcp
MCP Server for LightRAG. Runs locally from the lightrag_mcp Python package.