MCP Observatory
4m ago Tracked 56,807 Last 4m ago 24h 2,384
github TypeScript re-analysis due

congressgov-mcp-server

github

Access U.S. congressional data - bills, votes, members, committees via MCP. STDIO & Streamable HTTP.

maintainer
cyanheads
licence
Apache-2.0
first seen
2026-05-22
last seen
2026-08-31
releases · 30d
7
short id
risk 17/100 · heuristic grade
B low inferred analyzer v33 (current)
  • capability exposure inferred + 18
  • tool safety inferred + 10
  • trust mitigators mixed − 11

inferred mixed

The A–E grade is our heuristic synthesis — a "review this" prompt, not a verdict. Each factor is tagged by what backs it: attested (a verifiable record), reported (a third party's claim), or inferred (our own heuristic, e.g. permissions). See methodology.

grade last moved 6d ago · see ecosystem CVEs →

risk trajectory 11 movements
  • B · 22 → B · 17
  • B · 30 → B · 22
  • B · 28 → B · 30
  • B · 33 → B · 28
  • C · 38 → B · 33
  • B · 33 → C · 38
  • C · 38 → B · 33
  • B · 33 → C · 38
  • B · 24 → B · 33
  • B · 28 → B · 24
  • B · 19 → B · 28
capability exposure grade factor +18
Inferred surface — each links to servers holding it:
vulnerabilities 0 CVEs

No known CVEs for this server.

tool safety 2 findings · grade factor +10
  1. medium exfiltration combo congressgov_enacted_laws

    single tool reads + sends: fs, net

  2. medium toxic flow (lethal trifecta)

    lethal trifecta reachable across this server's tools: private-data access + untrusted-content ingestion + network exfil

skills & danger signals github-tarball
prompt-surface shipped agent-instruction files + hidden-content / dangerous-code findings — quoted from the analyzed source

analyzed commit 479472c · analyzer v33 · 2w ago

skills & prompt files 34

embed badge readme-ready
live risk-grade badge preview [![MCP Observatory risk grade](https://mcpobservatory.com/servers/smithery:cyanheads/congressgov-mcp-server/badge.svg)](https://mcpobservatory.com/servers/smithery:cyanheads/congressgov-mcp-server/security)

Heuristic, inferred signals — false positives (legitimately powerful tools, forks, language ports) are expected. Treat each as "review this", not a verdict. See the ecosystem-wide picture on the security hub, or the fleet security of cyanheads.