# io.github.cyanheads/congressgov-mcp-server (remote · congressgov.caseyjhand.com)

Access U.S. congressional data - bills, votes, members, committees - via MCP.

- Trust score: 71/100 (medium)
- Change this week: +5
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `congressgov.caseyjhand.com`: 71/100 (this document), [markdown](https://verifymcp.io/servers/cyanheads-congressgov-mcp-server/congressgov.md), [page](https://verifymcp.io/servers/cyanheads-congressgov-mcp-server/congressgov)
- npm · `@cyanheads/congressgov-mcp-server`: 35/100, [markdown](https://verifymcp.io/servers/cyanheads-congressgov-mcp-server/cyanheads-congressgov-mcp-server.md), [page](https://verifymcp.io/servers/cyanheads-congressgov-mcp-server/cyanheads-congressgov-mcp-server)

## Channel facts

- Endpoint: `https://congressgov.caseyjhand.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.4.1`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 66/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 76/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 2860 tokens (~238/item across 12 items; 10 tools + 2 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http cyanheads-congressgov-mcp-server https://congressgov.caseyjhand.com/mcp
```

### Codex

```toml
[mcp_servers.cyanheads-congressgov-mcp-server]
url = "https://congressgov.caseyjhand.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "cyanheads-congressgov-mcp-server": {
      "type": "remote",
      "url": "https://congressgov.caseyjhand.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add cyanheads-congressgov-mcp-server --url https://congressgov.caseyjhand.com/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  cyanheads-congressgov-mcp-server:
    url: "https://congressgov.caseyjhand.com/mcp"
```

### Other

```json
{
  "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.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-01 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 69, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 68, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-28 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 66, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 66)

First indexed and scored.

## MCP tools (10)

### `congressgov_bill_lookup` (~338 tokens)

Congressgov Bill Lookup

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).

Input parameters:

- `billNumber` (integer): Bill number. Required for get and sub-resource operations.
- `billType` (string): Bill type code. Required for get and sub-resource operations.
- `congress` (integer, required): Congress number (e.g., 118, 119).
- `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, required): 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.
- `toDateTime` (string): End of date range filter (ISO 8601). Same field semantics as fromDateTime.

Output parameters:

- `data` (array): Result rows. Per-tool item shape is rendered in the markdown body.
- `effectiveQuery` (string): The browse scope and applied filters.
- `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.

### `congressgov_enacted_laws` (~210 tokens)

Congressgov Enacted Laws

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"}).

Input parameters:

- `congress` (integer, required): Congress number.
- `lawNumber` (integer): Law number. Required for 'get'.
- `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, required): Which data to retrieve.

Output parameters:

- `data` (array): Result rows. Per-tool item shape is rendered in the markdown body.
- `effectiveQuery` (string): The browse scope and applied filters.
- `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.

### `congressgov_member_lookup` (~247 tokens)

Congressgov Member Lookup

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.

Input parameters:

- `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, required): Which data to retrieve.
- `stateCode` (string): Two-letter state code (e.g., 'CA', 'TX').

Output parameters:

- `data` (array): Result rows. Per-tool item shape is rendered in the markdown body.
- `effectiveQuery` (string): The browse scope and applied filters.
- `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.

### `congressgov_committee_lookup` (~434 tokens)

Congressgov Committee Lookup

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.

Input parameters:

- `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 lowercase letters + 2-digit suffix. Pass a committee name here and the tool will attempt to resolve it automatica…
- `congress` (integer): Congress number.
- `filter` (string): Filter committee list results by name (e.g., 'transportation', 'armed services'). Only meaningful for 'list'. Fetches the full chamber set and matches client-side; fuzzy-matched rows are labeled appr…
- `limit` (integer): Results per page (1-250).
- `offset` (integer): Pagination offset.
- `operation` (string, required): 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.

Output parameters:

- `data` (array): Result rows. Per-tool item shape is rendered in the markdown body.
- `effectiveQuery` (string): The browse scope and applied filters.
- `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.

### `congressgov_roll_votes` (~324 tokens)

Congressgov Roll Votes

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.

Input parameters:

- `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, required): Congress number.
- `limit` (integer): Results per page (1-250).
- `offset` (integer): Pagination offset.
- `operation` (string, required): 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, required): 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'.

Output parameters:

- `data` (array): Result rows. Per-tool item shape is rendered in the markdown body.
- `effectiveQuery` (string): The browse scope and applied filters.
- `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.

### `congressgov_senate_nominations` (~358 tokens)

Congressgov Senate Nominations

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.

Input parameters:

- `congress` (integer, required): 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, required): 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…

Output parameters:

- `data` (array): Result rows. Per-tool item shape is rendered in the markdown body.
- `effectiveQuery` (string): The browse scope and applied filters.
- `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.

### `congressgov_bill_summaries` (~248 tokens)

Congressgov Bill Summaries

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.

Input parameters:

- `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.

Output parameters:

- `data` (array): Result rows. Per-tool item shape is rendered in the markdown body.
- `effectiveQuery` (string): The browse scope and applied filters.
- `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.

### `congressgov_crs_reports` (~155 tokens)

Congressgov Crs Reports

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).

Input parameters:

- `limit` (integer): Results per page (1-250).
- `offset` (integer): Pagination offset.
- `operation` (string, required): Which data to retrieve.
- `reportNumber` (string): CRS report ID (e.g., 'R40097'). Required for 'get'.

Output parameters:

- `data` (array): Result rows. Per-tool item shape is rendered in the markdown body.
- `effectiveQuery` (string): The browse scope and applied filters.
- `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.

### `congressgov_committee_reports` (~150 tokens)

Congressgov Committee Reports

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).

Input parameters:

- `congress` (integer, required): Congress number.
- `limit` (integer): Results per page (1-250).
- `offset` (integer): Pagination offset.
- `operation` (string, required): Which data to retrieve.
- `reportNumber` (integer): Committee report number. Required for get and text operations.
- `reportType` (string): Report type. Required for get and text operations.

Output parameters:

- `data` (array): Result rows. Per-tool item shape is rendered in the markdown body.
- `effectiveQuery` (string): The browse scope and applied filters.
- `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.

### `congressgov_daily_record` (~158 tokens)

Congressgov Daily Record

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.

Input parameters:

- `issueNumber` (integer): Issue number within a volume. Required for 'articles'.
- `limit` (integer): Results per page (1-250).
- `offset` (integer): Pagination offset.
- `operation` (string, required): Which data to retrieve.
- `volumeNumber` (integer): Volume number. Required for 'issues' and 'articles'.

Output parameters:

- `data` (array): Result rows. Per-tool item shape is rendered in the markdown body.
- `effectiveQuery` (string): The browse scope and applied filters.
- `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.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/cyanheads-congressgov-mcp-server/congressgov#diagnostics

## Score history

- 2026-08-03: 71
- 2026-08-02: 70
- 2026-08-01: 70
- 2026-07-31: 69
- 2026-07-30: 68
- 2026-07-29: 68
- 2026-07-28: 67
- 2026-07-27: 66
- 2026-07-26: 66

## Links

- Remote endpoint: https://congressgov.caseyjhand.com/mcp
- Repository: https://github.com/cyanheads/congressgov-mcp-server
- Changelog RSS feed: https://verifymcp.io/servers/cyanheads-congressgov-mcp-server/congressgov/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/cyanheads-congressgov-mcp-server/congressgov/changelog.json
- HTML version of this page: https://verifymcp.io/servers/cyanheads-congressgov-mcp-server/congressgov