Wayback Machine MCP server
io.github.Mearman/mcp-wayback-machine·v3.7.1·54 starsMCP server and CLI tool for interacting with the Wayback Machine without API keys
54 stars1.6k downloads/wk
Reviews
Write oneNobody has reviewed Wayback Machine yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Wayback Machine tools (8)
write = sends, deletes, buys or postsRead from the package source without running it. The installed server may list more.
check_archive_statusCheck if a URL has been archived by the Wayback Machine and get capture
clear_cacheClear all cached Wayback Machine API responses.
compare_snapshotsCompare two archived snapshots of a URL.
get_archived_urlRetrieve an archived version of a URL from the Wayback Machine.
healthCheck server health and connectivity.
list_screenshotsList available screenshots for a URL from the Wayback Machine.
save_urlSave a URL to the Wayback Machine for archival using the SPN2 API.
search_archivesSearch the Wayback Machine CDX API for archived versions of a URL.
Public scan report
scanner v0.1.9 · 2026-09-27 · same rubric, same numbers if you re-run it
- Code scan39 source files scanned25/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitystatic API keys via environment variables6/15
- Maintenancelast push 48 days ago12/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
How Wayback Machine compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 78/100
- higher than 57% of 48,255 servers
- Tools
- 8
- the typical server has 7
- Tools that change things
- 0%
- typical: 0%. Fewer write tools means less an agent can break
- GitHub stars
- 54
- more than 94% of 28,688 servers
- Downloads a week
- 1,586
- more than 95% of 12,191 servers with a package
What its tools let an agent do: 7 read · 1 create
Install Wayback Machine in Claude Code, Cursor or VS Code
Runs npx -y mcp-wayback-machine on your machine. Read the scan report first; the gateway never runs local packages.
claude mcp add mcp-wayback-machine -- npx -y mcp-wayback-machine
What the publisher says
From the Wayback Machine repository's README, as published. We do not edit it. Read it on GitHub
MCP Wayback Machine Server
MCP server and CLI tool for interacting with the Internet Archive's Wayback Machine. Supports full CDX search, snapshot content retrieval, screenshot listing, snapshot comparison, and optional authentication for higher SPN2 rate limits.
Stack: TypeScript · Node.js 22+ · ES Modules · pnpm · Turbo · Zod
Getting started
Requires Node.js 22+ and pnpm.
pnpm installOptional credentials (anonymous access works, but authenticated requests get higher SPN2 rate limits):
export WAYBACK_ACCESS_KEY="your-access-key"
export WAYBACK_SECRET_KEY="your-secret-key"Obtain credentials at archive.org/account/s3.php.
Build, test, and lint
pnpm validate # typecheck + lint + build + test + untested-files check (the full CI gate)
pnpm check # typecheck + lint + build only
pnpm build # compile TypeScript to dist/
pnpm test # run unit and integration tests
pnpm test:coverage # run tests with coverage (80% line/branch/function threshold)
pnpm lint # lint with ESLint
pnpm lint:fix # auto-fix lint issuesTo run a single test file:
node --test tests/tools/save.unit.test.tsEnd-to-end tests hit the live Wayback Machine API and are opt-in:
pnpm test:e2e # sets WAYBACK_LIVE_TESTS=1 internally via turbopnpm validate is the gate that must pass before a release. prepublishOnly runs it automatically.
Architecture
src/bin.ts is the entry point. It detects whether it is invoked as a CLI or loaded as an MCP server and routes accordingly.
src/
bin.ts — entry point; dispatches to CLI or MCP server
cli.ts — Commander-based CLI implementation
server.ts — MCP server wiring (ListTools + CallTool handlers)
contexts.ts — shared context (rate limiter, cache, credentials)
schemas.ts — Zod schemas for all tool inputs; single source of truth
tools/
save.ts — save_url tool (SPN2 API)
retrieve.ts — get_archived_url tool
search.ts — search_archives tool (CDX API)
status.ts — check_archive_status tool (sparkline API)
screenshots.ts — list_screenshots tool
compare.ts — compare_snapshots tool
cache.ts — clear_cache tool
context.ts — injects shared context into tool handlers
utils/
http.ts — fetch wrapper with rate limiting and Retry-After handling
cache.ts — in-memory + disk cache with per-endpoint TTLs
rate-limit.ts — 15 req/min token bucket
validation.ts — shared Zod validation helpersEach tool module exports a schema (consumed by ListToolsRequestSchema) and an execution function (consumed by CallToolRequestSchema). New tools need both registrations in server.ts.
Caching TTLs are intentional — do not normalise them:
Conventions
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Wayback Machine: common questions
- Is Wayback Machine MCP server safe?
- Mostly: it is graded B (78/100). Read the Wayback Machine safety report
- How do I install Wayback Machine?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does Wayback Machine need an API key?
- Yes. The registry entry asks for
WAYBACK_ACCESS_KEY,WAYBACK_SECRET_KEY. - Is Wayback Machine maintained?
- The last commit was 86 days ago (2026-08-10). The latest release is v3.7.1.
- How does Wayback Machine compare with other MCP servers?
- safety score 78/100 (higher than 57% of 48,255 servers); tools 8 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.