Install
Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).
claude mcp add --transport http wayback 'https://gateway.pipeworx.io/wayback/mcp'{
"mcpServers": {
"wayback": {
"type": "http",
"url": "https://gateway.pipeworx.io/wayback/mcp"
}
}
}@pipeworx/mcp-waybackclaude mcp add wayback -e 'PIPEWORX_API_KEY=<your pipeworx_api_key>' -- npx -y @pipeworx/mcp-wayback@0.2.0{
"mcpServers": {
"wayback": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-wayback@0.2.0"
],
"env": {
"PIPEWORX_API_KEY": "<your pipeworx_api_key>"
}
}
}
}Environment variables
PIPEWORX_API_KEYsecret Optional Pipeworx API key. Without it calls are anonymous and capped daily; a free key raises the cap.
Documentation
From the project's README on GitHub, refreshed weekly. Links open on GitHub.
Contents
mcp-wayback
Internet Archive Wayback Machine MCP.
Part of Pipeworx — an MCP gateway connecting AI agents to 1743+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.
Tools
| 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). |
Quick Start
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"wayback": {
"url": "https://gateway.pipeworx.io/wayback/mcp"
}
}
}What this endpoint actually serves
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 1743+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
No MCP client? Call it over HTTP
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":"..."}.
Standalone (no gateway account)
This package also runs as a local stdio MCP server — no Pipeworx account, no gateway round-trip:
{
"mcpServers": {
"wayback": {
"command": "npx",
"args": ["-y", "@pipeworx/mcp-wayback"]
}
}
}Or run it directly to confirm it starts:
npx -y @pipeworx/mcp-waybackIt speaks MCP over stdin/stdout and answers initialize/tools/list/tools/call
for only this pack's tools — none of the shared meta-tools the gateway
connection above adds. Same source, same tools, no ask_pipeworx routing.
Using with ask_pipeworx
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.
More
License
MIT
Frequently asked questions
What is Wayback?
Internet Archive Wayback Machine MCP.
How do I install Wayback?
It runs as a remote server. In Claude Code: claude mcp add --transport http wayback 'https://gateway.pipeworx.io/wayback/mcp'. For other clients, paste the JSON configuration from this page into their MCP settings.
Does Wayback need an API key?
Yes. It expects PIPEWORX_API_KEY, which you set in its configuration.
Is Wayback open source?
Yes. Its code is on GitHub under the MIT license.
Who maintains Wayback?
It is published by pipeworx-io. AI.tn lists it but does not maintain or endorse it.
From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.