Skip to content
Back to search

mcp-denmark-polls

Danish opinion polls (Folketing voting intention), read live per request from Wikipedia's pollster-by-pollster tables of Danish general election polls.

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-denmark-polls/badge.svg)](/listings/pipeworx-io--mcp-denmark-polls)

HTML

<a href="/listings/pipeworx-io--mcp-denmark-polls"><img src="/api/listings/pipeworx-io--mcp-denmark-polls/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": {
    "denmark-polls": {
      "url": "https://gateway.pipeworx.io/denmark-polls/mcp"
    }
  }
}

What this endpoint actually serves

`tools/list` at `https://gateway.pipeworx.io/denmark-polls/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 · 137 lines
  1. # @pipeworx/denmark-polls
  2. Danish Folketing voting-intention polls, by party and pollster, from mid-2019 to the latest published poll. Every party share is keyed by the standard Danish party letter (A, B, C, F, I, M, O, V, Æ, Ø, Å, ...).
  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_latest_polls(limit?)` — the most recent polls, newest first, each with fieldwork dates, pollster, sample size, every party share and the sum of those shares (so a caller can see it totals about 100).
  6. - `dk_party_series(party, from?, to?, pollster?)` — one party's share across all pollsters, oldest to newest, one point per poll.
  7. - `dk_polls_by_pollster(pollster, from?, to?, limit?)` — one pollster's polls in a date range. A range with no polls returns an explicit empty answer stating the covered date range and the pollsters available.
  8. - `dk_poll_average(days?, to?)` — a simple average over a window. Method, stated in every response: per pollster, the mean of its polls in the window for each party; then the unweighted mean of those pollster means. No sample-size weighting, no house-effect correction. The window defaults to the 30 days ending at the latest poll.
  9. ## Auth
  10. Keyless.
  11. ## Data sources
  12. - Wikipedia (Wikimedia Foundation), opinion polling for Danish general elections. Text is available under CC BY-SA 4.0; every response carries that attribution in its `source` field. Read live per request and parsed on the spot, with nothing stored by us.
  13. ## Notes
  14. - Coverage is three Wikipedia articles together: polls since the March 2026 general election, polls from the 2022 election to the 2026 election, and polls from the 2019 election to the 2022 election. `covered_range` in each response gives the exact first and latest poll dates.
  15. - Shares are percentages as published; the "Others" column is carried separately (`others`). Polls from the 2022 era list parties that no longer poll (D, K, Q, G); the newest polls do not list them.
  16. - Election-result rows and local-election rows in the source tables are skipped; they are not polls.
  17. - The parser fails loudly. If an expected table, party column or header is missing, or more than 10% of rows cannot be read, the call returns an error naming what changed instead of an empty or partial answer. A fixture test removes a column and expects that error.
  18. - The source is a volunteer-edited encyclopaedia, not a statistical agency. Pollster names are as Wikipedia spells them (for example Voxmeter, Epinion, Verian, Megafon, Norstat, YouGov).
  19. ## Quick Start
  20. Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
  21. ```json
  22. {
  23. "mcpServers": {
  24. "denmark-polls": {
  25. "url": "https://gateway.pipeworx.io/denmark-polls/mcp"
  26. }
  27. }
  28. }
  29. ```
  30. ### What this endpoint actually serves
  31. `tools/list` at `https://gateway.pipeworx.io/denmark-polls/mcp` returns the tools in the table
  32. above **plus the shared Pipeworx meta-tools** — `ask_pipeworx`,
  33. `discover_tools`, `search_within`, `remember`/`recall` and the rest of the
  34. gateway-wide set. So the tool count you see is larger than this table: a
  35. single-pack endpoint currently lists roughly 30 shared tools alongside the
  36. pack's own. The connection's `initialize` response states its exact scope, and
  37. is the authoritative answer for a given day.
  38. This is deliberate, not multiplexing by accident. The meta-tools are what let a
  39. scoped connection answer a question this pack does not cover — via
  40. `ask_pipeworx`, which routes across the whole catalog — without you adding a
  41. second MCP server. There is currently no way to mount a pack endpoint without
  42. them; if the extra schemas cost you more context than the routing is worth,
  43. connect to the full gateway once rather than to several pack endpoints.
  44. Or connect to the full Pipeworx gateway to get every pack's tools listed
  45. directly, instead of just this one's:
  46. ```json
  47. {
  48. "mcpServers": {
  49. "pipeworx": {
  50. "url": "https://gateway.pipeworx.io/mcp"
  51. }
  52. }
  53. }
  54. ```
  55. Both URLs reach the same gateway and the same 2024+ data sources. The
  56. only difference is which pack's tools are listed **directly**; `ask_pipeworx`
  57. reaches all of them from either one.
  58. ## No MCP client? Call it over HTTP
  59. ```bash
  60. curl -X POST https://gateway.pipeworx.io/v1/tools/dk_latest_polls \
  61. -H 'Content-Type: application/json' \
  62. -d '{"limit":3}'
  63. ```
  64. No account needed for the first calls. Inspect any tool: `GET https://gateway.pipeworx.io/v1/tools/dk_latest_polls`. Find one: `POST https://gateway.pipeworx.io/v1/tools/search_packs` with `{"query":"..."}`.
  65. ## Run it from npm
  66. `@pipeworx/mcp-denmark-polls` is a local stdio bridge to the Pipeworx gateway: your MCP client
  67. starts it with `npx`, and it forwards every call to the same
  68. `https://gateway.pipeworx.io/denmark-polls/mcp` endpoint shown above. It needs network access;
  69. there is no offline mode.
  70. ```json
  71. {
  72. "mcpServers": {
  73. "denmark-polls": {
  74. "command": "npx",
  75. "args": ["-y", "@pipeworx/mcp-denmark-polls"]
  76. }
  77. }
  78. }
  79. ```
  80. Without a key it calls anonymously, capped at 50 calls a day. A free account
  81. raises that to 200 a day: get a key at https://pipeworx.io/signup and add
  82. `"env": { "PIPEWORX_API_KEY": "<your key>" }` to the server entry.
  83. The key is sent as a Bearer token, the same way a hosted connection sends it,
  84. so calls are metered and billed exactly as they are there.
  85. It lists **only** this pack's tools by default. Set `PIPEWORX_META_TOOLS=1` to
  86. also list `ask_pipeworx` and the other gateway-wide tools.
  87. Behind an HTTPS proxy: Node's built-in `fetch` does not read `HTTPS_PROXY` by
  88. default. Newer Node releases honour it when `NODE_USE_ENV_PROXY=1` is set; check
  89. your Node version's documentation.
  90. ## Using with ask_pipeworx
  91. Instead of calling tools directly, you can ask questions in plain English —
  92. this works on the pack endpoint above as well as on the full gateway:
  93. ```
  94. ask_pipeworx({ question: "your question about Denmark Polls data" })
  95. ```
  96. The gateway picks the right tool and fills the arguments automatically.
  97. ## More
  98. - [Docs and guides](https://pipeworx.io/docs)
  99. - [pipeworx.io](https://pipeworx.io)
  100. ## License
  101. MIT

Ratings and comments

Sign in to rate this skill.

Sign in

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