Eldwren: Wayback Machine History — how old a site is, what it looked like

dev.workers.cybermax-tools.cybermaxPublished by cybermax.cybermax-tools.workers.devv1.0.0Updated Oct 29, 2026

Wayback Machine history of any website: first and last capture, snapshot rows, how old the site is.

VerifiedStreamable HTTPWeb executableWeb Search & Scraping

Overview

AI-generated overview

Remote MCP server that queries Wayback Machine history for a website: first and last capture, snapshot rows, and how old the site is.

What you can do
  • Look up the Wayback Machine history of a given website
  • Retrieve the first and last capture dates for a site
  • List snapshot rows from the archive
  • Report how old a site is based on its archived history
When to use it
Useful when you need to check when a site was first archived, how long it has existed, or which snapshots exist, for research, due diligence, or content verification.
Requirements
A remote endpoint at mcp.apify.com over streamable HTTP, with OAuth authentication. An Apify API token is required in the Authorization header as a Bearer token. Runs are billed per history to the Apify account.
Before you install
The Authorization header carries an Apify API token, a secret that should be kept private. Runs are billed per history to your Apify account, so usage costs money. Queries are sent to Apify and the Wayback Machine as third parties.

Installation

In SourceWeft

  1. Open Eldwren: Wayback Machine History — how old a site is, what it looked like in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/dev.workers.cybermax-tools.cybermax%2Fwayback-machine/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "eldwren-wayback-machine-history-how-old": {
      "type": "http",
      "url": "https://mcp.apify.com/?tools=cybermax/wayback-machine&via=mcp-registry"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestOct 29, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.