Us Elections
NPM · @PIPEWORX/MCP-US-ELECTIONS · 2 COMPONENTS
us-elections -- U.S. election results by state, district, county and precinct (fleet #2952…
Available components
Last scanned (11 hours ago)
Scores higher than 58% 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-elections). 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 Usability60
- AI-judged instruction clarity (good).Pass
- 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. 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 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
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 0
- Security disclosure: unverified → fail ▼ functional
- 29 Oct 26 78
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-elections@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-elections |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-us-elections/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3560847690 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:dc20aa84db7fb8c1044d28121309254a33ed6f06cca10262ba2b5150752cb751c8f021845d0716a9dfdd7270429460e14ee57092e483803eba10592f5 |
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 →
election_race_summary ~203
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.
| Name | Type | Req | Description |
|---|---|---|---|
| office | string | yes | "president", "senate", or "house". |
| state | string | yes | US state, postal code ("PA") or full name ("Pennsylvania"). |
| year | number | yes | Election year, e.g. 2024. |
No output schema declared.
No examples provided.
election_results ~593
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | "president", "senate", or "house". |
| offset | number | – | Pagination offset. Default 0. |
| state | string | yes | US state, postal code ("PA") or full name ("Pennsylvania"). |
| year | number | yes | Election year, e.g. 2024. |
No output schema declared.
No examples provided.
list_elections ~111
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.
| Name | Type | Req | Description |
|---|---|---|---|
| state | string | – | US state, postal code ("PA") or full name ("Pennsylvania"), to scope the listing. Optional. |
No output schema declared.
No examples provided.
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.
npm · @pipeworx/mcp-us-elections
claude mcp add pipeworx-io-us-elections -- npx -y @pipeworx/mcp-us-elections
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.