mcp-registry/com.electionsmcp/electionsmcp · v1.0.0
As of 2026-10-19 12:03 UTC, the Electionsmcp Elections MCP server is up with a Glimind reliability score of 91/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 8 minutes.
Model and map any 2028 U.S. race down to the precinct: scenarios, swing, turnout, and roll-ups.
Claude Code
claude mcp add --transport http electionsmcp-elections-mcp-server https://www.electionsmcp.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"electionsmcp-elections-mcp-server": {
"type": "http",
"url": "https://www.electionsmcp.com/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
5 tool definition(s) exceed ~1,200 tokens each (largest: render_chart, ~2,304).
Move long reference material out of descriptions (link a doc or expose a resource), drop repeated examples, and collapse large enums. Trimming these to ~600 tokens saves ~6,192 tokens every session. How to fix →
48 tools on one server. Tool-selection accuracy drops as the menu grows, and some clients (e.g. Cursor) cap the number of active tools.
Group tools by task into smaller servers or toolsets, and merge near-duplicates behind one tool with a mode parameter. How to fix →
64 parameter(s) across 26 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
1 tool(s) have parameters with no type (no type/enum/anyOf/$ref).
Give every parameter a "type" (or "enum"/"anyOf"). Untyped parameters make models guess — strings for numbers, objects for arrays. How to fix →
Loading this server's tool list costs an agent ~30,478 tokens before any work — more than 95% of MCP servers.
Split rarely-used tools into a separate server or a toolset the client can enable, or expose one "search tools" entry point. Many agents load every connected server's tools into every request. How to fix →
Handshake + tools/list takes ~1,532 ms.
Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.
In the last 30 days: 111 tool(s) removed and 4 schema change(s).
Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 26 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.electionsmcp%2Felectionsmcp/fixes
{
"name": "get_simulation",
"description": "Read the canonical simulation/scenario state, including candidates, race scope, geography overrides, active version identity, provenance, and optional summary or selected dot-path fields.",
"inputSchema": {
"type": "object",
"required": [
"simulation_id"
],
"properties": {
"fields": {
"description": "Optional read shaping: the string \"summary\" → the compact identity card (target <5KB); an array of dot-paths (e.g. [\"id\",\"mode\",\"primary.asof\",\"primary.grain_pref\",\"updated_at\"]) → just those values from the document (plus mode_truth / campaign_identity / provenance as pickable top-level paths). Omit for the full state.",
"type": "string"
},
"simulation_id": {
"type": "string"
},
"workspace_scope": {
"type": "string",
"pattern": "^[uw]-[a-z0-9](?:[a-z0-9-]{0,61})$",
"maxLength": 64,
"minLength": 3,
"description": "Optional workspace for THIS call: use an exact personal/team ID from list_workspaces. Repeat on each call; it does not change the connection default. Must agree with MCP metadata and the effective HTTP workspace selector (header, otherwise connector URL). OAuth connections can only use their granted workspace. Membership and campaign permissions still apply."
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/com.electionsmcp/electionsmcp"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/com.electionsmcp/electionsmcp"}) over MCP.
render_chart ~2,304 tokensrender_view ~2,304 tokensadd_map_comment ~1,892 tokensapply_swing_to_query ~1,467 tokensget_view ~1,225 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fcom.electionsmcp%2Felectionsmcp?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fcom.electionsmcp%2Felectionsmcp?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.electionsmcp%2Felectionsmcp.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.electionsmcp%2Felectionsmcp.svg :target: https://glimind.com/server/mcp-registry%2Fcom.electionsmcp%2Felectionsmcp?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:7f41b8155a1b9a9a…, first seen 2026-10-17, included at leaf 14515 of 26,566. Version history · verify what your client received.
Compare: most reliable communication servers · most reliable data servers · most reliable other servers · most reliable security servers · most reliable calendar servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-19 12:03 UTC, the Electionsmcp Elections MCP server is up with a Glimind reliability score of 91/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 8 minutes.
Electionsmcp Elections MCP server advertises 48 tools, including add_map_comment, apply_swing_to_query, apply_uniform_swing, billing_status, call_tool.
Point your MCP client at this streamable-http endpoint: https://www.electionsmcp.com/mcp
Glimind scanned all 48 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.