Skip to main content
Glama
ianderso

nara-catalog-mcp

by ianderso
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to nara-catalog-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
      24
      Apache 2.0

    • nara-mcp-server

      GeorgeTownSabatical
      A
      license
      A
      quality
      C
      maintenance
      Read-only Model Context Protocol server for the US National Archives Catalog API, enabling search and retrieval of archival records, child records, extracted text, comments, and tags.
      7
      1
      MIT

    • fold3-com-mcp

      ball2jh
      A
      license
      A
      quality
      C
      maintenance
      Enables searching and reading Fold3 military records, including files, index records, memorials, and collection browsing, along with full-resolution page image downloads, using an existing Ancestry session in read-only mode.
      6
      MIT

    • sept11-mcp

      pranava0x0
      F
      license
      A
      quality
      C
      maintenance
      Enables users to search catalog metadata, read captured pages, verify quotations, and detect changes in accepted catalog captures for New York City's September 11th Document Portal using local, read-only snapshots.
      10
      -
    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

    A4/5.0

    Scored across 18 tools

    Disambiguation4/5

    There is a large cluster of search tools (search_records, search_records_advanced, search_transcriptions, search_tags, search_extracted_text, search_comments, search_by_contribution_text) plus mirroring getters, which could cause misselection. However, the descriptions carefully draw the line — notably search_by_contribution_text returning records vs. the contribution-returning siblings — so an attentive agent can tell them apart.

    Naming Consistency4/5

    Nearly everything follows a clean snake_case verb_noun pattern (get_record, search_records, browse_children, download_page_image). The lone outlier is api_budget, a bare noun that breaks the convention, but it is a minor deviation.

    Tool Count4/5

    18 tools is on the heavier side but each maps to a distinct resource or surface (records, images, OCR, transcriptions, tags, comments, partner objects, hierarchy, budget), so most earn their place. It sits just past the comfortable 3-15 range rather than being bloated.

    Completeness4/5

    The surface covers search, full-record read, page-image listing/download, machine and human text, citizen tags/comments, partner objects, hierarchy descent, and budget tracking. Only minor gaps exist, such as no explicit ancestor-walk or citation-export tool, though ancestors are folded into get_record.

    Maintenance

    ActivityNo data
    ResponsivenessNo issues

    Resources