MCP.Market

Us Elections MCP server

online · 100% uptime
by pipeworx-io·io.github.pipeworx-io/us-elections·v0.2.0

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

B73/100grade B
What users say
No reviews yet
Be the first
Safety scan
B73/100

not scanned yet

Adoption
Growing

0 stars

Reviews

Write one

Nobody has reviewed Us Elections yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Us Elections tools

Tool list not cached yet. `describe` through the gateway fetches it live.

Not scanned yet. New listings are scanned within a day or two of arriving.

How Us Elections compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
73/100
higher than 39% of 48,255 servers
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
46 ms
faster than 93% of 30,031 servers

Release history: 3 versions in the registry since 2026-10-13, latest 2026-10-29, typically one every 15 days.

Install Us Elections in Claude Code, Cursor or VS Code

claude mcp add --transport http us-elections https://gateway.pipeworx.io/us-elections/mcp
Add to Cursor

What the publisher says

From the Us Elections repository's README, as published. We do not edit it. Read it on GitHub

@pipeworx/us-elections

U.S. election results — candidate-level vote counts for President and U.S. Senate by state (every state, 1976-2024), plus county- and precinct-level detail for President, Senate and U.S. House in the 2024 general election for Pennsylvania, Michigan and Georgia. Fleet #2952.

Part of Pipeworx — an MCP gateway connecting AI agents to 1779+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.

Tools

— candidate-level results for one state/year/office at state, county, or precinct granularity (default county). Pass county to scope a county- or precinct-level query to one county. Each row carries candidate, party, votes, the race total and vote share, plus source, sourceurl, license and dataas_of. A combination with no data returns a loud not-found naming which levels actually exist, never an empty success.

  • election_results(state, year, office, level?, county?, limit?, offset?)

share, winner and margin for a race, computed from the most aggregated level actually available (statewide when covered, otherwise summed from whatever county/precinct detail exists). A district office (House) returns one summary per district.

  • electionracesummary(state, year, office) — aggregated totals, vote

actually holds, and at which levels. Call this first to check coverage before querying a specific race.

  • list_elections(state?) — the state/year/office combinations this pack

State accepts a postal code ("PA") or full name ("Pennsylvania"), case-insensitive. Office accepts "president", "senate", or "house" (and common synonyms like "POTUS", "U.S. Senate").

Auth

Keyless. The tools answer only through the Pipeworx gateway, which holds the data; a standalone npm install has no data to read, and every tool throws a clear "not bound in this runtime" error there instead of returning an empty list.

Data sources

U.S. President returns, 1976-2024.

  • MIT Election Data + Science Lab (MEDSL), Harvard Dataverse — state-level

U.S. Senate returns, 1976-2024. Licence: CC0 1.0 (public domain dedication) for both.

  • MIT Election Data + Science Lab (MEDSL), Harvard Dataverse — state-level

for Pennsylvania, Michigan and Georgia. Licence: no separate data-reuse licence is published on the data repositories; the project's parser codebase (openelections-core) is MIT, and the underlying figures are county/state election-board certified vote counts — public election records. No terms were found forbidding reuse, so this pack builds a copy per Pipeworx's rule for a source that only publishes bulk files: build it, and flag it, when the terms are silent.

  • OpenElections — county- and precinct-level 2024 general-election returns

Known gaps — read before extending this pack

MEDSL's own county-level and House files are gated, not just unbuilt. MEDSL's canonical "County Presidential Election Returns 2000-2024" dataset and its "U.S. House 1976-2024" dataset (both on Harvard Dataverse) are gated behind a mandatory guestbook (name, email, institution and position all required) with no documented API bypass — every file-download call for those two datasets returns "You may not download this file without the required Guestbook response for guestbookID 458", for anonymous and authenticated access alike. This is an access wall, not a robots.txt question, so the loader does not attempt to automate past it (CLAUDE.md "Authentication or payment walls" is the applicable carve-out, even though no persistent account is created — a mandatory identity-collection form blocking machine access is the same shape). If a person fills the form by hand and hands the resulting file to this pack, scripts/us-elections/load-data.mjs can load it directly — the schema already has the right shape (level = 'county', office = 'HOUSE').

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Us Elections: common questions

Is Us Elections MCP server safe?
Mostly: it is graded B (73/100). Read the Us Elections safety report
How do I install Us Elections?
It runs remotely at gateway.pipeworx.io. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does Us Elections need an API key?
Yes. The registry entry asks for PIPEWORX_API_KEY.
Is Us Elections maintained?
The last commit was 22 days ago (2026-10-13). The latest release is v0.2.0.
Is Us Elections up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
How does Us Elections compare with other MCP servers?
safety score 73/100 (higher than 39% of 48,255 servers); uptime 100% (of our recent checks; the typical remote server answers 100%); response time 46 ms (faster than 93% of 30,031 servers). Full comparison.

More from pipeworx-io →