# Congress Member Votes (npm · @pipeworx/mcp-congress-member-votes)

Congress Member Votes -- how each U.S. House member voted, from the U.S. House Clerk's roll-call…

- Trust score: 80/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `gateway.pipeworx.io`: 78/100, [markdown](https://verifymcp.io/servers/pipeworx-io-congress-member-votes/congress-member-votes-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-congress-member-votes/congress-member-votes-mcp)
- npm · `@pipeworx/mcp-congress-member-votes`: 80/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-congress-member-votes/pipeworx-mcp-congress-member-votes.md), [page](https://verifymcp.io/servers/pipeworx-io-congress-member-votes/pipeworx-mcp-congress-member-votes)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-congress-member-votes`
- Version: `0.2.1`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, 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-11-05.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-congress-member-votes).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 5 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 54/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1331 tokens (~443/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 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.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Congress Member Votes MCP server?

Congress Member Votes runs locally as an npm package, launched with npx -y @pipeworx/mcp-congress-member-votes. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add pipeworx-io-congress-member-votes -- npx -y @pipeworx/mcp-congress-member-votes
```

### Cursor

```json
{
  "mcpServers": {
    "pipeworx-io-congress-member-votes": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-congress-member-votes"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pipeworx-io-congress-member-votes": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-congress-member-votes"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add pipeworx-io-congress-member-votes -- npx -y @pipeworx/mcp-congress-member-votes
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pipeworx-io-congress-member-votes": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pipeworx/mcp-congress-member-votes"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pipeworx-io-congress-member-votes --command npx --arg -y --arg @pipeworx/mcp-congress-member-votes
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-congress-member-votes:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-congress-member-votes"]
```

### Netclaw

```json
{
  "McpServers": {
    "pipeworx-io-congress-member-votes": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pipeworx/mcp-congress-member-votes"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pipeworx-io-congress-member-votes -t stdio -c npx -a -y @pipeworx/mcp-congress-member-votes
```

### Other

```json
{
  "mcpServers": {
    "pipeworx-io-congress-member-votes": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-congress-member-votes"
      ]
    }
  }
}
```

## 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-11-03 (score 80, +1)

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

### 2026-11-01 (score 79, +16)

- [security improvement] Malware scan: unverified → pass

### 2026-10-31 (score 63, −15)

- [security regression] Malware scan: pass → unverified
- [functional] Package version: 0.2.0 → 0.2.1

### 2026-10-30 (score 78, +1)

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

### 2026-10-29 (score 77)

First indexed and scored.

## MCP tools (3)

### `member_vote_positions` (~496 tokens)

ANSWERS "how did Rep. X vote on bill Y" / "what were X's last 20 votes" / "did X vote against the budget resolution" -- one member's recorded position (Yea, Nay, Present, Not Voting, or not on the roll) on roll calls, newest first -- House members from the U.S. House Clerk's roll-call votes, senators (chamber "senate") from the Congressional Record, where the Senate's roll calls are printed. Filter by `bill` (e.g. "H R 1"), `question_contains` (matched against question, bill number and description) or a roll range. Quorum calls, Speaker elections and Senate rolls whose record could not be derived are left out unless include_non_recorded is true. Every response names its chamber, congress, session, the last roll it covers and data_as_of. An unknown member or a Congress/session not held returns a named reason, never an empty list.

Input parameters:

- `bill` (string): Legislation number as the Clerk prints it, e.g. "H R 1", "H J RES 104", "S 2403" (punctuation and spacing ignored; exact match).
- `bioguide_id` (string): Bioguide id, e.g. "P000197".
- `chamber` (string): "house" (default) or "senate". The two chambers number their roll calls independently.
- `congress` (number): Congress number, e.g. 119. Default: the newest held.
- `from_roll` (number): First roll number to consider.
- `include_non_recorded` (boolean): Include quorum calls and Speaker-election rolls (default false).
- `limit` (number): Rolls to return (default 20, max 50).
- `name` (string): Surname as the Clerk prints it, e.g. "Pelosi"; combine with state when several members share it.
- `question_contains` (string): Case-insensitive text to match in the vote question, bill number or description, e.g. "suspend the rules", "continuing appropriations".
- `session` (number): 1 or 2. Default: the newest held for the default Congress.
- `state` (string): Two-letter state code to disambiguate a surname.
- `to_roll` (number): Last roll number to consider.

### `member_attendance_party_line` (~490 tokens)

ANSWERS "how many votes did Rep. X miss", "how often does X vote with their party", "party unity score" -- attendance and party-line share for ONE member (House, or a senator with chamber "senate") over a session (or a roll range), computed from the U.S. House Clerk's roll-call votes or, for the Senate, the Congressional Record's printed roll calls. Nothing is returned as a bare percentage: attendance gives its denominator (recorded roll calls the member was on the roll for; quorum calls, Speaker elections and Senate rolls that could not be derived are excluded and counted; rolls before the member was seated or after they left are excluded and counted -- absence from the roll is NOT treated as Not Voting) and splits yea/nay, present and Not Voting. Party line gives two figures, each with its own denominator and exclusions: share of yea/nay votes cast with the member's party majority (a strict majority of that party's yea/nay voters; ties excluded and counted), and party unity (only the roll calls where a majority of Democrats opposed a majority of Republicans). If a figure cannot be computed from the rolls in range (member on none, no party-splitting votes, independent) it is null with a stated reason, never 0% or 100%. Independents (including the Senate's two caucusing independents) have no D-versus-R majority to compare against, so their party-line figure is null with that reason.

Input parameters:

- `bioguide_id` (string): Bioguide id, e.g. "P000197".
- `chamber` (string): "house" (default) or "senate". The two chambers number their roll calls independently.
- `congress` (number): Congress number, e.g. 119. Default: the newest held.
- `from_roll` (number): First roll number of the range (default 1).
- `name` (string): Surname as the Clerk prints it, e.g. "Pelosi"; combine with state when several members share it.
- `session` (number): 1 or 2. Default: the newest held for the default Congress.
- `state` (string): Two-letter state code to disambiguate a surname.
- `to_roll` (number): Last roll number of the range (default: last roll covered).

### `roll_call_positions` (~288 tokens)

ANSWERS "who voted against roll call 100", "how did Texas Republicans split on roll 250", "how many Democrats voted Yea" -- every member's position on ONE roll call (House: the U.S. House Clerk's roll-call votes; Senate: the Congressional Record) with Yea/Nay/Present/Not Voting tallies by party. Pass party (D/R/I), state or position (yea/nay/present/not_voting) to list matching members; with none of these only the tallies and the roll's question, result and bill are returned. A roll number that does not exist in that session returns a named reason.

Input parameters:

- `chamber` (string): "house" (default) or "senate". The two chambers number their roll calls independently.
- `congress` (number): Congress number, e.g. 119. Default: the newest held.
- `party` (string): "D", "R" or "I" to list only that party.
- `position` (string): yea, nay, present or not_voting.
- `roll_number` (number, required): Roll call number within the session, e.g. 100.
- `session` (number): 1 or 2. Default: the newest held for the default Congress.
- `state` (string): Two-letter state code to list only that state's members.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pipeworx-io-congress-member-votes/pipeworx-mcp-congress-member-votes#diagnostics

## Score history

- 2026-11-05: 80
- 2026-11-04: 80
- 2026-11-03: 80
- 2026-11-02: 79
- 2026-11-01: 79
- 2026-10-31: 63
- 2026-10-30: 78
- 2026-10-29: 77

## Common questions

### What is the Congress Member Votes MCP server?

Congress Member Votes is an MCP server listed in the public MCP registry as io.github.pipeworx-io/congress-member-votes. Congress Member Votes -- how each U.S. House member voted, from the U.S. House Clerk's roll-call… This page covers its npm package (@pipeworx/mcp-congress-member-votes).

### Is the Congress Member Votes MCP server safe to use?

Congress Member Votes scores 80 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Congress Member Votes MCP server expose?

Congress Member Votes exposes 3 tools: member_vote_positions, member_attendance_party_line, roll_call_positions. Their descriptions and schemas cost roughly 1,274 tokens of context every time the server is loaded.

### Is the Congress Member Votes MCP server still maintained?

Congress Member Votes is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the Congress Member Votes MCP server under?

Congress Member Votes declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/@pipeworx/mcp-congress-member-votes
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-congress-member-votes
- Repository: https://github.com/pipeworx-io/mcp-congress-member-votes
- Website: https://pipeworx.io/packs/congress-member-votes
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-congress-member-votes/pipeworx-mcp-congress-member-votes.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-congress-member-votes/pipeworx-mcp-congress-member-votes.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-congress-member-votes/pipeworx-mcp-congress-member-votes