Us Race Matchups
NPM · @PIPEWORX/MCP-US-RACE-MATCHUPS · 2 COMPONENTS
US race matchups — one call per federal race: who holds the seat, who is running, which of them…
Available components
Last scanned (7 hours ago)
Scores higher than 61% of npm servers
Category News and Social
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-us-race-matchups). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 6 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability65
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 418 tokens (~209/item across 2 items; 2 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 Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 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
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
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.
- 30 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 29 Oct 26 64
First indexed and scored.
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 5 Nov 2026 · Analysed npm/@pipeworx/mcp-us-race-matchups@0.2.0
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-us-race-matchups |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-us-race-matchups/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3575128062 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:054cc5ae42003bb2353382daacb37824ea5a9ad32897a1d73cdc059d4a950862688710bd9b10880aee1593645297cebdcf6ecd53d35407dc6ee06b61e |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
list_races ~133
Every federal race in a state for a cycle (the Senate seat if any, and each House district) with how many distinct people registered with the FEC and who the sitting officeholder is (incumbent; incumbent_note says when the seat is open and they are not a candidate). Use it to find the district number before calling race_matchup.
| Name | Type | Req | Description |
|---|---|---|---|
| cycle | number | – | Election year, even. Default 2026. |
| office | string | – | Optional: "house" or "senate" to restrict. |
| state | string | yes | US state: postal code ("IA") or full name. |
No output schema declared.
No examples provided.
race_matchup ~227
One US House district or Senate seat: who the sitting officeholder is (incumbent, with seeking_reelection and incumbent_note saying whether they are actually on the ballot or the seat is open), every FEC-registered candidate by party with money raised/spent/cash on hand, which candidates won their primary, primary and general election dates. Primary vote counts come from Wikipedia (non-official, labelled as such, cites the state election authority); money and incumbency are FEC. A district that does not exist returns an error naming the districts that do.
| Name | Type | Req | Description |
|---|---|---|---|
| cycle | number | – | Election year, even. Default 2026. |
| district | string | – | House district number (1, "01") or "at-large". Required for house, ignored for senate. |
| office | string | yes | "house" or "senate". |
| special | boolean | – | Senate only: read the special-election primary page (Ohio and Florida in 2026). |
| state | string | yes | US state: postal code ("IA") or full name ("Iowa"). |
No output schema declared.
No examples provided.
How do I install the Us Race Matchups MCP server?
Us Race Matchups runs locally as an npm package, launched with npx -y @pipeworx/mcp-us-race-matchups. 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-us-race-matchups
claude mcp add pipeworx-io-us-race-matchups -- npx -y @pipeworx/mcp-us-race-matchups
What is the Us Race Matchups MCP server?
Us Race Matchups is an MCP server listed in the public MCP registry as io.github.pipeworx-io/us-race-matchups. US race matchups, one call per federal race: who holds the seat, who is running, which of them… This page covers its npm package (@pipeworx/mcp-us-race-matchups).
Is the Us Race Matchups MCP server safe to use?
Us Race Matchups scores 79 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 Us Race Matchups MCP server expose?
Us Race Matchups exposes 2 tools: race_matchup, list_races. Their descriptions and schemas cost roughly 360 tokens of context every time the server is loaded.
Is the Us Race Matchups MCP server still maintained?
Us Race Matchups 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 Us Race Matchups MCP server under?
Us Race Matchups declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.