CCongressmcpAn MCP server for the Congress.gov API that consolidates 91 operations into 6 comprehensive tools that can be used by any MCP client (i.e. Claude Desktop), or MCP-compatible AI agent, to query and reason about congressional data. It has: full coverage of the Congress.gov APi, an NPM published bridge to enable stdio on local MCP clients, a web server over http transport, authentication, account and API key management. Use cases organized by user type: Policy Professionals: - Track bills by keyword ("AI", "climate") - Monitor swing-state voting patterns - Research bill co-sponsors and amendments Government Affairs: - Daily briefings: "What happened in Congress yesterday?" - Voting history for upcoming meetings - Industry-specific legislative tracking Journalists: - Find voting pattern changes - Background research on members - Story leads from committee activities AI Workflows: - "Summarize all crypto bills and status" - Generate weekly legislative updates - Create talking points for hearings
mcp-so:congressmcp_Alex Murshak
View sourceFirst Seen
Feb 18, 2026
Last Scanned
Feb 18, 2026
Findings
2
Score
92/100
Findings (2)
Detects -y, --yes, or --auto-approve flags in MCP/skill install commands that bypass user confirmation
"-y" Remove the -y/--yes auto-confirm flag from MCP server launch arguments. This flag bypasses user confirmation prompts and allows unattended execution of potentially dangerous operations.
Likely FP if the matched text is an isolated flag (-y or --yes) in documentation describing command-line options, not in an actual MCP config.
Detects MCP server configs using npx to run packages without version pinning
"command": "npx" Pin the npx package in the MCP config to an exact version (e.g., @scope/server@1.2.3). Unpinned npx commands can silently fetch a compromised package version.
Likely FP if the MCP config is a local development setup example, though unpinned npx in production configs is a real supply chain risk.