io.github.cyanheads/congressgov-mcp-server
REMOTE · CONGRESSGOV.CASEYJHAND.COM · 2 COMPONENTS · SCANNED SEP 21
Access U.S. congressional data - bills, votes, members, committees - via MCP.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security66
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 10 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability75
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 3720 tokens (~310/item across 12 items; 10 tools + 2 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the io.github.cyanheads/congressgov-mcp-server server?
io.github.cyanheads/congressgov-mcp-server is a hosted endpoint at https://congressgov.caseyjhand.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · congressgov.caseyjhand.com
claude mcp add --transport http cyanheads-congressgov-mcp-server 'https://congressgov.caseyjhand.com/mcp'
{
"mcpServers": {
"cyanheads-congressgov-mcp-server": {
"url": "https://congressgov.caseyjhand.com/mcp"
}
}
} {
"servers": {
"cyanheads-congressgov-mcp-server": {
"type": "http",
"url": "https://congressgov.caseyjhand.com/mcp"
}
}
} [mcp_servers.cyanheads-congressgov-mcp-server] url = "https://congressgov.caseyjhand.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"cyanheads-congressgov-mcp-server": {
"type": "remote",
"url": "https://congressgov.caseyjhand.com/mcp",
"enabled": true
}
}
} openclaw mcp add cyanheads-congressgov-mcp-server --url 'https://congressgov.caseyjhand.com/mcp' --transport streamable-http
mcp_servers:
cyanheads-congressgov-mcp-server:
url: "https://congressgov.caseyjhand.com/mcp" {
"McpServers": {
"cyanheads-congressgov-mcp-server": {
"Transport": "http",
"Url": "https://congressgov.caseyjhand.com/mcp"
}
}
} assistant mcp add cyanheads-congressgov-mcp-server -t streamable-http -u 'https://congressgov.caseyjhand.com/mcp'
{
"mcpServers": {
"cyanheads-congressgov-mcp-server": {
"type": "http",
"url": "https://congressgov.caseyjhand.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 19 Sept 26 0
- Server version: 0.7.0 → 0.7.1 functional
- 9 Sept 26 +1
- Stability: 0.97 → pass security
- 7 Sept 26 −1
- Stability: pass → 0.93 functional
- 31 Aug 26 0
- Server version: 0.6.0 → 0.7.0 functional
- 30 Aug 26 0
- Server version: 0.5.2 → 0.6.0 functional
- “congressgov_committee_lookup” reworded the description of “filter” cosmetic
- Tool “congressgov_member_lookup” changed its title: Congressgov Member Lookup → Congress.gov Member Lookup cosmetic
- Tool “congressgov_bill_lookup” changed its title: Congressgov Bill Lookup → Congress.gov Bill Lookup cosmetic
- Tool “congressgov_bill_summaries” changed its title: Congressgov Bill Summaries → Congress.gov Bill Summaries cosmetic
- Tool “congressgov_committee_lookup” changed its title: Congressgov Committee Lookup → Congress.gov Committee Lookup cosmetic
- Tool “congressgov_committee_reports” changed its title: Congressgov Committee Reports → Congress.gov Committee Reports cosmetic
- Tool “congressgov_crs_reports” changed its title: Congressgov Crs Reports → Congress.gov CRS Reports cosmetic
- Tool “congressgov_daily_record” changed its title: Congressgov Daily Record → Congress.gov Daily Record cosmetic
- Tool “congressgov_enacted_laws” changed its title: Congressgov Enacted Laws → Congress.gov Enacted Laws cosmetic
- Tool “congressgov_roll_votes” changed its title: Congressgov Roll Votes → Congress.gov Roll Votes cosmetic
- Tool “congressgov_senate_nominations” changed its title: Congressgov Senate Nominations → Congress.gov Senate Nominations cosmetic
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 +1
- Stability: 0.97 → pass security
- MCP protocol: Implements a current MCP spec version (2026-07-28). functional
- MCP protocol version: 2025-11-25 → 2026-07-28 functional
- Server version: 0.5.1 → 0.5.2 functional
- 17 Aug 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “congressgov_daily_record” rewrote its description, which is the text the model reads security
- Tool “congressgov_bill_lookup” rewrote its description, which is the text the model reads security
- Tool “congressgov_committee_reports” rewrote its description, which is the text the model reads security
- Schema quality: 238 → 310 ▼ functional
- Server version: 0.4.3 → 0.5.1 functional
- Server version: 0.4.2 → 0.4.3 functional
- Server version: 0.4.1 → 0.4.2 functional
- “congressgov_daily_record” added an optional parameter “articleIndex” cosmetic
- “congressgov_daily_record” added an optional parameter “characterOffset” cosmetic
- “congressgov_daily_record” added an optional parameter “format” cosmetic
- “congressgov_daily_record” added an optional parameter “characterLimit” cosmetic
- “congressgov_bill_lookup” added an optional parameter “characterLimit” cosmetic
- “congressgov_bill_lookup” added an optional parameter “characterOffset” cosmetic
- “congressgov_bill_lookup” added an optional parameter “format” cosmetic
- “congressgov_bill_lookup” added an optional parameter “textVersionIndex” cosmetic
- “congressgov_committee_reports” added an optional parameter “characterLimit” cosmetic
- “congressgov_committee_reports” added an optional parameter “characterOffset” cosmetic
- “congressgov_committee_reports” added an optional parameter “format” cosmetic
- “congressgov_committee_reports” reworded the description of “reportNumber” cosmetic
- “congressgov_committee_reports” reworded the description of “reportType” cosmetic
- “congressgov_enacted_laws” reworded the description of “lawNumber” cosmetic
- “congressgov_committee_lookup” reworded the description of “committeeCode” cosmetic
- “congressgov_bill_lookup” reworded the description of “billNumber” cosmetic
- “congressgov_daily_record” reworded the description of “volumeNumber” cosmetic
- “congressgov_daily_record” reworded the description of “issueNumber” cosmetic
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Sept 2026 · Probed https://congressgov.caseyjhand.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=caseyjhand.com | CN=WE1,O=Google Trust Services,C=US | 4 Sept 2026 | 3 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | a6985204ed51ae050e7738aa6be668e9 |
| SANs: caseyjhand.com, *.caseyjhand.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of congressgov.caseyjhand.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| caseyjhand.com. | present | 2371 | 13 | Verified |
| congressgov.caseyjhand.com. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://congressgov.caseyjhand.com/mcp | Verified | 200 | |
| http (plaintext) | http://congressgov.caseyjhand.com/mcp | HTTPS enforced | 301 | https://congressgov.caseyjhand.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
congressgov_bill_lookup Congress.gov Bill Lookup ~612
Browse and retrieve U.S. legislative bill data from Congress.gov. Discover bills by filtering on congress, bill type, and date range — there is no keyword search. Use 'list' to browse (requires congress, defaults to most-recently-updated first), 'get' for full bill detail (sponsor, policy area, CBO estimates, law info), or drill into a specific bill with 'actions', 'amendments', 'cosponsors', 'committees', 'subjects', 'summaries', 'text', 'titles', or 'related' (each requires congress + billType + billNumber). 'text' lists the published versions and their format URLs; 'content' then reads one version's actual text, a bounded character window at a time.
| Name | Type | Req | Description |
|---|---|---|---|
| billNumber | – | – | Bill number. Required for get and sub-resource operations. Accepts the digit-string form list rows carry (e.g. "9479") as well as a number. |
| billType | string | – | Bill type code. Required for get and sub-resource operations. |
| characterLimit | integer | – | Maximum characters to return for 'content' (1-100000). Legislative documents run past a million characters, so a full bill takes several windows. |
| characterOffset | integer | – | First character to return for 'content', 0-based. Offsets are exact and are never snapped to a section or paragraph break, so feeding the response's nextOffset back walks the whole document with ever… |
| congress | integer | yes | Congress number (e.g., 118, 119). |
| format | string | – | Document format for 'content'. 'text' is GPO's Formatted Text — plain, pre-formatted print output, published for every document checked. 'xml' prefers United States Legislative Markup and falls back… |
| fromDateTime | string | – | Start of date range filter (ISO 8601). Filters by the bill's update date — when Congress.gov last touched the record — not by the bill's latest legislative action. |
| limit | integer | – | Results per page (1-250). |
| offset | integer | – | Pagination offset. |
| operation | string | yes | Which data to retrieve. |
| order | string | – | Sort order for 'list' (sorts by update date). 'recent' (default) is newest first; 'oldest' is ascending. Ignored by other operations. |
| textVersionIndex | integer | – | Which text version 'content' reads, 0-based against the same order 'text' returns — 0 is the most recent version. Ignored by other operations. |
| toDateTime | string | – | End of date range filter (ISO 8601). Same field semantics as fromDateTime. |
| Name | Type | Req | Description |
|---|---|---|---|
| bill | object | – | Dynamic upstream JSON record. |
| content | object | – | Dynamic upstream JSON record. |
| data | array | – | Result rows. Per-tool item shape is rendered in the markdown body. |
| effectiveQuery | string | – | The browse scope and applied filters. |
| error | object | – | Present when the call failed. Absent on success. |
| notice | string | – | Guidance when results are empty, a page is past the end, or a caveat applies. |
| pagination | object | – | Pagination metadata: total count and next offset. |
| totalCount | number | – | Total results across all pages. |
No examples provided.
congressgov_bill_summaries Congress.gov Bill Summaries ~248
Browse recent CRS (Congressional Research Service) bill summaries — plain-language summaries of bills at each legislative stage, useful for answering "what's happening in Congress?". The fromDateTime/toDateTime filters apply to the summary's update time, not the bill's action date, so results include recently rewritten summaries of older bills. Defaults to summaries updated in the last 7 days. Each item shows both the bill's action date and the summary update date. For summaries of one specific bill, use congressgov_bill_lookup with operation='summaries' instead.
| Name | Type | Req | Description |
|---|---|---|---|
| billType | string | – | Bill type filter. Requires 'congress'. |
| congress | integer | – | Congress number. Optional — omit for summaries across all congresses. |
| fromDateTime | string | – | Start of date range (ISO 8601), filtered on the summary update time. Defaults to 7 days ago if neither date param is set. |
| limit | integer | – | Results per page (1-250). |
| offset | integer | – | Pagination offset. |
| toDateTime | string | – | End of date range (ISO 8601), filtered on the summary update time. Defaults to now. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | array | – | Result rows. Per-tool item shape is rendered in the markdown body. |
| effectiveQuery | string | – | The browse scope and applied filters. |
| error | object | – | Present when the call failed. Absent on success. |
| notice | string | – | Guidance when results are empty, a page is past the end, or a caveat applies. |
| pagination | object | – | Pagination metadata: total count and next offset. |
| totalCount | number | – | Total results across all pages. |
No examples provided.
congressgov_committee_lookup Congress.gov Committee Lookup ~441
Browse congressional committees and their legislation, reports, and nominations. Committee codes follow the pattern chamber-prefix (h/s/j) + abbreviation + 2-digit number — use 'list' (with optional 'filter' for name→code resolution) to discover codes, then 'get' or drill into 'bills', 'reports', or 'nominations' ('nominations' is Senate-only). 'get' and sub-resources only need committeeCode (chamber is inferred from the prefix); pass chamber explicitly to override. The 'bills' sub-resource defaults to 'recent' order (newest update-date first); pass order='oldest' for ascending update-date order. Upstream omits bill titles from the 'bills' sub-resource — rows carry only {congress, billType, billNumber, actionDate, relationshipType, url}; chain 'congressgov_bill_lookup get' per row to retrieve titles and policy area.
| Name | Type | Req | Description |
|---|---|---|---|
| chamber | string | – | Chamber filter for 'list', or override for 'get' and sub-resources (otherwise inferred from committeeCode prefix). |
| committeeCode | string | – | Committee system code, e.g. 'hsju00'. Required for 'get' and sub-resources. Codes are letters + a 2-digit suffix and are matched case-insensitively. Any other non-blank value is treated as a committe… |
| congress | integer | – | Congress number. |
| filter | string | – | Filter committee-list results by name (e.g., 'transportation', 'armed services'). Only meaningful for 'list'; fuzzy-matched rows are labeled approximate. |
| limit | integer | – | Results per page (1-250). |
| offset | integer | – | Pagination offset. |
| operation | string | yes | Which data to retrieve. |
| order | string | – | Sort order for the 'bills' sub-resource. 'recent' (default) returns newest update-date first; 'oldest' returns ascending update-date order. Ignored by other operations. |
| Name | Type | Req | Description |
|---|---|---|---|
| committee | object | – | Dynamic upstream JSON record. |
| data | array | – | Result rows. Per-tool item shape is rendered in the markdown body. |
| effectiveQuery | string | – | The browse scope and applied filters. |
| error | object | – | Present when the call failed. Absent on success. |
| notice | string | – | Guidance when results are empty, a page is past the end, or a caveat applies. |
| pagination | object | – | Pagination metadata: total count and next offset. |
| totalCount | number | – | Total results across all pages. |
No examples provided.
congressgov_committee_reports Congress.gov Committee Reports ~364
Browse and retrieve committee reports from Congress.gov — reports accompany legislation reported out of committee and explain the bill's purpose, committee amendments, dissenting views, and the committee vote. Report types are 'hrpt' (House), 'srpt' (Senate), and 'erpt' (Executive). 'text' lists the published format URLs; 'content' then reads the report's actual text, a bounded character window at a time.
| Name | Type | Req | Description |
|---|---|---|---|
| characterLimit | integer | – | Maximum characters to return for 'content' (1-100000). Legislative documents run past a million characters, so a full bill takes several windows. |
| characterOffset | integer | – | First character to return for 'content', 0-based. Offsets are exact and are never snapped to a section or paragraph break, so feeding the response's nextOffset back walks the whole document with ever… |
| congress | integer | yes | Congress number. |
| format | string | – | Document format for 'content'. 'text' is GPO's Formatted Text — plain, pre-formatted print output, published for every document checked. 'xml' prefers United States Legislative Markup and falls back… |
| limit | integer | – | Results per page (1-250). |
| offset | integer | – | Pagination offset. |
| operation | string | yes | Which data to retrieve. |
| reportNumber | integer | – | Committee report number. Required for get, text, and content operations. |
| reportType | string | – | Report type. Required for get, text, and content operations. |
| Name | Type | Req | Description |
|---|---|---|---|
| content | object | – | Dynamic upstream JSON record. |
| data | array | – | Result rows. Per-tool item shape is rendered in the markdown body. |
| effectiveQuery | string | – | The browse scope and applied filters. |
| error | object | – | Present when the call failed. Absent on success. |
| notice | string | – | Guidance when results are empty, a page is past the end, or a caveat applies. |
| pagination | object | – | Pagination metadata: total count and next offset. |
| report | object | – | Dynamic upstream JSON record. |
| text | array | – | Dynamic upstream JSON records. |
| totalCount | number | – | Total results across all pages. |
No examples provided.
congressgov_crs_reports Congress.gov CRS Reports ~155
Browse and retrieve CRS (Congressional Research Service) reports — nonpartisan policy analyses by subject-matter experts at the Library of Congress, covering policy areas, legislative proposals, and legal questions. Report IDs use letter-number codes (e.g., R40097, RL33612, IF12345). Use 'list' to browse available reports or 'get' for full detail (authors, topics, summary, download formats).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Results per page (1-250). |
| offset | integer | – | Pagination offset. |
| operation | string | yes | Which data to retrieve. |
| reportNumber | string | – | CRS report ID (e.g., 'R40097'). Required for 'get'. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | array | – | Result rows. Per-tool item shape is rendered in the markdown body. |
| effectiveQuery | string | – | The browse scope and applied filters. |
| error | object | – | Present when the call failed. Absent on success. |
| notice | string | – | Guidance when results are empty, a page is past the end, or a caveat applies. |
| pagination | object | – | Pagination metadata: total count and next offset. |
| report | object | – | Dynamic upstream JSON record. |
| totalCount | number | – | Total results across all pages. |
No examples provided.
congressgov_daily_record Congress.gov Daily Record ~447
Browse the daily Congressional Record — floor speeches, debates, and legislative text published each day Congress is in session. Navigation is hierarchical: volumes (via 'list') → issues (via 'issues') → articles (via 'articles'). Use 'list' to find recent volumes, 'issues' to see what's in a volume, and 'articles' to access individual speeches and debate sections. 'articles' lists each article and its format URLs; 'content' then reads one article's actual text, a bounded character window at a time.
| Name | Type | Req | Description |
|---|---|---|---|
| articleIndex | integer | – | Which article 'content' reads, 0-based against the issue's whole article sequence — the same absolute position 'articles' pages through with offset. Ignored by other operations. |
| characterLimit | integer | – | Maximum characters to return for 'content' (1-100000). Legislative documents run past a million characters, so a full bill takes several windows. |
| characterOffset | integer | – | First character to return for 'content', 0-based. Offsets are exact and are never snapped to a section or paragraph break, so feeding the response's nextOffset back walks the whole document with ever… |
| format | string | – | Document format for 'content'. 'text' is GPO's Formatted Text — plain, pre-formatted print output, published for every document checked. 'xml' prefers United States Legislative Markup and falls back… |
| issueNumber | – | – | Issue number within a volume. Required for 'articles' and 'content'. List rows carry this as a string (e.g. "109") — both forms are accepted. |
| limit | integer | – | Results per page (1-250). |
| offset | integer | – | Pagination offset. |
| operation | string | yes | Which data to retrieve. |
| volumeNumber | – | – | Volume number. Required for 'issues', 'articles', and 'content'. Accepts a number or the digit-string form list rows carry. |
| Name | Type | Req | Description |
|---|---|---|---|
| content | object | – | Dynamic upstream JSON record. |
| data | array | – | Result rows. Per-tool item shape is rendered in the markdown body. |
| effectiveQuery | string | – | The browse scope and applied filters. |
| error | object | – | Present when the call failed. Absent on success. |
| notice | string | – | Guidance when results are empty, a page is past the end, or a caveat applies. |
| pagination | object | – | Pagination metadata: total count and next offset. |
| totalCount | number | – | Total results across all pages. |
No examples provided.
congressgov_enacted_laws Congress.gov Enacted Laws ~278
Browse enacted public and private laws from Congress.gov by congress and law type ('pub' for public laws, 'priv' for private). 'list' filters by enactment status and law type — the discovery path 'bill_lookup' does not offer. 'get' returns the origin bill record (sponsor, actions, summaries, text), with the public/private law citation on the bill's 'laws' array (e.g. {"number":"118-2","type":"Public Law"}).
| Name | Type | Req | Description |
|---|---|---|---|
| congress | integer | yes | Congress number. |
| lawNumber | – | – | Law number, as carried by a 'list' row's `laws[].number` — either the full citation ('118-90', rendered as 'Public Law 118-90') or the portion after the hyphen ('90'); the prefix is the congress and… |
| lawType | string | – | Law type — 'pub' (public laws, general application, most common) or 'priv' (private laws, specific individuals or entities). Required for 'get'. |
| limit | integer | – | Results per page (1-250). |
| offset | integer | – | Pagination offset. |
| operation | string | yes | Which data to retrieve. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | array | – | Result rows. Per-tool item shape is rendered in the markdown body. |
| effectiveQuery | string | – | The browse scope and applied filters. |
| error | object | – | Present when the call failed. Absent on success. |
| law | object | – | Dynamic upstream JSON record. |
| notice | string | – | Guidance when results are empty, a page is past the end, or a caveat applies. |
| pagination | object | – | Pagination metadata: total count and next offset. |
| totalCount | number | – | Total results across all pages. |
No examples provided.
congressgov_member_lookup Congress.gov Member Lookup ~247
Discover congressional members and their legislative activity. No name search. For 'list', filter by stateCode (optionally with district), by congress, or by both together (e.g., 118th Congress + CA, or CA district 12 in the 118th). Add currentMember=true to restrict to currently serving members. Once you have a bioguideId, use 'get' for full profile or 'sponsored'/'cosponsored' for their legislative portfolio.
| Name | Type | Req | Description |
|---|---|---|---|
| bioguideId | string | – | Unique member identifier (e.g., 'P000197'). Required for get/sponsored/cosponsored. |
| congress | integer | – | Congress number to filter by. |
| currentMember | boolean | – | Filter to currently serving members. Omit to include both current and former members. |
| district | integer | – | Congressional district number. Requires stateCode. Use 0 for at-large. |
| limit | integer | – | Results per page (1-250). |
| offset | integer | – | Pagination offset. |
| operation | string | yes | Which data to retrieve. |
| stateCode | string | – | Two-letter state code (e.g., 'CA', 'TX'). |
| Name | Type | Req | Description |
|---|---|---|---|
| data | array | – | Result rows. Per-tool item shape is rendered in the markdown body. |
| effectiveQuery | string | – | The browse scope and applied filters. |
| error | object | – | Present when the call failed. Absent on success. |
| member | object | – | Dynamic upstream JSON record. |
| notice | string | – | Guidance when results are empty, a page is past the end, or a caveat applies. |
| pagination | object | – | Pagination metadata: total count and next offset. |
| totalCount | number | – | Total results across all pages. |
No examples provided.
congressgov_roll_votes Congress.gov Roll Votes ~324
Retrieve U.S. congressional roll call votes and individual member voting positions for either chamber. Set 'chamber' to 'house' (default, from the Congress.gov API) or 'senate' (from the Senate's official LIS feed). Use 'list' to find votes by congress and session (newest first by default), 'get' for vote details (question, result, tallies, party breakdown, associated bill/nomination/amendment), or 'members' for how each member voted.
| Name | Type | Req | Description |
|---|---|---|---|
| chamber | string | – | Chamber whose votes to query. 'house' (default) draws from the Congress.gov API; 'senate' draws from the Senate's official LIS roll-call feed. Roll call numbers reset each session and are specific to… |
| congress | integer | yes | Congress number. |
| limit | integer | – | Results per page (1-250). |
| offset | integer | – | Pagination offset. |
| operation | string | yes | Which data to retrieve. |
| order | string | – | Sort order for 'list'. 'recent' (default) returns newest first; 'oldest' returns ascending. House sorts by vote update date (with 'recent', offset=0 always returns the strictly newest page); Senate s… |
| session | integer | yes | Session number (1 or 2). Odd years are session 1, even years session 2. |
| voteNumber | integer | – | Roll call vote number. Required for 'get' and 'members'. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | array | – | Result rows. Per-tool item shape is rendered in the markdown body. |
| effectiveQuery | string | – | The browse scope and applied filters. |
| error | object | – | Present when the call failed. Absent on success. |
| notice | string | – | Guidance when results are empty, a page is past the end, or a caveat applies. |
| pagination | object | – | Pagination metadata: total count and next offset. |
| totalCount | number | – | Total results across all pages. |
| vote | object | – | Dynamic upstream JSON record. |
No examples provided.
congressgov_senate_nominations Congress.gov Senate Nominations ~358
Browse presidential nominations to federal positions and track the Senate confirmation process. Use 'list' to browse, 'get' for nomination detail, 'actions'/'committees'/'hearings' for confirmation pipeline data, or 'nominees' to retrieve individual appointees in a multi-nominee batch. Nominations use 'PN' (Presidential Nomination) numbering. Most nominations carry confirmation activity on the parent (e.g., PN1000); multi-part parents (e.g., PN851) carry no activity of their own — their actions, committees, hearings, and nominees live on partitioned children (PN851-1, PN851-2, …). 'get' on a parent that has no `nominees` array signals the partitioned form is needed for everything below it.
| Name | Type | Req | Description |
|---|---|---|---|
| congress | integer | yes | Congress number. |
| limit | integer | – | Results per page (1-250). |
| nominationNumber | string | – | Nomination number. Use the bare form (e.g. '1000') for nominations whose activity sits on the parent; use the partitioned form (e.g. '851-1') for sub-resources of a multi-part nomination. Required fo… |
| offset | integer | – | Pagination offset. |
| operation | string | yes | Which data to retrieve. |
| ordinal | integer | – | Batch ordinal within a multi-nominee nomination. Each ordinal addresses a group of nominees; the 'nominees' operation returns every individual in that batch. Use 'get' first to see available ordinals… |
| Name | Type | Req | Description |
|---|---|---|---|
| data | array | – | Result rows. Per-tool item shape is rendered in the markdown body. |
| effectiveQuery | string | – | The browse scope and applied filters. |
| error | object | – | Present when the call failed. Absent on success. |
| nomination | object | – | Dynamic upstream JSON record. |
| notice | string | – | Guidance when results are empty, a page is past the end, or a caveat applies. |
| pagination | object | – | Pagination metadata: total count and next offset. |
| totalCount | number | – | Total results across all pages. |
No examples provided.
What is the io.github.cyanheads/congressgov-mcp-server server?
io.github.cyanheads/congressgov-mcp-server is listed in the public MCP registry as io.github.cyanheads/congressgov-mcp-server. Access U.S. congressional data - bills, votes, members, committees - via MCP. This page covers its hosted endpoint (https://congressgov.caseyjhand.com/mcp).
Is the io.github.cyanheads/congressgov-mcp-server server safe to use?
io.github.cyanheads/congressgov-mcp-server scores 82 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.cyanheads/congressgov-mcp-server server expose?
io.github.cyanheads/congressgov-mcp-server exposes 10 tools: congressgov_bill_lookup, congressgov_enacted_laws, congressgov_member_lookup, congressgov_committee_lookup, congressgov_roll_votes, and 5 more. Their descriptions and schemas cost roughly 3,474 tokens of context every time the server is loaded.
Does the io.github.cyanheads/congressgov-mcp-server server require authentication?
No. We connected to io.github.cyanheads/congressgov-mcp-server without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.cyanheads/congressgov-mcp-server server still maintained?
io.github.cyanheads/congressgov-mcp-server is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.