Skip to main content
Glama
polish-archives-mcp

polish-archives-mcp

by ianderso

Related Servers

Alternatives to polish-archives-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      Enables 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.
      11
      32 PyPI
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables searching the record images US state archives and state libraries publish on CONTENTdm, across one or several sites at once, and reading items, pages and transcripts with citation details. Also downloads page images through each site's IIIF service, for genealogy and history research.
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables users to search and browse US National Archives Catalog records, read OCR text, citizen transcriptions, tags, and comments, and download page images for genealogical or historical research. It also supports advanced filtered searches and searching within contributed document text while remaining read-only except for saving page images locally.
      18
      27 PyPI
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables searching Dutch archival deeds and records via the Open Archieven API, discovering every scan of a register, and downloading images with full provenance and metadata. It also offers a conservative, locally-OCR-based resolver that suggests candidate scans for a given act without performing automatic matching.
      6
      MIT

    TDQS

    A4/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool targets a clearly distinct object: region codes (regions), session telemetry (cache_status), register inventory (geneteka_coverage), and three separate search backends (geneteka_search, poznan_search, basia_search) plus a scan downloader (swa_scan). The descriptions actively pre-empt the main confusion points, explicitly telling the agent to check geneteka_coverage before trusting a zero from geneteka_search.

    Naming Consistency3/5

    Four tools follow a readable <source>_<action> pattern (geneteka_search, geneteka_coverage, poznan_search, basia_search, swa_scan), but regions and cache_status are bare nouns with no verb, so the convention is mixed. It is still predictable enough that an agent can infer which tools query which archive.

    Tool Count5/5

    Seven tools is well-scoped for a genealogy lookup server: one per data source, plus region decoding, coverage verification, scan retrieval, and cache introspection. No tool appears redundant or padded.

    Completeness4/5

    The surface covers the full research loop: discover regions, verify indexed registers, search three indexes, and download the underlying scan. Minor gaps remain, such as no way to list or browse parishes without already knowing a name, and scan retrieval is limited to Szukaj w Archiwach rather than the other custodians mentioned.

    Maintenance

    ActivityMaintained
    ResponsivenessOutdated data