MCP.Market

GOV Historical Gazetteer MCP server

by ianderso·io.github.ianderso/gov-gazetteer-mcp·v0.1.0

German historical gazetteer GOV: a place's name, Kreis, parish and Standesamt in any year.

A92/100grade A
What users say
No reviews yet
Be the first
Safety scan
A92/100

full report

Adoption
Growing

0 stars97 downloads/wk

Reviews

Write one

Nobody has reviewed GOV Historical Gazetteer yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

GOV Historical Gazetteer tools (6)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • cache_status

    Report this session's requests to GOV, by operation, and cache use. Makes no network call.

  • gov_enclosures

    Every dated enclosure of a place and of each civil place above it, for a place tree.

  • gov_object

    Read one GOV object in full: every name, type and parent, each with its dates.

  • gov_place_at_date

    A place as it was in one year: its name and the civil chain above it to the state.

  • gov_registers

    Which parish and Standesamt kept a place's registers in one year, as GOV records it.

  • gov_search

    Find places in GOV by name: id, names, types, coordinates and current parents.

Public scan report

scanner v0.1.10 · 2026-10-13 · same rubric, same numbers if you re-run it

no findings
  • Code scan13 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 2 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 92/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How GOV Historical Gazetteer compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
92/100
higher than 95% of 48,255 servers
Tools
6
the typical server has 7
Tools that change things
0%
typical: 0%. Fewer write tools means less an agent can break
Downloads a week
97
more than 62% of 12,191 servers with a package

What its tools let an agent do: 6 read

Install GOV Historical Gazetteer in Claude Code, Cursor or VS Code

claude mcp add gov-gazetteer-mcp -- uvx gov-gazetteer-mcp
Add to Cursor

What the publisher says

From the GOV Historical Gazetteer repository's README, as published. We do not edit it. Read it on GitHub

gov-gazetteer-mcp

<!-- mcp-name: io.github.ianderso/gov-gazetteer-mcp -->

An MCP server for GOV, the Geschichtliches Orts-Verzeichnis: the historical gazetteer of the Verein für Computergenealogie (CompGen), with about 1.2 million places, mostly in Germany and the lands that were once German or Prussian. GOV dates everything it records about a place: its names, what kind of place it was, and every place that enclosed it, civil and ecclesiastical.

That makes it the tool for the question a genealogist asks of every German village: in the year of the event, which Kreis, province and state held it, and which parish and Standesamt kept its registers? A village in Posen was Prussian until 1919 and Polish after 1920; a Pomeranian one was German until 1945. A Kreis was renamed, an Amt dissolved, a parish merged. The server reads GOV's public web service and answers for one year at a time, and it gives the dated enclosures a genealogy program needs to build a place tree that is right for every date.

It works the way a careful genealogist does. A gazetteer entry is a finding aid, not evidence. GOV is edited by volunteers: a parish or Standesamt link says which register to look in, and the register's own heading confirms it. Every result credits GOV and CompGen and carries the address of each object's page on GOV, because that page is what gets cited.

Nothing here writes anywhere, and nothing here keeps a family tree. It sits well beside familysearch-mcp, whose place tools resolve a place by date but know no parishes or Standesämter, and us-places-mcp, its counterpart for American counties.

This is an independent project. It is not affiliated with, endorsed by, or supported by the Verein für Computergenealogie.

Tools

The server publishes six tools. All are read-only.

Setup

You need Python 3.11 or later and uv. There is no key to request.

Without cloning. uvx fetches it from PyPI and runs it in one step:

uvx gov-gazetteer-mcp

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

GOV Historical Gazetteer: common questions

Is GOV Historical Gazetteer MCP server safe?
Yes, by our scan: it is graded A (92/100). Read the GOV Historical Gazetteer safety report
How do I install GOV Historical Gazetteer?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does GOV Historical Gazetteer need an API key?
No secret keys are declared. It reads 4 settings from the environment.
Is GOV Historical Gazetteer maintained?
The last commit was 24 days ago (2026-10-11). The latest release is v0.1.0.
How does GOV Historical Gazetteer compare with other MCP servers?
safety score 92/100 (higher than 95% of 48,255 servers); tools 6 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

More from ianderso →