geldersarchief-mcp
Related Servers
Alternatives to geldersarchief-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceEnables querying genealogical records, archive statistics, historical weather, and full-text transcriptions from Open Archives via natural language.4-
- AlicenseBqualityBmaintenanceEnables users to inspect, download, verify, and prepare publicly accessible church book scans, including single pages and page ranges with resume support.71MIT
- AlicenseAqualityBmaintenanceEnables users to search and access digital collections from the Swedish National Archives (Riksarkivet) through multiple APIs. Supports searching records by keywords, exploring collections, and downloading historical images and documents.227Apache 2.0
- AlicenseAqualityCmaintenanceEnables searching and retrieving Dutch case law (uitspraken) via the Rechtspraak Open Data API, including full text and citation graph exploration.666 npm2MIT
- AlicenseBqualityBmaintenanceFamily history research toolkit with 79 archives and databases, name variants, historical calendars, kinship, evidence checks, GEDCOM auditing and archive-request drafts. An MIT-licensed Python MCP server that runs locally without API keys or network requests.31124 PyPI10MIT
- AlicenseAqualityBmaintenanceEnables users to search German archives’ finding aids through the Deutsche Digitale Bibliothek and Archivportal-D, locate civil and church registers across multiple state archives, and download register page images for genealogy and historical research.1160 PyPIMIT
TDQS
Scored across 6 tools
Most tools have distinct purposes (search, get, inspect, resolve, download), but resolve_act_scan and download_act overlap since download_act also resolves, and download_scan vs download_act both download scans. Descriptions provide enough guidance to differentiate them, keeping this a minor issue.
All six tools follow a consistent snake_case verb_noun pattern: get_record, search_acts, inspect_register, resolve_act_scan, download_scan, download_act. The convention is predictable and readable throughout.
Six tools is well-scoped for a focused archival/genealogy resolution workflow. Each tool targets a distinct stage (search, retrieve, inspect, resolve, download) without redundancy bloat.
The surface covers the full discovery-to-download lifecycle: searching acts, fetching records, inspecting registers, resolving acts to scans, and downloading scans/acts. Minor gap in that there's no explicit listing of collections/registers beyond inspect_register, but core workflows are covered.