Skip to content
Back to search

mcp-dk-elections

Danish national election results (Statistics Denmark, final-count results, 2009 to the latest election), down to polling-station area.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/pipeworx-io--mcp-dk-elections/badge.svg)](/listings/pipeworx-io--mcp-dk-elections)

HTML

<a href="/listings/pipeworx-io--mcp-dk-elections"><img src="/api/listings/pipeworx-io--mcp-dk-elections/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):

{
  "mcpServers": {
    "dk-elections": {
      "url": "https://gateway.pipeworx.io/dk-elections/mcp"
    }
  }
}

What this endpoint actually serves

`tools/list` at `https://gateway.pipeworx.io/dk-elections/mcp` returns the tools in the table above **plus the shared Pipeworx meta-tools** — `ask_pipeworx`, `discover_tools`, `search_within`, `remember`/`recall` and the rest of the gateway-wide set. So the tool count you see is larger than this table: a single-pack endpoint currently lists roughly 30 shared tools alongside the pack's own. The connection's `initialize` response states its exact scope, and is the authoritative answer for a given day.

This is deliberate, not multiplexing by accident. The meta-tools are what let a scoped connection answer a question this pack does not cover — via `ask_pipeworx`, which routes across the whole catalog — without you adding a second MCP server. There is currently no way to mount a pack endpoint without them; if the extra schemas cost you more context than the routing is worth, connect to the full gateway once rather than to several pack endpoints.

Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:

{
  "mcpServers": {
    "pipeworx": {
      "url": "https://gateway.pipeworx.io/mcp"
    }
  }
}

