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.

io.github.mrfentmen/archive-org-mcp

NPM · ARCHIVE-ORG-MCP

Internet Archive search, item metadata, and Wayback snapshots.

Available components

0 this week 72 Trust /100

Last scanned (17 hours ago)

Scores higher than 44% of npm servers

Category Search and Retrieval

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 Security81
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 30 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
Schema Quality & AI Usability69
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 581 tokens (~58/item across 10 items; 10 tools + 0 resources), lean.Pass
  • 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 Coverage94
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 82% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 10 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
What we tested

Checks we ran (16)

  • Malware scan
  • 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

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 →

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.

  • 21 Nov 26 0
    • Stability: 0.97 → pass security
  • 20 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.

  • 19 Nov 26 −1
    • Stability: pass → 0.93 functional
  • 13 Nov 26 0
    • Stability: 0.97 → pass security
    • Package version: 1.0.1 → 1.0.6 functional
  • 12 Nov 26 0
    • Stability: pass → 0.97 functional
  • 6 Nov 26 0
    • Stability: 0.97 → pass security
  • 5 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.

  • 3 Nov 26 −1
    • Stability: pass → 0.90 functional
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 21 Nov 2026 · Analysed npm/archive-org-mcp@1.0.6

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Vulnerabilities 1 finding
ID CVE Severity Vector Fix available
GHSA-mrhx-c7xc-m3w5 CVE-2023-54404 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 93 packages
Packages resolved 93
Stale 30
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 10 exposed · ~581 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
get_availability ~30

Check whether a page is archived and get its closest snapshot.

NameTypeReqDescription
urlstringyesFull URL

No output schema declared.

No examples provided.

get_item ~32

Get full details + file manifest for an archive.org item.

NameTypeReqDescription
identifierstringyesItem identifier from search_items

No output schema declared.

No examples provided.

get_snapshots ~45

List the Wayback Machine snapshot history for a URL.

NameTypeReqDescription
limitinteger––
urlstringyesFull URL, e.g. 'example.com/page.html'

No output schema declared.

No examples provided.

health_check ~17

Check if the server is running and responsive.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_tools ~16

List all available tools on this server.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

read_snapshot ~66

Read the text content of an archived page, for reading dead sites.

NameTypeReqDescription
maxCharsinteger––
timestampstringyesSnapshot timestamp from get_snapshots, e.g. '20240101120000'
urlstringyesThe original URL that was archived

No output schema declared.

No examples provided.

search_items ~86

Search the Internet Archive — old software, abandoned CD-ROM games, bootleg concert tapes, 78rpm records, dead web pages, and more.

NameTypeReqDescription
limitinteger––
mediatypestring–Restrict to a media type
querystringyesSearch query, e.g. 'Windows 95' or 'sonic hedgehog prototype'

No output schema declared.

No examples provided.

search_profile ~130

What a search term looks like across the Internet Archive rather than eight rows of it: the catalogue total, the media type split, how many items carry no year, the most common years, the collections involved and the download distribution, with the sample size stated. The search_items tool only prints a short list.

NameTypeReqDescription
limitinteger–How many items to read for the profile, 10 to 500.
mediatypestring–Restrict to one media type, e.g. software or audio.
querystringyesSearch terms, e.g. 'Windows 95'

No output schema declared.

No examples provided.

snapshot_timeline ~145

The shape of one URL's archived history rather than a list of it: how many successful snapshots exist in a year range, how many distinct content digests they hold, how many captures just repeat a page already archived, the media types captured, the payload size and captures per year. The get_snapshots tool returns the newest few with no digest, no date range and no totals.

NameTypeReqDescription
frominteger–Earliest year to include.
limitinteger–How many snapshots to read, up to 3000.
tointeger–Latest year to include.
urlstringyesFull URL, e.g. 'example.com/page.html'

No output schema declared.

No examples provided.

version_info ~14

Get server version and metadata.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Install

How do I install the io.github.mrfentmen/archive-org-mcp server?

io.github.mrfentmen/archive-org-mcp runs locally as an npm package, launched with npx -y archive-org-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · archive-org-mcp

# add to Claude Code
claude mcp add mrfentmen-archive-org-mcp -- npx -y archive-org-mcp
Common questions

What is the io.github.mrfentmen/archive-org-mcp server?

io.github.mrfentmen/archive-org-mcp is listed in the public MCP registry as io.github.mrfentmen/archive-org-mcp. Internet Archive search, item metadata, and Wayback snapshots. This page covers its npm package (archive-org-mcp).

Is the io.github.mrfentmen/archive-org-mcp server safe to use?

io.github.mrfentmen/archive-org-mcp scores 72 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 21 November 2026. It declares no install or post-install scripts. 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 io.github.mrfentmen/archive-org-mcp server expose?

io.github.mrfentmen/archive-org-mcp exposes 10 tools: search_items, get_item, get_snapshots, get_availability, read_snapshot, and 5 more. Their descriptions and schemas cost roughly 581 tokens of context every time the server is loaded.

Is the io.github.mrfentmen/archive-org-mcp server still maintained?

io.github.mrfentmen/archive-org-mcp 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 io.github.mrfentmen/archive-org-mcp server under?

io.github.mrfentmen/archive-org-mcp 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 io.github.mrfentmen/archive-org-mcp server?

VerifyMCP ran 16 checks on io.github.mrfentmen/archive-org-mcp, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.