NARA Catalog
PYPI · NARA-CATALOG-MCP
Genealogical research in the US National Archives Catalog: records, transcriptions, page images.
Available components
Last scanned (21 hours ago)
Scores higher than 76% of PyPI servers
Category Education and Research
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 Security50
- Malware scan not yet available for this package.Unverified
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 1 of 32 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to ianderso/nara-catalog-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 45 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability68
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 4975 tokens (~236/item across 21 items; 21 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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 21 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 22 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (15)
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Malware scan in Supply Chain SecurityMalware scan not yet available for this package.
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 21 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 19 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 18 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 17 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 16 Nov 26 0
- Stability: 0.97 → pass security
- 15 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
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 21 Nov 2026 · Analysed pypi/nara-catalog-mcp@1.1.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 | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | ianderso/nara-catalog-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/ianderso/nara-catalog-mcp/.github/workflows/release.yml@refs/tags/v1.1.0 |
| Rekor log index | 3101216551 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:41568ef1c0268773d3b447009247e6b2525ab84c76fe989f175b6ad38d62ee00 |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | Known build tool | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 32 packages
| Packages resolved | 32 |
|---|---|
| No linked repository | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
aad_get_record ~167
Read one AAD row in full, with a citation in NARA's recommended form. Returns every field with its code's meaning, and the file, series and record group; the citation carries the date the row was retrieved. A NUMIDENT row gives parents' names and birthplace. It is still a transcription, not the record. Cite it as an electronic record, and get the original where one survives: the SS-5 from SSA, a manifest image.
| Name | Type | Req | Description |
|---|---|---|---|
| file_id | string | yes | The AAD file the record is in. |
| record_id | string | yes | The record id an aad_search row gives. |
| refresh | boolean | – | True fetches the record from AAD again instead of the cache, which keeps an answer for 7 days. |
No output schema declared.
No examples provided.
aad_list_series ~181
List the series in NARA's Access to Archival Databases (AAD), with each file's id. AAD holds name-searchable federal databases the Catalog tools cannot reach: the NUMIDENT (Social Security applications, claims and deaths, 1936-2007), WWII Army enlistments, ship passengers 1820-1912 and casualty files among them. aad_search works on one file at a time, and a big series is split into files: the NUMIDENT by entry type and surname range.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | AAD's browse category. 'genealogy' is AAD's own Genealogy/Personal History group and covers the other five. |
| series_id | string | – | One series' id, to list every one of its files. A series with more than 25 files is otherwise listed with a count. |
No output schema declared.
No examples provided.
aad_search ~278
Search one AAD file by `query` over the whole row and by `fields`. A wrong field name is refused with the file's search fields. A coded field (a state, a country) cannot be searched by field: put the meaning in `query`. Returns 50 rows a page, each with its record id. A row is a clerk's transcription or index entry, not the record: names are misspelt and dates wrong in it. No file holds everyone, so no hit is not proof of absence. Record ids change when NARA reloads a file; search again rather than reuse an old one.
| Name | Type | Req | Description |
|---|---|---|---|
| fields | object | – | Field name to value, e.g. {'LAST NAME': 'PRESLEY', 'DATE OF BIRTH (YEAR)': '1930-1935'}. Text matches all the words given, * is a wildcard; a number field takes a value or a range. |
| file_id | string | yes | The AAD file to search, as aad_list_series gives it. |
| page | integer | – | Page of results, 1-based, 50 rows each. |
| query | string | – | Words to find anywhere in a row, code meanings included, e.g. 'BEILIN RUSSIA'. A row must hold all of them. |
No output schema declared.
No examples provided.
api_budget ~66
Report the key's Catalog API spend, this session and this month. A key is capped per month and a long sweep can exhaust it. Live calls are kept in a ledger beside the cache, so the month's figure survives restarts. Cached repeats cost nothing and are not counted.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
browse_children ~150
List a record's immediate children, one level down the hierarchy. The Catalog nests record group, then series, then file unit, then item. Searching finds a node; this walks down from it, which is how you get from a series you trust to the file unit for one person, and how you find out what else sits alongside a file you already have. A record's own ancestors come back from `get_record`.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum children to return (1-100). |
| page | integer | – | Page of results, 1-based. |
| parent_naid | string | yes | NAID of the parent: a record group, collection, series or file unit. |
No output schema declared.
No examples provided.
download_page_image ~283
Download one page of a record so it can actually be read. This is the step that turns a catalogue hit into evidence. The image is written to disk rather than returned inline — a page scan runs to several megabytes. NARA's media URLs are open and need no key, so this costs nothing against your API allowance. One catalogue call resolves the page list; the download itself is not an API call. A pension file can run to sixty pages and the page you need is rarely the first. Use get_extracted_text or get_transcriptions to find which page carries the fact, then fetch it by the object_id they name.
| Name | Type | Req | Description |
|---|---|---|---|
| destination | string | yes | Absolute path of a new file to write, e.g. '/tmp/hall-w17050-p51.jpg'. The directory must already exist, and the file must not: nothing is ever overwritten. |
| naid | string | yes | The record's NAID, e.g. '54765873'. |
| object_id | string | – | The digital object to download, as get_extracted_text, get_transcriptions and get_record_images name it. An alternative to page: pass one or the other. |
| page | – | – | Which page to download, 1-based, in the order get_record_images lists them. Defaults to 1 when object_id is not given. |
No output schema declared.
No examples provided.
get_comments ~146
Read other researchers' comments on a record. Comments often say what a file actually contains, where a related file sits, or that the description is wrong. None of it is verified by NARA: it is correspondence between researchers, useful for finding the next record and never a source in itself.
| Name | Type | Req | Description |
|---|---|---|---|
| max_chars | integer | – | Characters of each comment to return. |
| naid | string | yes | The record's NAID. |
| refresh | boolean | – | True re-reads from the Catalog instead of the cache, spending one call and replacing the cached copy. The cache never expires on its own, so use this when the answer may have changed since you last a… |
No output schema declared.
No examples provided.
get_extracted_text ~277
Read the OCR text NARA machine-extracted from a record's page images. This is a lead, not evidence. OCR was run over scans of handwriting, carbon copies and microfilm: it drops handwritten pages entirely, and it turns one surname into another silently. Use it to find which page matters, then open that page image with `get_record_images` and cite what you saw there -- never cite the OCR text itself. Returns one entry per digital object, in page order, with the text truncated to `max_chars`.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum digital objects to return (1-100). |
| max_chars | integer | – | Characters of text to return per page. 0 returns all of it, which for a long file unit is tens of thousands. |
| naid | string | yes | The record's NAID. |
| object_id | string | – | Limit to one digital object (one scanned page). Omit it to get the text of every page of the record. |
| page | integer | – | Page of results, 1-based. |
| refresh | boolean | – | True re-reads from the Catalog instead of the cache, spending one call and replacing the cached copy. The cache never expires on its own, so use this when the answer may have changed since you last a… |
No output schema declared.
No examples provided.
get_online_availability ~99
List where else this record is available online. NARA records what has been digitised and published elsewhere, including by commercial partners. Use it to resolve a hint from a subscription site back to the archival original: the NAID and the reference unit are what make a citation refindable, and a partner's index entry is not a substitute for the page.
| Name | Type | Req | Description |
|---|---|---|---|
| naid | string | yes | The record's NAID. |
No output schema declared.
No examples provided.
get_partner_digital_objects ~152
List digital object ids a partner has matched to this record. NARA indexes metadata supplied by commercial partners — Ancestry among them — against its own records. A hit tells you the partner holds imagery for this NAID, which is worth knowing when NARA's own pages are not online. An empty list is the common answer and is not an error. It means no partner metadata has been matched, not that no partner holds the record. The ids are pointers into the partner's index, not a citation. Cite the archival record by NAID and reference unit.
| Name | Type | Req | Description |
|---|---|---|---|
| naid | string | yes | The record's NAID, e.g. '54765873'. |
No output schema declared.
No examples provided.
get_record ~127
Read one Catalog record in full, by NAID. Returns the scope and content note, the full hierarchy, the holding reference units, and every page-image URL. Use this once a search has given you a NAID worth pursuing.
| Name | Type | Req | Description |
|---|---|---|---|
| naid | string | yes | The record's NAID, e.g. '54765873'. |
| refresh | boolean | – | True re-reads from the Catalog instead of the cache, spending one call and replacing the cached copy. The cache never expires on its own, so use this when the answer may have changed since you last a… |
No output schema declared.
No examples provided.
get_record_images ~157
List a record's page images in page order, each with its object id. These are the evidence. A catalog description summarises a file; it does not tell you what any individual page says, so read the images before citing anything to this record. The object id is what get_extracted_text and get_transcriptions entries point at; pass it, or the page number, to download_page_image.
| Name | Type | Req | Description |
|---|---|---|---|
| naid | string | yes | The record's NAID. |
| refresh | boolean | – | True re-reads from the Catalog instead of the cache, spending one call and replacing the cached copy. The cache never expires on its own, so use this when the answer may have changed since you last a… |
No output schema declared.
No examples provided.
get_tags ~144
Read the citizen tags on a record. On genealogical records tags are very often the names of the people who appear inside the file -- the widow, the children, the witnesses -- which the title does not carry. A tag is a stranger's reading of the document and is not evidence: follow it to the page image and cite what the image shows.
| Name | Type | Req | Description |
|---|---|---|---|
| naid | string | yes | The record's NAID. |
| refresh | boolean | – | True re-reads from the Catalog instead of the cache, spending one call and replacing the cached copy. The cache never expires on its own, so use this when the answer may have changed since you last a… |
No output schema declared.
No examples provided.
get_transcriptions ~209
Read the citizen transcriptions of a record's pages. Volunteers have transcribed handwritten pension files, service records and letters that OCR cannot touch, which makes this the fastest way into a document in copperplate. It is still a lead, not evidence: a transcription is one stranger's reading, unreviewed, and names are exactly where such a reading goes wrong. Check the page image before citing a name or date you found here, and cite the image. Returns one entry per transcription with its text, its author and the page it belongs to.
| Name | Type | Req | Description |
|---|---|---|---|
| max_chars | integer | – | Characters of each transcription to return. 0 returns the whole thing. |
| naid | string | yes | The record's NAID. |
| refresh | boolean | – | True re-reads from the Catalog instead of the cache, spending one call and replacing the cached copy. The cache never expires on its own, so use this when the answer may have changed since you last a… |
No output schema declared.
No examples provided.
search_by_contribution_text ~298
Search what people wrote on records, and get the records back. This is the difference between searching a catalogue and searching the documents. A pension file titled only with the veteran's name will name his widow, his children and his witnesses in its transcribed text — none of which a title search reaches. Unlike `search_transcriptions` and its siblings, which return the contributions themselves, this filters the main index and returns full record summaries. Use this when you want the record; use those when you want to read what a particular volunteer wrote. A transcription is one volunteer's reading and OCR is a machine's. Both are leads, not evidence — open the page image before citing anything.
| Name | Type | Req | Description |
|---|---|---|---|
| available_online | – | – | Restrict to digitised records only. |
| comment_text | string | – | Words to find in researchers' comments on records. |
| extracted_text | string | – | Words to find in OCR text, including text NARA's partners contributed. |
| limit | integer | – | Maximum records (1-100). |
| page | integer | – | Page of results, 1-based. |
| tag_text | string | – | Words to find in citizen tags, which on genealogical records are usually the names of people appearing in them. |
| transcription_text | string | – | Words to find in volunteers' transcriptions of the handwriting. Accepts AND, OR, NOT, wildcards and "exact phrases". |
No output schema declared.
No examples provided.
search_comments ~130
Find records other researchers have commented on. Useful for picking up where someone else stopped: a comment naming a surname often marks a file that a researcher has already read. Unverified by NARA, so it points at records rather than settling anything.
| Name | Type | Req | Description |
|---|---|---|---|
| contributor | string | – | Restrict to one contributor's screen name. |
| limit | integer | – | Maximum records to return (1-100). |
| naid | string | – | Restrict to comments on one record. |
| page | integer | – | Page of results, 1-based. |
| query | string | – | Words to find in comments. |
No output schema declared.
No examples provided.
search_extracted_text ~146
Find records whose extracted text mentions something. This reaches text contributed by NARA's digitisation partners over the digital objects -- the searchable layer under the scans. It is machine output and is not evidence: it misses handwriting, it mangles names, and a hit means a page probably says this, not that it does. Read the page image before citing anything you find here.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum records to return (1-100). |
| page | integer | – | Page of results, 1-based. |
| query | string | yes | Words to find in extracted text. Accepts AND, OR, NOT, wildcards and "exact phrases". |
No output schema declared.
No examples provided.
search_records ~294
Search the National Archives Catalog for records. Start with `title` and a specific phrase; the Catalog holds tens of millions of descriptions and a broad `query` will bury the useful hit. A result is a lead: check the hierarchy and dates against what you already know before reading the images. Returns the total number of matches and a page of summaries, each with its NAID, hierarchy (each level with its NAID), holding unit and image count. A series, as a hit or in a hierarchy, also names its `creator`, the office that made it: many series share a title, such as one "Homestead Final Certificates" per land office, and the creator tells them apart. Use `search_records_advanced` when you need dates, a record group, an M-number or digitised-only.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum records to return (1-100). |
| page | integer | – | Page of results, 1-based. The API pages rather than offsetting; beyond 10,000 results it needs cursor pagination. |
| query | string | – | Full-text search across the description. Broader and noisier than title; use it when a title search finds nothing. |
| title | string | – | Words to match in the record title, e.g. 'Hall pension' or a person's name. Titles of case files usually carry the name. |
No output schema declared.
No examples provided.
search_records_advanced ~1,139
Search the Catalog with the filters that narrow a common name. Every parameter is optional but at least one is required. The filters that earn their keep for research are the date range, `microform_publication` for an M-number you already cite, `record_group_number` or `ancestor_naid` to stay inside one body of records, and `available_online` when you intend to read pages rather than order copies. Results are the same summaries `search_records` returns. Past 10,000 hits use the `next_search_after` cursor rather than `page`; a common surname passes that boundary easily.
| Name | Type | Req | Description |
|---|---|---|---|
| ancestor_naid | string | – | NAID of an ancestor node: returns only records below it in the hierarchy. Use it to search inside one series. |
| available_online | – | – | True for digitised records only -- those whose pages you can read now rather than order from a reading room. |
| collection_identifier | string | – | Collection identifier, the Presidential-library equivalent of a record group. |
| comments_exist | – | – | True for records carrying researcher comments. |
| congress_number | – | – | Records of one numbered Congress, e.g. 55 for 1897-99. Private relief bills, petitions and claims naming individuals sit in the records of Congress. |
| contributions_exist | – | – | True for records carrying any contribution at all: a transcription, tag or comment. Someone has already worked on them. |
| control_numbers | string | – | Any identifier NARA attaches to a record: accession number, local identifier, microfilm publication, NAID, transfer number or variant control number. For a citation whose kind you cannot name. |
| creators | string | – | The agency or person who created the records, matched against the creator headings. |
| data_source | string | – | 'description' for archival descriptions, 'authority' for authority records (people, organisations, topics). This narrows a search and cannot be one on its own. |
| end_date | string | – | Latest date to include, in the same format as start_date. |
| exact | boolean | – | Match title, local_identifier and microform_publication in full and exactly, instead of by words within them. Use it when a words match returns too much, or you hold the complete title. |
| exact_date | string | – | A single date, YYYY-MM-DD. Cannot be combined with start_date or end_date. |
| geographic_reference | string | – | Place the records are about, matched against geographic subject headings, e.g. 'Franklin County (Pa.)'. |
| include_extracted_text | boolean | – | Fold each hit's OCR text into the response, saving a call per hit: each record gains an extracted_text list with one entry per page that carries text, NARA's own OCR or a partner's, capped at 2000 ch… |
| level_of_description | string | – | One of recordGroup, collection, series, fileUnit, item. A case file is usually a fileUnit; a single page is an item. |
| limit | integer | – | Maximum records to return (1-100). |
| local_identifier | string | – | The archives' own identifier for the record, as printed in finding aids. |
| microform_publication | string | – | Microfilm publication number, e.g. 'M804' for Revolutionary War pension applications or 'T624' for the 1910 census. This is the citation genealogists actually carry. |
| page | integer | – | Page of results, 1-based. Ignored when search_after is given, and unusable past 10,000 results. |
| person_or_org | string | – | A person or organisation named in the description, either as its subject or in a role such as creator. Distinct from `creators`, which is the record's creating body only. |
| query | string | – | Full-text search across the whole description. |
| record_group_number | string | – | Record group number, e.g. '15' for Veterans Affairs. Scopes the search to one agency's records. |
| recurring_day | string | – | Day as DD. Normally used with recurring_month. |
| recurring_month | string | – | Month as MM. With recurring_day, finds records dated to that day in any year -- a birthday across every census. |
| reference_units | string | – | Name of the archive holding the paper, e.g. 'National Archives at St. Louis'. Comma-separate several. |
| search_after | string | – | Cursor for paging past 10,000 results. You MUST pass '*' for the first page, then the 'next_search_after' value from each response. Starting from an ordinary search does not work: without '*' the res… |
| start_date | string | – | Earliest date to include, as YYYY, YYYY-MM or YYYY-MM-DD. Use the same precision as end_date. A surname search is usually only workable once it is bounded to a lifetime. |
| tags_exist | – | – | True for records carrying citizen tags. |
| title | string | – | Words to match in the record title. |
| transcriptions_exist | – | – | True for records someone has transcribed; False for ones nobody has. Transcribed records are searchable by their text. |
| type_of_materials | string | – | Material type, e.g. 'Textual Records', 'Photographs and other Graphic Materials', 'Maps and Charts', 'Moving Images'. |
No output schema declared.
No examples provided.
search_tags ~166
Find records that carry a given citizen tag. Tags are short, so an exact `tag_is` on a surname is often sharper than a title search: a volunteer who read the file tagged the people in it. What comes back is what a stranger thought the document said -- a lead to the page image, and not evidence.
| Name | Type | Req | Description |
|---|---|---|---|
| contributor | string | – | Restrict to one contributor's screen name. |
| limit | integer | – | Maximum records to return (1-100). |
| naid | string | – | Restrict to tags on one record. |
| page | integer | – | Page of results, 1-based. |
| query | string | – | Words to find in citizen tags. |
| tag_is | string | – | Match one exact tag rather than words within tags. |
No output schema declared.
No examples provided.
search_transcriptions ~209
Find records whose citizen transcriptions mention something. This searches the documents rather than the catalogue, which is the difference between finding a pension file titled with the veteran's name and finding the file that names his widow, his children and the neighbours who swore to the marriage. Only transcribed records are reachable this way, so silence here means nobody has transcribed it, not that it does not exist. Returns record summaries. A transcription is a stranger's reading and is not evidence: open the matching page images to see what was written.
| Name | Type | Req | Description |
|---|---|---|---|
| contributor | string | – | Restrict to one contributor's screen name. |
| limit | integer | – | Maximum records to return (1-100). |
| naid | string | – | Restrict to transcriptions of one record. |
| page | integer | – | Page of results, 1-based. |
| query | string | – | Words to find in transcribed text. Accepts AND, OR, NOT, wildcards and "exact phrases". |
No output schema declared.
No examples provided.
How do I install the NARA Catalog MCP server?
NARA Catalog runs locally as a PyPI package, launched with uvx nara-catalog-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · nara-catalog-mcp
claude mcp add ianderso-nara-catalog-mcp -- uvx nara-catalog-mcp
What is the NARA Catalog MCP server?
NARA Catalog is an MCP server listed in the public MCP registry as io.github.ianderso/nara-catalog-mcp. Genealogical research in the US National Archives Catalog: records, transcriptions, page images. This page covers its PyPI package (nara-catalog-mcp).
Is the NARA Catalog MCP server safe to use?
NARA Catalog scores 79 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. 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 NARA Catalog MCP server expose?
NARA Catalog exposes 21 tools: search_records, search_records_advanced, get_record, get_record_images, get_extracted_text, and 16 more. Their descriptions and schemas cost roughly 4,818 tokens of context every time the server is loaded.
Is the NARA Catalog MCP server still maintained?
NARA Catalog is still listed as active in the MCP registry. We last reached this channel on 21 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 NARA Catalog MCP server under?
NARA Catalog declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the NARA Catalog MCP server?
VerifyMCP ran 15 checks on NARA Catalog, covering Known CVEs, Install scripts, Dependency health, Source repository and 11 more. One item could not be completed, a gap on our side rather than a finding about NARA Catalog: Malware scan. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.