# Us Elections (npm · @pipeworx/mcp-us-elections)

us-elections -- U.S. election results by state, district, county and precinct (fleet #2952…

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

## Components

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

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-us-elections`
- 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-elections).
  - 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**: 60/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 961 tokens (~320/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**: 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 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.

**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 Elections MCP server?

Us Elections runs locally as an npm package, launched with npx -y @pipeworx/mcp-us-elections. 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-elections -- npx -y @pipeworx/mcp-us-elections
```

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

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

## 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 78, 0)

- [functional regression] Security disclosure: unverified → fail

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

First indexed and scored.

## MCP tools (3)

### `election_results` (~593 tokens)

Candidate-level U.S. election results for one state, year and office, at state, county, or precinct granularity. State-level President and Senate cover every state 1976-2024, including 2020 and 2022 (MIT Election Data + Science Lab / MEDSL, Harvard Dataverse, CC0). Official FEC district-by-district U.S. House results (FEC, "Federal Elections" statistical publication, public domain) cover the 2020 and 2022 general elections nationwide -- FEC has not yet published its compiled 2024 edition, and House is not otherwise available nationwide (MEDSL's own House file is guestbook-gated). County-level President/Senate/House results (OpenElections, county/state election-board certified counts) cover the 2024 general election in Georgia, Mississippi, New Mexico, North Dakota, South Dakota, Tennessee, Utah, West Virginia, Colorado, Missouri, Oregon, South Carolina and Kentucky; Pennsylvania and Michigan additionally keep true precinct-level rows. Pass state as a postal code ("PA") or full name ("Pennsylvania"), office as "president", "senate" or "house". For a House race, pass district (e.g. "09") to scope one district; omit it to get every district returned for that state/year. Use county to scope a county/precinct query (e.g. county="Allegheny"); omit it at level="county" to get every county in the state. Returns candidate, party, votes, the race total and the share of the vote, plus source/licence/data_as_of on every row. A state/year/office/level combination with no data returns a loud not-found (reason + available_levels hint), never an empty success.

Input parameters:

- `county` (string): County name to scope a county- or precinct-level query (case-insensitive). Optional.
- `district` (string): House district to scope to one race, e.g. "09" or "9" (normalized to 2 digits). Optional; only meaningful for office="house".
- `level` (string): Granularity: "state", "county", or "precinct". Default "county". FEC official House results are stored at level="state" (FEC publishes one final count per district, with no further sub-division).
- `limit` (number): Max rows, 1-500. Default 50. A truncated response carries truncated:true, total_matching, and a hint for narrowing (county, level="county").
- `office` (string, required): "president", "senate", or "house".
- `offset` (number): Pagination offset. Default 0.
- `state` (string, required): US state, postal code ("PA") or full name ("Pennsylvania").
- `year` (number, required): Election year, e.g. 2024.

### `election_race_summary` (~203 tokens)

Aggregated summary of a U.S. election race -- total votes, each candidate's vote share, the winner and the winning margin -- for one state/year/office. Uses the most aggregated level actually available for that race: a statewide/district number when MEDSL or FEC data covers it (President/Senate nationwide 1976-2024; House nationwide for 2020+2022 by FEC), otherwise summed from whatever county/precinct detail exists (OpenElections). For a district office (House) returns one summary per district. Use for "who won the 2024 PA Senate race and by how much" rather than reading every county row yourself.

Input parameters:

- `office` (string, required): "president", "senate", or "house".
- `state` (string, required): US state, postal code ("PA") or full name ("Pennsylvania").
- `year` (number, required): Election year, e.g. 2024.

### `list_elections` (~111 tokens)

List the state/year/office combinations this pack actually holds data for, and at which levels (state/county/precinct). Pass state to scope the listing to one state; omit it to see full coverage. Use this before election_results or election_race_summary to check whether a given state/year/office exists before querying it, or to discover what is covered.

Input parameters:

- `state` (string): US state, postal code ("PA") or full name ("Pennsylvania"), to scope the listing. Optional.

## Diagnostics

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

## Score history

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

## Common questions

### What is the Us Elections MCP server?

Us Elections is an MCP server listed in the public MCP registry as io.github.pipeworx-io/us-elections. us-elections -- U.S. election results by state, district, county and precinct (fleet #2952… This page covers its npm package (@pipeworx/mcp-us-elections).

### Is the Us Elections MCP server safe to use?

Us Elections scores 78 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 Elections MCP server expose?

Us Elections exposes 3 tools: election_results, election_race_summary, list_elections. Their descriptions and schemas cost roughly 907 tokens of context every time the server is loaded.

### Is the Us Elections MCP server still maintained?

Us Elections 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 Elections MCP server under?

Us Elections 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-us-elections
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-us-elections
- Repository: https://github.com/pipeworx-io/mcp-us-elections
- Website: https://pipeworx.io/packs/us-elections
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-us-elections/pipeworx-mcp-us-elections.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-us-elections/pipeworx-mcp-us-elections.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-us-elections/pipeworx-mcp-us-elections