Wayback
Internet Archive Wayback Machine MCP.
Open the source (opens github.com) https://github.com/pipeworx-io/mcp-wayback
Before you use it
- Runs on someone else's server: what you send it leaves your machine.
- Runs on your computer with your permissions. Read what it can do before connecting it to an agent.
- Needs credentials: PIPEWORX_API_KEY. Use a key with the least access you can.
What it is
MCP servers from io.github.pipeworx-io.
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)
@pipeworx/mcp-wayback@0.2.1
From the server's entry in the official MCP Registry
Remote endpoint (streamable-http)
https://gateway.pipeworx.io/wayback/mcp
From the server's entry in the official MCP Registry
Settings it asks for
PIPEWORX_API_KEYsecret · Optional Pipeworx API key. Without it calls are anonymous and capped daily; a free key raises the cap.
Related
-
wayback-mcp
MCP serversMCP server for the Wayback Machine, snapshot history, page availability, and dead site recovery.
wayback-mcp@1.0.0 -
Wayback Machine
MCP serversMCP server and CLI tool for interacting with the Wayback Machine without API keys
mcp-wayback-machine@3.7.1 -
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.
-
archive-org-mcp
MCP serversInternet Archive search, item metadata, and Wayback snapshots.
archive-org-mcp@1.0.6