Skip to main content
Glama
harrywesterman

geldersarchief-mcp

by harrywesterman
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to geldersarchief-mcp

No user-submitted related servers found.

    Related Servers

    • Riksarkivet MCP Server

      AI-Riksarkivet
      A
      license
      A
      quality
      A
      maintenance
      Enables 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.
      2
      27
      Apache 2.0

    • genealogy-mcp

      igormel81
      A
      license
      B
      quality
      A
      maintenance
      Family 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.
      31
      431 PyPI
      4
      MIT

    • nl-opendata-mcp

      soulnai
      A
      license
      A
      quality
      C
      maintenance
      Enables accessing and querying Dutch government open datasets from CBS and data.overheid.nl, with tools for searching, filtering, downloading, and analyzing data using CSV, Parquet, DuckDB, or Pandas.
      9
      MIT

    • contentdm-mcp

      ianderso
      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.
      28 PyPI
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.5/5.0

    Scored across 6 tools

    Disambiguation4/5

    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.

    Naming Consistency5/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources