
Connects Claude to the Internet Archive's Wayback Machine, letting you pull historical snapshots of websites programmatically. Part of the Pipeworx gateway ecosystem, which aggregates 725+ data sources behind a single MCP interface. The repo doesn't list specific tools in the table, but you can either call Wayback operations directly or use the ask_pipeworx natural language wrapper to query without knowing exact parameters. Useful when you need to reference how a site looked at a specific point in time, track content changes, or verify claims about historical web presence. Runs as a hosted service at gateway.pipeworx.io, so no local setup required.
Internet Archive Wayback Machine MCP.
Part of Pipeworx — an MCP gateway connecting AI agents to 1476+ live data sources.
| Tool | Description |
|---|---|
get_snapshot | Look up the archived/historical version of a web page in the Internet Archive Wayback Machine. Returns the closest available snapshot (its Wayback URL, timestamp and HTTP status). Pass a timestamp to find the snapshot nearest a specific date; omit it to get the latest archived version. |
list_snapshots | List the captured snapshots of a URL in the Internet Archive Wayback Machine over time, using the CDX index. Each entry includes the capture timestamp, the original URL, HTTP status code, MIME type, content digest and a direct Wayback snapshot URL. Optionally restrict to a date range with from/to (YYYYMMDD). |
get_capture_count | Count how many times a URL has been captured by the Internet Archive Wayback Machine, and find when a URL was first and last archived. Returns the total number of captures plus the earliest and latest capture timestamps (YYYYMMDDhhmmss). |
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"wayback": {
"url": "https://gateway.pipeworx.io/wayback/mcp"
}
}
}
tools/list at https://gateway.pipeworx.io/wayback/mcp returns the tools in the table
above plus the shared Pipeworx meta-tools — ask_pipeworx,
discover_tools, search_within, remember/recall and the rest of the
gateway-wide set. So the tool count you see is larger than this table: a
single-pack endpoint currently lists roughly 30 shared tools alongside the
pack's own. The connection's initialize response states its exact scope, and
is the authoritative answer for a given day.
This is deliberate, not multiplexing by accident. The meta-tools are what let a
scoped connection answer a question this pack does not cover — via
ask_pipeworx, which routes across the whole catalog — without you adding a
second MCP server. There is currently no way to mount a pack endpoint without
them; if the extra schemas cost you more context than the routing is worth,
connect to the full gateway once rather than to several pack endpoints.
Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:
{
"mcpServers": {
"pipeworx": {
"url": "https://gateway.pipeworx.io/mcp"
}
}
}
Both URLs reach the same gateway and the same 1476+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:
ask_pipeworx({ question: "your question about Wayback data" })
The gateway picks the right tool and fills the arguments automatically.
MIT
curl -X POST https://gateway.pipeworx.io/v1/tools/get_snapshot \
-H 'Content-Type: application/json' \
-d '{"url":"https://example.com"}'
No account needed for the first calls. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/get_snapshot. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.