Us National Archives
Server Details
US National Archives Catalog (NARA): search the federal government's permanent records…
Glama couldn't complete the latest health check. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.
If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.
- Status
- Unhealthy
- Uptime
- 0.2% over 20 days
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- pipeworx-io/mcp-us-national-archives
- GitHub Stars
- 0
- Server Listing
- @pipeworx/us-national-archives
TDQS
Scored across 39 tools
The long descriptions work hard to delineate boundaries (e.g. entity_profile vs company_facts vs recent_changes, and the six polymarket_* tools each claim a distinct role), but three near-identical routers (ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded) and several overlapping company/entity tools (entity_profile, compare_entities, resolve_entity, company_facts) create real misselection risk. The server name 'Us National Archives' also clashes with 36 non-NARA tools, adding conceptual confusion.
Names are uniformly snake_case with a mostly predictable verb_noun or noun_action shape (nara_search, discover_tools, resolve_entity, polymarket_edges, validate_claim). A few noun-first names (entity_profile, company_facts, recent_alerts) deviate slightly but remain readable and consistent in style.
39 tools is heavy for any single server, and it is a severe mismatch for a server titled 'Us National Archives' where only 3 tools (nara_search, nara_record, nara_digital_objects) actually serve the stated purpose. The remaining 36 belong to an unrelated broad gateway, so the surface feels like two servers glued together.
The NARA surface covers keyword search, single-record fetch and digital-object listing but has no browse-by-record-group, collection listing, or bulk/export operations — notable gaps for an archival domain. The broader gateway side is comparatively rich (research, entity resolution, financials, markets, memory, subscriptions, feedback), which offsets but does not eliminate the archival gaps.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
1 tool update
- Changed
release_calendar_markets2 fields changed- added
Output schema / properties / empty_reasonAdded value: +{ + "description": "Present ONLY on a zero-release window: \"no_releases_in_window\". The window was queried and nothing is scheduled — this is an answer, not a failure.", + "type": "string" +} - added
Output schema / properties / hintAdded value: +{ + "description": "Present ONLY on a zero-release window: what to change (usually a wider `hours`).", + "type": "string" +}
39 tool updates
- First observed
ai_visibility_check - First observed
ask_pipeworx - First observed
ask_pipeworx_beta - First observed
ask_pipeworx_grounded - First observed
bet_research - First observed
company_facts - First observed
compare_entities - First observed
deep_research - First observed
discover_tools - First observed
entity_profile - First observed
forget - First observed
generate_llms_txt - First observed
kalshi_weather_edge - First observed
list_subscriptions - First observed
nara_digital_objects - First observed
nara_record - First observed
nara_search - First observed
pipeworx_feedback - First observed
pipeworx_trending - First observed
polymarket_arbitrage - First observed
polymarket_edge_tracker - First observed
polymarket_edges - First observed
polymarket_fill_risk - First observed
polymarket_kalshi_spread - First observed
recall - First observed
recent_alerts - First observed
recent_changes - First observed
release_calendar_markets - First observed
remember - First observed
resolution_audit - First observed
resolution_diff - First observed
resolve_entity - First observed
scan_competitor_ai_presence - First observed
scan_dependency - First observed
search_within - First observed
subscribe - First observed
suggest_questions - First observed
unsubscribe - First observed
validate_claim
Related MCP Connectors
Search 14.5M Smithsonian Open Access objects, get CC0 images, find cross-collection connections.
Search LOC digital collections, Chronicling America newspapers (full OCR), and LC Subject Headings.
FJC Judges — the Federal Judicial Center's Biographical Directory of Article III federal judges…
Chronicling America MCP — full-text search of ~150 years of digitized U.S.
Related MCP Servers
- AlicenseAqualityAmaintenanceEnables 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.18575 PyPIMIT
- FlicenseNot gradedqualityNot gradedmaintenanceEnables semantic search across the Arke Institute's extensive archive of NARA records and presidential libraries using natural language queries. Provides access to millions of historical documents, photographs, and records with OCR'd content and complete metadata.-
- AlicenseAqualityBmaintenanceEnables users to resolve historical US land and jurisdiction questions: which county held a given spot on a specific date, where a federal land description (PLSS) falls on the ground, and which National Archives series and file hold the case behind a land patent. All lookups are read-only and can be used alongside archive-search tools to route records requests to the right office.9159 PyPIMIT
- AlicenseAqualityCmaintenanceRead-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.71MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.