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/cyanheads/openstates-mcp-serverWrote 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/cyanheads/openstates-mcp-server/openstates-mcp-server)<a href="https://agentmods.dev/mcp/cyanheads/openstates-mcp-server/openstates-mcp-server"><img src="https://agentmods.dev/badge/mcp/cyanheads/openstates-mcp-server/openstates-mcp-server/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/cyanheads/openstates-mcp-server/openstates-mcp-server"><img src="https://agentmods.dev/badge/mcp/cyanheads/openstates-mcp-server/openstates-mcp-server.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
openstates-mcp-server 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 12d ago.
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
{
"openstates-mcp-server": {
"command": "npx",
"args": [
"-y",
"@cyanheads/openstates-mcp-server"
],
"env": {
"OPENSTATES_API_KEY": "",
"OPENSTATES_DAILY_REQUEST_BUDGET": "250",
"OPENSTATES_REQUEST_TIMEOUT_MS": "45000",
"OPENSTATES_TOTAL_REQUEST_BUDGET_MS": "90000",
"MCP_LOG_LEVEL": "info"
}
}
}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.
- 12d ago First seen · 16 lines scan A 3ffc432adb82
openstates-mcp-server is an MCP server published in the GitHub repository cyanheads/openstates-mcp-server (2 stars, last pushed 18d ago), licensed Apache-2.0. 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-08-31.
Other mcp servers, from other repositories
chestnyznak
MCP server for Chestniy ZNAK — product marking verification, CRPT (Russia). Runs locally from the @theyahia/chestnyznak-mcp npm package.
obsidian-native-mcp
Zero-dependency MCP server for Obsidian vaults. Direct filesystem access — no Obsidian process or REST API plugin needed. Runs locally from the obsidian-native-mcp npm package.
sg-eli-mcp
MCP server for Singapore Statutes Online (sso.agc.gov.sg) — browse, fetch, and cite Singapore legislation by act code. Runs locally from the sg-eli-mcp Python package.
sanctions-screening
Sanctions screening against OFAC SDN, company registry verification and trade-restriction checks. Remote server at hatchloop.dev.
agent-broker
20 tools for sanctions, export-control and company-registry screening, plus messaging. 12 keyless. Remote server at hatchloop.dev.
wikipedia-mcp-server
Search Wikipedia, read summaries and full text, target sections, find nearby pages, list languages. Runs locally from the @cyanheads/wikipedia-mcp-server npm package. Needs 1 environment variable to run.