Wayback Machine
MCP server and CLI tool for interacting with the Wayback Machine without API keys
Open the source (opens github.com) https://github.com/mearman/mcp-wayback-machine
Before you use it
- Runs on your computer with your permissions. Read what it can do before connecting it to an agent.
- Needs credentials: WAYBACK_ACCESS_KEY, WAYBACK_SECRET_KEY. Use a key with the least access you can.
What it is
MCP servers from io.github.Mearman.
The problem it solves and who it suits haven't been reviewed by InnerVault. The description above is the source's own.
How to get it
npm package (stdio)
mcp-wayback-machine@3.7.1
From the server's entry in the official MCP Registry
Settings it asks for
WAYBACK_ACCESS_KEYsecret · Internet Archive S3 access key for higher SPN2 rate limits. Optional — anonymous mode works without it.WAYBACK_SECRET_KEYsecret · Internet Archive S3 secret key for higher SPN2 rate limits. Optional — anonymous mode works without it.
Related
-
Wayback Machine
MCP serversWayback Machine for agents: closest archived copy of a URL with its text, and full capture history
-
Snapshot history and page text, as one MCP tool through Apify
-
Wayback Machine history of any website: first and last capture, snapshot rows, how old the site is.
-
Wayback
MCP serversInternet Archive Wayback Machine MCP.
@pipeworx/mcp-wayback@0.2.1 -
wayback-mcp
MCP serversMCP server for the Wayback Machine, snapshot history, page availability, and dead site recovery.
wayback-mcp@1.0.0 -
Pricing Time Machine
MCP serversHow any SaaS pricing page changed over the years, from the Wayback Machine. No API keys.
pricing-time-machine-mcp@0.1.0