Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Congress Member Votes

NPM · @PIPEWORX/MCP-CONGRESS-MEMBER-VOTES · 2 COMPONENTS

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

80 Trust /100

Last scanned (23 hours ago)

Scores higher than 65% of npm servers

Category News and Social

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-congress-member-votes). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 4 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability54
  • AI-judged instruction clarity (good).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
  • Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Changelog

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.

  • 3 Nov 26 +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.

  • 1 Nov 26 +16
    • Malware scan: unverified → pass ▲ security
  • 31 Oct 26 −15
    • Malware scan: pass → unverified ▼ security
    • Package version: 0.2.0 → 0.2.1 functional
  • 30 Oct 26 +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.

  • 29 Oct 26 77

    First indexed and scored.

Diagnostics

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 4 Nov 2026 · Analysed npm/@pipeworx/mcp-congress-member-votes@0.2.1

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo pipeworx-io/mcp-congress-member-votes
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/pipeworx-io/mcp-congress-member-votes/.github/workflows/publish.yml@refs/heads/main
Rekor log index 3612225169
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:ab5fcfbed0d861f3a058d6bfa724213f969cd4eb9352bf6f8d7cd7b5ca73f53cca8ab220d9907d0738b717d9314640cd91513d22ecd055dab98f82b13

Background: How many MCP packages publish verified provenance →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 3 exposed · ~1,274 tokens

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 →

Tool Tokens
member_attendance_party_line ~490

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.

NameTypeReqDescription
bioguide_idstring–Bioguide id, e.g. "P000197".
chamberstring–"house" (default) or "senate". The two chambers number their roll calls independently.
congressnumber–Congress number, e.g. 119. Default: the newest held.
from_rollnumber–First roll number of the range (default 1).
namestring–Surname as the Clerk prints it, e.g. "Pelosi"; combine with state when several members share it.
sessionnumber–1 or 2. Default: the newest held for the default Congress.
statestring–Two-letter state code to disambiguate a surname.
to_rollnumber–Last roll number of the range (default: last roll covered).

No output schema declared.

No examples provided.

member_vote_positions ~496

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.

NameTypeReqDescription
billstring–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_idstring–Bioguide id, e.g. "P000197".
chamberstring–"house" (default) or "senate". The two chambers number their roll calls independently.
congressnumber–Congress number, e.g. 119. Default: the newest held.
from_rollnumber–First roll number to consider.
include_non_recordedboolean–Include quorum calls and Speaker-election rolls (default false).
limitnumber–Rolls to return (default 20, max 50).
namestring–Surname as the Clerk prints it, e.g. "Pelosi"; combine with state when several members share it.
question_containsstring–Case-insensitive text to match in the vote question, bill number or description, e.g. "suspend the rules", "continuing appropriations".
sessionnumber–1 or 2. Default: the newest held for the default Congress.
statestring–Two-letter state code to disambiguate a surname.
to_rollnumber–Last roll number to consider.

No output schema declared.

No examples provided.

roll_call_positions ~288

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.

NameTypeReqDescription
chamberstring–"house" (default) or "senate". The two chambers number their roll calls independently.
congressnumber–Congress number, e.g. 119. Default: the newest held.
partystring–"D", "R" or "I" to list only that party.
positionstring–yea, nay, present or not_voting.
roll_numbernumberyesRoll call number within the session, e.g. 100.
sessionnumber–1 or 2. Default: the newest held for the default Congress.
statestring–Two-letter state code to list only that state's members.

No output schema declared.

No examples provided.

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.

npm · @pipeworx/mcp-congress-member-votes

# add to Claude Code
claude mcp add pipeworx-io-congress-member-votes -- npx -y @pipeworx/mcp-congress-member-votes
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 4 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 4 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.