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
Markdown
[](/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
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
- # @pipeworx/denmark-polls
- 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, Æ, Ø, Å, ...).
- 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.
- ## Tools
- - `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).
- - `dk_party_series(party, from?, to?, pollster?)` — one party's share across all pollsters, oldest to newest, one point per poll.
- - `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.
- - `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.
- ## Auth
- Keyless.
- ## Data sources
- - 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.
- ## Notes
- - 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.
- - 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.
- - Election-result rows and local-election rows in the source tables are skipped; they are not polls.
- - 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.
- - 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).
- ## Quick Start
- Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
- ```json
- {
- "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:
- ```json
- {
- "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.
- ## No MCP client? Call it over HTTP
- ```bash
- curl -X POST https://gateway.pipeworx.io/v1/tools/dk_latest_polls \
- -H 'Content-Type: application/json' \
- -d '{"limit":3}'
- ```
- 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":"..."}`.
- ## Run it from npm
- `@pipeworx/mcp-denmark-polls` is a local stdio bridge to the Pipeworx gateway: your MCP client
- starts it with `npx`, and it forwards every call to the same
- `https://gateway.pipeworx.io/denmark-polls/mcp` endpoint shown above. It needs network access;
- there is no offline mode.
- ```json
- {
- "mcpServers": {
- "denmark-polls": {
- "command": "npx",
- "args": ["-y", "@pipeworx/mcp-denmark-polls"]
- }
- }
- }
- ```
- Without a key it calls anonymously, capped at 50 calls a day. A free account
- raises that to 200 a day: get a key at https://pipeworx.io/signup and add
- `"env": { "PIPEWORX_API_KEY": "<your key>" }` to the server entry.
- The key is sent as a Bearer token, the same way a hosted connection sends it,
- so calls are metered and billed exactly as they are there.
- It lists **only** this pack's tools by default. Set `PIPEWORX_META_TOOLS=1` to
- also list `ask_pipeworx` and the other gateway-wide tools.
- Behind an HTTPS proxy: Node's built-in `fetch` does not read `HTTPS_PROXY` by
- default. Newer Node releases honour it when `NODE_USE_ENV_PROXY=1` is set; check
- your Node version's documentation.
- ## Using with ask_pipeworx
- Instead of calling tools directly, you can ask questions in plain English —
- this works on the pack endpoint above as well as on the full gateway:
- ```
- ask_pipeworx({ question: "your question about Denmark Polls data" })
- ```
- The gateway picks the right tool and fills the arguments automatically.
- ## More
- - [Docs and guides](https://pipeworx.io/docs)
- - [pipeworx.io](https://pipeworx.io)
- ## License
- MIT
Ratings and comments
Sign in to rate this skill.
Sign inFree to use. If it’s helped, pass it on.