# Wayback (npm · @pipeworx/mcp-wayback)

Internet Archive Wayback Machine MCP.

- Trust score: 85/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `gateway.pipeworx.io`: 86/100, [markdown](https://verifymcp.io/servers/pipeworx-io-wayback/wayback-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-wayback/wayback-mcp)
- npm · `@pipeworx/mcp-wayback`: 85/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-wayback/pipeworx-mcp-wayback.md), [page](https://verifymcp.io/servers/pipeworx-io-wayback/pipeworx-mcp-wayback)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-wayback`
- Version: `0.2.0`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-wayback).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 7 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 79/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 411 tokens (~137/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Wayback MCP server?

Wayback runs locally as an npm package, launched with npx -y @pipeworx/mcp-wayback. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add pipeworx-io-wayback -- npx -y @pipeworx/mcp-wayback
```

### Cursor

```json
{
  "mcpServers": {
    "pipeworx-io-wayback": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-wayback"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pipeworx-io-wayback": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-wayback"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add pipeworx-io-wayback -- npx -y @pipeworx/mcp-wayback
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pipeworx-io-wayback": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pipeworx/mcp-wayback"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pipeworx-io-wayback --command npx --arg -y --arg @pipeworx/mcp-wayback
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-wayback:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-wayback"]
```

### Netclaw

```json
{
  "McpServers": {
    "pipeworx-io-wayback": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pipeworx/mcp-wayback"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pipeworx-io-wayback -t stdio -c npx -a -y @pipeworx/mcp-wayback
```

### Other

```json
{
  "mcpServers": {
    "pipeworx-io-wayback": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-wayback"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 85, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-03 (score 84, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-31 (score 83, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-30 (score 82, 0)

- [functional regression] Security disclosure: unverified → fail

### 2026-10-29 (score 82)

First indexed and scored.

## MCP tools (3)

### `get_snapshot` (~128 tokens)

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.

Input parameters:

- `timestamp` (string): Optional target date as YYYYMMDD or YYYYMMDDhhmmss. The closest snapshot to this time is returned. Defaults to the latest snapshot.
- `url` (string, required): The page URL to look up, e.g. "example.com" or "https://example.com/page".

### `list_snapshots` (~151 tokens)

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).

Input parameters:

- `from` (string): Optional start of date range as YYYYMMDD.
- `limit` (number): Maximum number of snapshots to return (default 50, max 1000).
- `to` (string): Optional end of date range as YYYYMMDD.
- `url` (string, required): The page URL to list archived snapshots for, e.g. "example.com".

### `get_capture_count` (~80 tokens)

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).

Input parameters:

- `url` (string, required): The page URL to count archived captures for, e.g. "example.com".

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pipeworx-io-wayback/pipeworx-mcp-wayback#diagnostics

## Score history

- 2026-11-05: 85
- 2026-11-04: 84
- 2026-11-03: 84
- 2026-11-02: 83
- 2026-11-01: 83
- 2026-10-31: 83
- 2026-10-30: 82
- 2026-10-29: 82

## Common questions

### What is the Wayback MCP server?

Wayback is an MCP server listed in the public MCP registry as io.github.pipeworx-io/wayback. Internet Archive Wayback Machine MCP. This page covers its npm package (@pipeworx/mcp-wayback).

### Is the Wayback MCP server safe to use?

Wayback scores 85 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Wayback MCP server expose?

Wayback exposes 3 tools: get_snapshot, list_snapshots, get_capture_count. Their descriptions and schemas cost roughly 359 tokens of context every time the server is loaded.

### Is the Wayback MCP server still maintained?

Wayback is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the Wayback MCP server under?

Wayback declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/@pipeworx/mcp-wayback
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-wayback
- Repository: https://github.com/pipeworx-io/mcp-wayback
- Website: https://pipeworx.io/packs/wayback
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-wayback/pipeworx-mcp-wayback.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-wayback/pipeworx-mcp-wayback.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-wayback/pipeworx-mcp-wayback