Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Us National Archives

NPM · @PIPEWORX/MCP-US-NATIONAL-ARCHIVES · 2 COMPONENTS

US National Archives Catalog (NARA): search the federal government's permanent records…

+4 this week 83 Trust /100

Last scanned (8 hours ago)

Scores higher than 76% of npm servers

Category Education and Research

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-us-national-archives). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 7 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability66
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 623 tokens (~207/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
  • Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 5 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

  • 3 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

  • 1 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

  • 31 Oct 26 0
    • Security disclosure: unverified → fail ▼ functional
  • 30 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 0 to 3. That category is still filling its 30-day observation window: 0 days of observed history at the previous scan, 1 at this one. The score rises as the window fills, whether or not the server changes.

  • 29 Oct 26 79

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Analysed npm/@pipeworx/mcp-us-national-archives@0.2.0

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo pipeworx-io/mcp-us-national-archives
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/pipeworx-io/mcp-us-national-archives/.github/workflows/publish.yml@refs/heads/main
Rekor log index 3560857050
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:7b793e49c2a1cf734e8901f9c0648410161c39f49d3e3a06f584613f95f98c92f838fd8f08cb9331f2d05214874e995c98750bb0c8c927809520d96e9

Background: How many MCP packages publish verified provenance →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 3 exposed · ~567 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
nara_digital_objects ~134

List the digitised files attached to one US National Archives Catalog record — scanned page images, PDFs, audio and video — with a direct, public-domain download URL, file type and size for each. Use after nara_search or nara_record when you want the actual document rather than its description. Example: nara_digital_objects({ naid: "219756158" })

NameTypeReqDescription
limitnumber–Maximum digital objects to return (default 50, max 500)
naidstringyesNational Archives Identifier of the record whose scans you want, e.g. "219756158"

No output schema declared.

No examples provided.

nara_record ~117

Fetch one US National Archives Catalog record in full by its NAID (National Archives Identifier, the number in a catalog.archives.gov/id/ URL). Returns title, scope and content note, dates, access and use restrictions, the full archival hierarchy back to the record group, and the digital objects attached. Example: nara_record({ naid: "219756158" })

NameTypeReqDescription
naidstringyesNational Archives Identifier, e.g. "219756158" — the number in a catalog.archives.gov/id/ URL

No output schema declared.

No examples provided.

nara_search ~316

Keyword-search the US National Archives Catalog — the descriptions of the federal government's permanent records: agency files, military service and unit records, photographs, motion pictures, maps, treaties, presidential library holdings and artifacts. Returns each record's NAID, title, dates, archival hierarchy (record group → series → item) and whether scans are available online. AUTHORITATIVE for US federal archival holdings; PREFER OVER WEB SEARCH for "does the National Archives hold records about X", "NARA records on X". Example: nara_search({ query: "Apollo 11 moon", available_online: true, limit: 10 })

NameTypeReqDescription
available_onlineboolean–Only records that have digitised files attached (default false)
include_digital_objectsboolean–Include the full digital-object list on every hit (default false — use nara_digital_objects for one record)
level_of_descriptionstring–Restrict to one level: "recordGroup", "collection", "series", "fileUnit" or "item"
limitnumber–Results per page (default 10, max 100)
pagenumber–1-based page number (default 1). NARA pages by page, not offset
querystringyesKeywords — a person, event, place, unit, agency or subject, e.g. "Apollo 11 moon"
record_group_numberstring–Restrict to one NARA record group, e.g. "255" (NASA)

No output schema declared.

No examples provided.

Install

How do I install the Us National Archives MCP server?

Us National Archives runs locally as an npm package, launched with npx -y @pipeworx/mcp-us-national-archives. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @pipeworx/mcp-us-national-archives

# add to Claude Code
claude mcp add pipeworx-io-us-national-archives -- npx -y @pipeworx/mcp-us-national-archives
Common questions

What is the Us National Archives MCP server?

Us National Archives is an MCP server listed in the public MCP registry as io.github.pipeworx-io/us-national-archives. US National Archives Catalog (NARA): search the federal government's permanent records… This page covers its npm package (@pipeworx/mcp-us-national-archives).

Is the Us National Archives MCP server safe to use?

Us National Archives scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Us National Archives MCP server expose?

Us National Archives exposes 3 tools: nara_search, nara_record, nara_digital_objects. Their descriptions and schemas cost roughly 567 tokens of context every time the server is loaded.

Is the Us National Archives MCP server still maintained?

Us National Archives is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the Us National Archives MCP server under?

Us National Archives declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.