Skip to content
GERDA logo

GERDA

Provides German election results at municipality and constituency level, with a dashboard, data downloads and an R package.

Actively maintained

At a glanceswept Oct 23, 2026

≈ 2visits/mo

Little sign of use · estimate, read Oct 13, 2026

For
researchers and analysts working with German election results at municipality and constituency level
Activity
Actively maintainedsite updated 8 days ago
Used for
  • compare party vote shares across German municipalities over time
  • analyse Bundestag results by constituency and federal state
  • study mayoral and Landrat candidates across successive terms
Worth knowingcomputed from what we read · each with its source
How a program reaches itfound, not claimed · read Oct 21, 2026
  • MCP servercom.german-elections/gerdaverified in the MCP registry
  • Stateanswers, 5 toolschecked 2026-10-21
  • Address to connectmcp.german-elections.com/mcp

MCP server details →

This card as JSON, for your agent →

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.

Not it? Say what you need

beta

Three tools from the Atlas for the job you describe, each with what fits and what does not.

From people who use itnot part of the reading

No notes yet. What do you use GERDA for?

Sign in to leave a note
Questions this page answers
  • What is GERDA?

    Provides German election results at municipality and constituency level, with a dashboard, data downloads and an R package.

  • Who is GERDA for?

    researchers and analysts working with German election results at municipality and constituency level

  • Do people use GERDA?

    Little sign of use: ≈ 2 visits/mo · estimate, 2026-10.

  • Is GERDA still maintained?

    Actively maintained: site updated 8 days ago.

How we read a tool

No votes, no reviews, no vendor claims. Every week a crawler reads each tool's own site and a few public registries, and the words on the card are bands over what it read.

  • Use: visits to the site (estimated), installs from npm and PyPI, presence in Chrome's usage report.
  • Activity: the newest release on GitHub, npm or PyPI; the newest dated page on the site; open roles on a public jobs board.
  • Price: the vendor's own pricing page, read with the date. A figure is printed only when it is on that page.
  • The line and the use cases are written by us from the homepage, one tool at a time, and refused when they repeat the vendor's marketing.

How AI assistants read each site — the reading vendors ask us about — is on each tool's own visibility page.

How we read every tool → · By INITE Atlas Desk