Both URLs reach the same gateway and the same 2024+ data sources. The only difference is which pack's tools are listed **directly**; `ask_pipeworx` reaches all of them from either one.

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 144 lines
  1. # @pipeworx/dk-elections
  2. Danish national election and referendum results, final count, from the national total down to polling-station area: votes, percent and seats per party, eligible voters, turnout and invalid votes.
  3. Part of [Pipeworx](https://pipeworx.io) — an MCP gateway connecting AI agents to 2024+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.
  4. ## Tools
  5. - `dk_elections_list_elections(type?)` -- the elections covered (date, type, geography levels).
  6. - `dk_elections_results(election?, type?, level?, area?, within?)` -- results of one election at country, landsdel (3), storkreds (10), opstillingskreds (92) or afstemningsomraade (polling-station area, about 1,300-1,600). Omit `area` at the two fine levels to list the units and their ids.
  7. - `dk_elections_party_over_time(party, type?, level?, area?, within?, from_year?)` -- one party across elections, nationally or for a named area (matched across elections by name).
  8. - `dk_elections_turnout(election?, type?, level?, area?, within?)` -- eligible voters, votes cast, turnout and invalid votes, for one election or across all elections of a type.
  9. ## Coverage (stated in every response)
  10. National elections and referendums from 7 June 2009 to the latest held: Folketing elections (2011, 2015, 2019, 2022, 2026), European Parliament elections (2009, 2014, 2019, 2024) and referendums (2009, 2014, 2015, 2022).
  11. Not covered: anything before 2009, municipal and regional elections, Greenland and the Faroe Islands. An election outside the window returns `covered: false` naming the window and the elections available.
  12. ## Auth
  13. Keyless.
  14. ## Data sources
  15. - Statistics Denmark (Danmarks Statistik), national election results, final count.
  16. Live per request; nothing is stored. Results are final once published, so responses are cached for a day. Statistics Denmark also runs the Danish Election Database (1979 onward, municipal elections), which this pack does not read; the Statbank election tables are reachable through `dst-dk`.
  17. ## Notes
  18. - Polling-area ids are assigned per election, so areas are matched across elections by name. Boundaries and polling stations change; a matched area is best effort, and the response says so.
  19. - Party letters were reassigned over time (letter Q, for instance, belonged to different parties). A letter query returns the party that held it in each election, with the name.
  20. - Referendums have yes/no choices in place of parties; seats are null.
  21. - `data_as_of` is the publisher's last correction time for the returned unit.
  22. ## Quick Start
  23. Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
  24. ```json
  25. {
  26. "mcpServers": {
  27. "dk-elections": {
  28. "url": "https://gateway.pipeworx.io/dk-elections/mcp"
  29. }
  30. }
  31. }
  32. ```
  33. ### What this endpoint actually serves
  34. `tools/list` at `https://gateway.pipeworx.io/dk-elections/mcp` returns the tools in the table
  35. above **plus the shared Pipeworx meta-tools** — `ask_pipeworx`,
  36. `discover_tools`, `search_within`, `remember`/`recall` and the rest of the
  37. gateway-wide set. So the tool count you see is larger than this table: a
  38. single-pack endpoint currently lists roughly 30 shared tools alongside the
  39. pack's own. The connection's `initialize` response states its exact scope, and
  40. is the authoritative answer for a given day.
  41. This is deliberate, not multiplexing by accident. The meta-tools are what let a
  42. scoped connection answer a question this pack does not cover — via
  43. `ask_pipeworx`, which routes across the whole catalog — without you adding a
  44. second MCP server. There is currently no way to mount a pack endpoint without
  45. them; if the extra schemas cost you more context than the routing is worth,
  46. connect to the full gateway once rather than to several pack endpoints.
  47. Or connect to the full Pipeworx gateway to get every pack's tools listed
  48. directly, instead of just this one's:
  49. ```json
  50. {
  51. "mcpServers": {
  52. "pipeworx": {
  53. "url": "https://gateway.pipeworx.io/mcp"
  54. }
  55. }
  56. }
  57. ```
  58. Both URLs reach the same gateway and the same 2024+ data sources. The
  59. only difference is which pack's tools are listed **directly**; `ask_pipeworx`
  60. reaches all of them from either one.
  61. ## No MCP client? Call it over HTTP
  62. ```bash
  63. curl -X POST https://gateway.pipeworx.io/v1/tools/dk_elections_list_elections \
  64. -H 'Content-Type: application/json' \
  65. -d '{"type":"folketingsvalg"}'
  66. ```
  67. No account needed for the first calls. Inspect any tool: `GET https://gateway.pipeworx.io/v1/tools/dk_elections_list_elections`. Find one: `POST https://gateway.pipeworx.io/v1/tools/search_packs` with `{"query":"..."}`.
  68. ## Run it from npm
  69. `@pipeworx/mcp-dk-elections` is a local stdio bridge to the Pipeworx gateway: your MCP client
  70. starts it with `npx`, and it forwards every call to the same
  71. `https://gateway.pipeworx.io/dk-elections/mcp` endpoint shown above. It needs network access;
  72. there is no offline mode.
  73. ```json
  74. {
  75. "mcpServers": {
  76. "dk-elections": {
  77. "command": "npx",
  78. "args": ["-y", "@pipeworx/mcp-dk-elections"]
  79. }
  80. }
  81. }
  82. ```
  83. Without a key it calls anonymously, capped at 50 calls a day. A free account
  84. raises that to 200 a day: get a key at https://pipeworx.io/signup and add
  85. `"env": { "PIPEWORX_API_KEY": "<your key>" }` to the server entry.
  86. The key is sent as a Bearer token, the same way a hosted connection sends it,
  87. so calls are metered and billed exactly as they are there.
  88. It lists **only** this pack's tools by default. Set `PIPEWORX_META_TOOLS=1` to
  89. also list `ask_pipeworx` and the other gateway-wide tools.
  90. Behind an HTTPS proxy: Node's built-in `fetch` does not read `HTTPS_PROXY` by
  91. default. Newer Node releases honour it when `NODE_USE_ENV_PROXY=1` is set; check
  92. your Node version's documentation.
  93. ## Using with ask_pipeworx
  94. Instead of calling tools directly, you can ask questions in plain English —
  95. this works on the pack endpoint above as well as on the full gateway:
  96. ```
  97. ask_pipeworx({ question: "your question about Dk Elections data" })
  98. ```
  99. The gateway picks the right tool and fills the arguments automatically.
  100. ## More
  101. - [Docs and guides](https://pipeworx.io/docs)
  102. - [pipeworx.io](https://pipeworx.io)
  103. ## License
  104. MIT

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.