Wayback Machine
io.github.Mearman/mcp-wayback-machine
About Wayback Machine
Wayback Machine is an MCP server published by the GitHub account Mearman. MCP server and CLI tool for interacting with the Wayback Machine without API keys
It runs on your own machine: your AI client starts it from the npm package mcp-wayback-machine at version 3.7.1.
It asks for 2 secrets: WAYBACK_ACCESS_KEY and WAYBACK_SECRET_KEY. Give it a key with the least access that still works.
Version 3.7.1 was published on 31 May 2026, and the source code is public, so you can read it before installing.
Written from the registry entry. 9 automated checks on the registry entry and the package code: 7 pass, 0 warn, 0 fail, 2 info. How we check.
What it asks for
| Variable | Required | Secret | Description |
|---|---|---|---|
WAYBACK_ACCESS_KEY | No | Yes | Internet Archive S3 access key for higher SPN2 rate limits. Optional — anonymous mode works without it. |
WAYBACK_SECRET_KEY | No | Yes | Internet Archive S3 secret key for higher SPN2 rate limits. Optional — anonymous mode works without it. |
Checks
| Check | Result | Detail |
|---|---|---|
| Source repository linked | Pass | https://github.com/Mearman/mcp-wayback-machine |
| Version pinned | Pass | Every package has an explicit version |
| Secrets requested | Info | Asks for 2 secrets: WAYBACK_ACCESS_KEY, WAYBACK_SECRET_KEY |
| Known package registry | Pass | All packages come from npm, PyPI, OCI, NuGet or MCPB |
| Namespace ownership | Info | Name verified via GitHub account Mearman |
| Registry text aimed at the AI | Pass | Description and settings contain no hidden characters or instructions to the AI |
| Install scripts | Pass | mcp-wayback-machine@3.7.1 runs nothing at install |
| Code red flags | Pass | Read 41 files in mcp-wayback-machine@3.7.1: no obfuscation, encoded execution, credential reads or data-collection endpoints found |
| Text aimed at the AI | Pass | No hidden characters or instructions to the AI in 41 files, including comments and the README |
Popularity & health: 65 / 100
Worked out from public numbers and our own checks, not from user reviews or ratings. It says how used and how looked-after a server is, not whether it is safe.
11 forks, 5 merged pull requests. Sources: GitHub, npm, PyPI (pypistats.org) and Hacker News (Algolia), fetched 2026-10-31.
What people say
No Hacker News threads link to its source code.
Look further: search Reddit, search Hacker News, read its GitHub issues. These are not reviews we checked.
Facts
| Registry name | io.github.Mearman/mcp-wayback-machine |
|---|---|
| Publisher | GitHub account Mearman |
| How the name is verified | Name verified via GitHub account Mearman. The registry ties the name prefix to that account or domain; it does not check the code. |
| Type | Local: runs on your machine from a package |
| Packages | npm mcp-wayback-machine 3.7.1 (stdio) |
| Version | 3.7.1 |
| Published | |
| Last updated | |
| Source repository | https://github.com/Mearman/mcp-wayback-machine |
| Website | None linked |
| Category | Search & web (assigned by keyword rule, not by hand) |
Related servers in Search & web
- Pricing Time Machine7/7How any SaaS pricing page changed over the years, from the Wayback…
- SandBase3/3Connect MCP clients to 2,000+ AI models without managing provider…
- Vault MCP7/7MCP server for credential isolation — bots use passwords and API…
- Tolgee4/4Your app's translations in Tolgee: search keys, create…
- Scaleway MCP server4/4Scaleway MCP server for interacting with the Scaleway APIs
- my-websearch6/8MyWebSearch - multi-engine web search MCP server, CLI and local…