
Swiss Democracy Mcp
io.github.malkreidePublished by GitHub account malkreidev0.3.0Updated Oct 24, 2026
Swiss popular votes and elections: Swissvotes 1848+, BFS opendata.swiss, SRGSSR Polis 1900+
Overview
Local MCP server giving an assistant read-only access to Swiss federal popular votes since 1848 and elections since 1900, with cantonal, party and municipality-
- What you can do
- Search and list federal popular votes by keyword, date range, legal form, outcome or policy domain, and list voting dates with proposal counts. Retrieve full vote details: official title, parliamentary positions, national result and signatures. Get party recommendations with campaign finance data, and cantonal results with yes share, turnout and acceptance. Query BFS real-time and archived results at national, cantonal or municipality level. With optional SRGSSR Polis credentials, list historical votations and elections since 1900 and fetch municipality-level detail.
- When to use it
- Useful when answering questions about Swiss direct democracy: how a canton voted on a proposal, which parties backed it, historical vote trends, or comparing results across municipalities. Best for research and analysis of aggregate public data rather than live news.
- Requirements
- Runs locally as a Python package via uvx (uv required) over stdio; desktop client only. Network access to swissvotes.ch, opendata.swiss, bfs.admin.ch and api.srgssr.ch. No credentials needed for Swissvotes and BFS tools; the Polis tools need SRGSSR_CONSUMER_KEY and SRGSSR_CONSUMER_SECRET from free registration. Optional MCP_TRANSPORT, MCP_HOST, MCP_PORT, MCP_CORS_ORIGINS and MCP_ALLOWED_HOSTS settings for HTTP mode.
Installation
In SourceWeft
- Open Swiss Democracy Mcp in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
🗳️ swiss-democracy-mcp
[CI] [PyPI] [Python] [License: MIT] [MCP] [Swiss Public Data MCP]
🇨🇭 Part of the Swiss Public Data MCP Portfolio — connecting AI models to Swiss institutional data sources.
🌐 English | 🇩🇪 Deutsche Version
An MCP server providing access to Swiss direct democracy data, covering all federal popular votes since 1848 and elections since 1900.
Demo Query
→ democracy_search_votes(keyword="AHV 21", year_from=2022)
→ democracy_get_cantonal_results(vote_number="551")
→ democracy_get_party_positions(vote_number="551")
→ More use cases by audience →
Data Sources
Tools
Phase 1 — Swissvotes (No Auth Required)
Phase 2 — BFS Real-Time (No Auth Required)
Phase 3 — SRGSSR Polis (API Key Required)
Installation
Claude Desktop (stdio)
Add to claude_desktop_config.json:
The
SRGSSR_*variables are optional. Without them, all Swissvotes and BFS tools remain fully functional. Only the Polis tools require credentials.
Cloud / Render.com (Streamable HTTP)
MCP_HOST defaults to 127.0.0.1 (loopback). Set MCP_HOST=0.0.0.0 only
inside a sandboxed container/cloud deployment — never on a local machine, where
it would expose the server to your whole network.
Architecture
Transport: stdio for Claude Desktop · Streamable HTTP for cloud/Render.com
Auth pattern: No-Auth-First — Swissvotes & BFS work without any credentials
Cache: Swissvotes CSV is loaded once at startup and cached for 24 hours
Configuration
All configuration is via environment variables (see .env.example):
Secrets are held as SecretStr and never logged. See
docs/secret-management.md and
docs/security.md.
MCP Primitives
This server intentionally exposes Tools only (no Resources or Prompts). It is
a Phase-1 read-only data wrapper (see docs/roadmap.md); the
tool surface is small (10 use-case-oriented tools) and every response is
self-contained with source provenance. Resources (e.g. vote://{anr}) are a
candidate for a later phase once the URI scheme stabilises.
MCP Protocol Version
This server speaks two protocol eras over the same endpoint. The client's first request on a connection decides which one applies; a later claim from the other era is refused.
Both revisions are pinned in
tests/test_protocol_version.py and asserted
against the installed SDK, so a Dependabot bump of mcp cannot move either one
silently. Next to them,
tests/test_server_identity.py sends real
requests through the assembled ASGI app: a per-request envelope is answered
with the tool list, and an initialize that offers the modern revision still
gets the handshake ceiling back. The constants say which revisions the SDK
knows; the measurement says which ones this server serves.
Server identity. Under the handshake era serverInfo is named once, in the
initialize reply. The modern era has no handshake and stamps the identity
onto every response instead, as
_meta["io.modelcontextprotocol/serverInfo"]. Implementation.version is a
required schema field that the SDK pre-fills with "" when the constructor
omits it, so an unset version is not a gap but a value on the wire — and one
that a green test suite will not show you. This server passes its distribution
version explicitly; test_server_identity.py measures it on both wires, with a
bare MCPServer as the negative control.
Note that the SDK's LATEST_PROTOCOL_VERSION is an alias for the modern
era, not for the handshake era — pinning against it alone would leave the era
that current clients actually negotiate free to drift.
Update policy. When the gate fails, do not edit the constant blindly: read
the spec changelog between the two revisions, verify the server still behaves,
then move the constant, this section, README.de.md and
CHANGELOG.md together.
Portfolio Synergy
Combine with other servers in the Swiss Public Data MCP portfolio:
- zurich-opendata-mcp — add Zurich city-level statistics to vote analysis
- swiss-statistics-mcp — enrich with BFS demographic data by canton
- srgssr-mcp — link SRF news archive content to specific vote dates
Example multi-server query:
«Vergleiche die Abstimmungsresultate zur AHV-Reform mit der Altersstruktur der Kantone»
→ swiss-democracy-mcp + swiss-statistics-mcp
Safety & Limits
- Read-only: All tools perform HTTP GET requests only — no data is written, modified, or deleted upstream.
- Egress allow-list (SSRF protection): Outbound requests are restricted to a fixed allow-list of trusted hosts (
swissvotes.ch,opendata.swiss,*.bfs.admin.ch,api.srgssr.ch), HTTPS only. Caller-supplied URLs (the BFSresult_url) are additionally resolved and rejected if they point at private, loopback or cloud-metadata IP ranges. - No personal data: Swissvotes, BFS and SRGSSR Polis expose aggregate democratic data (vote results, party positions, cantonal/municipality tallies). No personally identifiable information (PII) is processed or stored by this server.
- Rate limits: Swissvotes is a single CSV downloaded once per 24h and cached in memory. BFS / opendata.swiss and SRGSSR Polis are public APIs without documented rate limits — keep
limitand date ranges conservative. The server enforces a 30s timeout per request. - Data freshness: Real-time BFS results reflect the upstream feed at query time (no local caching). Swissvotes is refreshed every 24h from the Uni Bern mirror.
- Terms of service: Data is subject to the ToS of each source — swissvotes.ch (CC BY 4.0, Uni Bern), opendata.swiss (mostly CC-BY / Open by Default), SRGSSR Polis (free tier, non-commercial use only). Always cite the upstream source in downstream products.
- No guarantees: This server is a community project, not affiliated with the University of Bern, the Federal Statistical Office, or SRG SSR. Availability depends on upstream APIs.
Known Limitations
- Swissvotes coverage: Cantonal-level results are available since 1848; municipality-level results only via SRGSSR Polis (since ~1990s depending on the vote).
- BFS archive: Real-time service covers federal votes since 1981 only.
- Polis tools: Require free registration at developer.srgssr.ch. Non-commercial use only.
- CSV cache: The Swissvotes dataset is ~several MB and is cached in memory for 24 hours. Memory footprint is accordingly higher than API-only servers.
Testing
Where the test data comes from
The fixtures under tests/fixtures/ are recorded from the live sources and
dated. Source, retrieval date, selection rule and SHA-256 for every file:
tests/fixtures/PROVENANCE.md.
The selection rule is the point here. The Swissvotes dataset has 714 rows
and 874 columns, and the recorded rows are chosen by property, not by
position. "The first N rows" would cut away exactly the cells the fixture
exists for: the placeholders 9999 ("no information") and . ("not
applicable"), which appear in 667 of the 714 votes. A fixture without them
would look clean and prove nothing — which is precisely why nobody noticed the
tools were passing them through as if they were values.
The byte-order mark stays in the file too, because the source sets one and the server strips it explicitly. Without it the fixture could not show that it has to.
SRGSSR Polis needs OAuth credentials and is listed under NOT RECORDED in
PROVENANCE.md rather than given a date it never had.
Contributing
See CONTRIBUTING.md (🇩🇪 Deutsch).
Security
See SECURITY.md (🇩🇪 Deutsch) for the security posture and vulnerability reporting.
License
MIT — see LICENSE.
Data licenses:
- Swissvotes: Creative Commons BY 4.0
- BFS / opendata.swiss: Open use
- SRGSSR Polis: Non-commercial use only — see developer.srgssr.ch
Author
Hayal Oezkan · github.com/malkreide
Installation
Run via uv's uvx — no clone or manual install needed. Add to your MCP client config (mcpServers for Claude Desktop, Cursor and Windsurf; use a top-level servers key for VS Code in .vscode/mcp.json):
Source: README.md at commit c0477a9
Tools
0Version history
2- v0.3.0LatestSep 26, 2026
- v0.2.5Sep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts