Skip to main content
Glama
norway-archives-mcp

norway-archives-mcp

by ianderso

Related Servers

Alternatives to norway-archives-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      C
      maintenance
      Enables AI assistants to conduct Swedish genealogy research using the Swedish National Archives' public APIs, from identifying parishes and locating digitised church books to fetching and reading scanned pages with source citations.
      7
      MIT
    • 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
    • A
      license
      B
      quality
      B
      maintenance
      MCP server providing typed tools for Norwegian public data sources, enabling natural language queries to official datasets like SSB, Brønnøysund, MET, Kartverket, Entur, and more, without requiring API keys.
      47
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables users to search and read UK National Archives catalogue records, browse series and pieces, and find WO 97 soldiers' service documents with parsed details via read-only MCP tools.
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      An MCP server to find and fetch Norwegian open government data from data.norge.no. Enables search, metadata retrieval, and data download.
      5
      4
      MIT
    • A
      license
      B
      quality
      B
      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
      135 PyPI
      6
      MIT

    TDQS

    A3.9/5.0

    Scored across 13 tools

    Disambiguation5/5

    Each tool targets a distinct resource/action pair, and the da_/nb_ prefixes cleanly separate the two archive services. Close pairs like da_get_record vs nb_get_page and da_download_page vs nb_download_page are explicitly differentiated, and nb_search vs nb_search_inside is clarified in the descriptions. place_names vs municipalities are also distinct (gazetteer vs historical administrative codes).

    Naming Consistency4/5

    The dominant pattern is consistent service-prefixed verb_noun snake_case (da_search_persons, da_get_source, nb_download_page), which is predictable and readable. Minor deviations are the noun-only place_names and municipalities and the meta-tool cache_status, but these are few and still clear.

    Tool Count5/5

    At 13 tools the set is well-scoped: roughly four tools per archive service plus two geographic lookups and one session utility. Every tool has a clear role in the research workflow, and nothing feels padded or redundant.

    Completeness4/5

    The surface covers a full pipeline from discovery (search persons/sources/items) through inspection (get record/source, list pages, search inside) to evidence (download page, get page, citation data), plus place and municipality lookups. Gaps are minor: there is no unified cross-service search, no tool for browsing holdings beyond place/period queries, and no explicit citation-export operation, but agents can work around these.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues