# Us Race Matchups (npm · @pipeworx/mcp-us-race-matchups)

US race matchups — one call per federal race: who holds the seat, who is running, which of them…

- Trust score: 79/100 (medium)
- Change this week: +15
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `gateway.pipeworx.io`: 76/100, [markdown](https://verifymcp.io/servers/pipeworx-io-us-race-matchups/us-race-matchups-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-us-race-matchups/us-race-matchups-mcp)
- npm · `@pipeworx/mcp-us-race-matchups`: 79/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-us-race-matchups/pipeworx-mcp-us-race-matchups.md), [page](https://verifymcp.io/servers/pipeworx-io-us-race-matchups/pipeworx-mcp-us-race-matchups)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-us-race-matchups`
- Version: `0.2.0`
- 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-us-race-matchups).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 6 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 65/100
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 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.

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

## Install

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

### Claude

```bash
claude mcp add pipeworx-io-us-race-matchups -- npx -y @pipeworx/mcp-us-race-matchups
```

### Cursor

```json
{
  "mcpServers": {
    "pipeworx-io-us-race-matchups": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-us-race-matchups"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pipeworx-io-us-race-matchups": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-us-race-matchups"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add pipeworx-io-us-race-matchups -- npx -y @pipeworx/mcp-us-race-matchups
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add pipeworx-io-us-race-matchups --command npx --arg -y --arg @pipeworx/mcp-us-race-matchups
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-us-race-matchups:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-us-race-matchups"]
```

### Netclaw

```json
{
  "McpServers": {
    "pipeworx-io-us-race-matchups": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pipeworx/mcp-us-race-matchups"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pipeworx-io-us-race-matchups -t stdio -c npx -a -y @pipeworx/mcp-us-race-matchups
```

### Other

```json
{
  "mcpServers": {
    "pipeworx-io-us-race-matchups": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-us-race-matchups"
      ]
    }
  }
}
```

## 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-10-30 (score 79, +15)

- [security improvement] Malware scan: unverified → pass

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

First indexed and scored.

## MCP tools (2)

### `race_matchup` (~227 tokens)

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.

Input parameters:

- `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, required): "house" or "senate".
- `special` (boolean): Senate only: read the special-election primary page (Ohio and Florida in 2026).
- `state` (string, required): US state: postal code ("IA") or full name ("Iowa").

### `list_races` (~133 tokens)

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.

Input parameters:

- `cycle` (number): Election year, even. Default 2026.
- `office` (string): Optional: "house" or "senate" to restrict.
- `state` (string, required): US state: postal code ("IA") or full name.

## Diagnostics

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

## Score history

- 2026-11-05: 79
- 2026-11-04: 79
- 2026-11-03: 79
- 2026-11-02: 79
- 2026-11-01: 79
- 2026-10-31: 79
- 2026-10-30: 79
- 2026-10-29: 64

## Common questions

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

### What did VerifyMCP test on the Us Race Matchups MCP server?

VerifyMCP ran 15 checks on Us Race Matchups, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about Us Race Matchups: Stability. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- npm package: https://www.npmjs.com/package/@pipeworx/mcp-us-race-matchups
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-us-race-matchups
- Repository: https://github.com/pipeworx-io/mcp-us-race-matchups
- Website: https://pipeworx.io/packs/us-race-matchups
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-us-race-matchups/pipeworx-mcp-us-race-matchups.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-us-race-matchups/pipeworx-mcp-us-race-matchups/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/pipeworx-io-us-race-matchups/pipeworx-mcp-us-race-matchups.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-us-race-matchups/pipeworx-mcp-us-race-matchups