# Wayback Machine (remote · waybackmcp.com)

Wayback Machine for agents: closest archived copy of a URL with its text, and full capture history

- Trust score: 30/100 (low)
- Change this week: −46
- Registry status: active
- Liveness: degraded
- Owner verified: no
- Last scored: 2026-09-25

> **Degraded**: one or more channels of this server are currently unreachable; their trust score is decaying and will reach 0 if they stay down.

## Components

- remote · `waybackmcp.com`: 30/100 (this document), [markdown](https://verifymcp.io/servers/ux-xd-wayback-machine/waybackmcp.md), [page](https://verifymcp.io/servers/ux-xd-wayback-machine/waybackmcp)

## Channel facts

- Endpoint: `https://waybackmcp.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.1`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, 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-09-25.

- **Endpoint Security**: 0/100
  - TLS not yet verified: we couldn't open a connection to check the certificate.
  - Authorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  - HTTPS check failed: the endpoint is reachable over plaintext HTTP.
  - HSTS not yet verified: we couldn't read the response headers to check for it.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but we couldn't connect to verify it.
- **Schema Quality & AI Usability**: 0/100
  - Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Capabilities**: 0/100
  - Capabilities not yet verified: we couldn't read the endpoint's capabilities.

**Unverified: 5 categories.** Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

## Install

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

Wayback Machine is a hosted endpoint at https://waybackmcp.com/mcp, so there is nothing to install locally. 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 --transport http ux-xd-wayback-machine 'https://waybackmcp.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "ux-xd-wayback-machine": {
      "url": "https://waybackmcp.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ux-xd-wayback-machine": {
      "type": "http",
      "url": "https://waybackmcp.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.ux-xd-wayback-machine]
url = "https://waybackmcp.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ux-xd-wayback-machine": {
      "type": "remote",
      "url": "https://waybackmcp.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ux-xd-wayback-machine --url 'https://waybackmcp.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ux-xd-wayback-machine:
    url: "https://waybackmcp.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "ux-xd-wayback-machine": {
      "Transport": "http",
      "Url": "https://waybackmcp.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add ux-xd-wayback-machine -t streamable-http -u 'https://waybackmcp.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "ux-xd-wayback-machine": {
      "type": "http",
      "url": "https://waybackmcp.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## 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-09-25 (score 30, −16)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-24 (score 46, −15)

The score moved with no change recorded against any check. We would rather say so than guess.

### 2026-09-19 (score 61, −15)

The score moved with no change recorded against any check. We would rather say so than guess.

### 2026-09-17 (score 76, 0)

- [security regression] Endpoint reachability: reachable → unreachable
- [security regression] HSTS header: fail → unverified
- [security regression] Authorization: partial → unverified
- [security regression] Tool safety: pass → unverified
- [security regression] TLS certificate: pass → unverified
- [security regression] Stability: 0.50 → unverified
- [security regression] Transport: pass → fail
- [functional regression] Tool coverage: 100 → unverified
- [functional regression] Capabilities: pass → unverified
- [functional] First check of Schema quality: unverified

### 2026-09-15 (score 76, +1)

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

### 2026-09-13 (score 75, +1)

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

### 2026-09-10 (score 74, +1)

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

### 2026-09-08 (score 73, +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.

## MCP tools (2)

### `archived_copy` (~211 tokens)

Closest archived copy of a URL from the Wayback Machine (Internet Archive), nearest to a date if given. Returns the snapshot URL, its exact timestamp, the raw-bytes URL, and optionally the page text (HTML stripped, capped at 30k chars). Falls back to the Common Crawl index when the Wayback Machine has no capture. Use when a page is dead, changed, or walled and you need what it said.

Input parameters:

- `fetch_text` (boolean): Also fetch the snapshot and return its visible text (default true).
- `task_context` (string, required): One sentence on what the user is ultimately trying to do (the task this call serves). Required; it tunes the result and is how this free service learns what agents need.
- `timestamp` (string): Preferred capture time, 4–14 digits: YYYY, YYYYMMDD or YYYYMMDDhhmmss. Closest capture wins; omit for the latest.
- `url` (string, required): The live URL (scheme optional).

### `capture_history` (~353 tokens)

Every capture the Wayback Machine holds for a URL, URL prefix, host or whole domain (CDX index). Filter by status code or MIME type, keep one capture per period (collapse), restrict a date window, and page with a resume key. Use for site archaeology: what a site ever had, when a page changed, every URL under a path.

Input parameters:

- `collapse` (string): Dedupe key: "urlkey" (one row per URL), or "timestamp:6" for one capture per month, "timestamp:4" per year.
- `filter` (array): CDX field:regex filters, e.g. ["statuscode:200", "!mimetype:warc/revisit"]. Prefix with ! to negate.
- `from` (string): Window start, 4–14 digits (YYYY…).
- `latest_first` (boolean): Return the NEWEST captures instead of the oldest (CDX negative limit). Cannot be combined with resume_key.
- `limit` (integer): Rows to return (default 50, max 1000), oldest first unless latest_first.
- `match_type` (string): How url matches captures. Default exact.
- `resume_key` (string): Continue a previous page: the resume_key that call returned.
- `task_context` (string, required): One sentence on what the user is ultimately trying to do (the task this call serves). Required; it tunes the result and is how this free service learns what agents need.
- `to` (string): Window end, same format.
- `url` (string, required): URL or domain to query, e.g. "example.com/blog/" for prefix work or "example.com" with match_type "domain".

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/ux-xd-wayback-machine/waybackmcp#diagnostics

## Score history

- 2026-09-25: 30
- 2026-09-24: 46
- 2026-09-23: 61
- 2026-09-22: 61
- 2026-09-21: 61
- 2026-09-20: 61
- 2026-09-19: 61
- 2026-09-18: 76
- 2026-09-17: 76
- 2026-09-16: 76
- 2026-09-15: 76
- 2026-09-14: 75
- 2026-09-13: 75
- 2026-09-12: 74
- 2026-09-11: 74
- 2026-09-10: 74
- 2026-09-09: 73
- 2026-09-08: 73
- 2026-09-07: 72
- 2026-09-06: 72
- 2026-09-05: 71
- 2026-09-04: 71
- 2026-09-03: 70
- 2026-09-02: 63
- 2026-09-01: 63

## Common questions

### What is the Wayback Machine MCP server?

Wayback Machine is an MCP server listed in the public MCP registry as io.github.ux-xd/wayback-machine. Wayback Machine for agents: closest archived copy of a URL with its text, and full capture history. This page covers its hosted endpoint (https://waybackmcp.com/mcp).

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

Wayback Machine scores 30 out of 100 on VerifyMCP. 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 Machine MCP server expose?

Wayback Machine exposes 2 tools: archived_copy, capture_history. Their descriptions and schemas cost roughly 564 tokens of context every time the server is loaded.

### Does the Wayback Machine MCP server require authentication?

Its publisher declares no required credentials for Wayback Machine. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

### Is the Wayback Machine MCP server still maintained?

Wayback Machine is still listed in the MCP registry, but we have not been able to reach this channel for several days and its score is decaying. We last reached this channel on 16 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://waybackmcp.com/mcp
- Repository: https://github.com/ux-xd/wayback-machine-mcp
- Website: https://waybackmcp.com/
- Changelog RSS feed: https://verifymcp.io/servers/ux-xd-wayback-machine/waybackmcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/ux-xd-wayback-machine/waybackmcp.json
- HTML version of this page: https://verifymcp.io/servers/ux-xd-wayback-machine/waybackmcp