mcp-archiveorg

Read a page as it was

get_snapshot

Read-onlyIdempotent

Find the Wayback Machine snapshot of any web page closest to a specified date, or retrieve the most recent capture. Get the capture URL and see how far it is from your requested date.

Instructions

Find the Wayback Machine capture of a web page closest to a given date. Give 'at' to ask for a moment in time; leave it out for the most recent capture. The answer always states 'days_from_requested', because the closest capture can be years away from the date asked for: read it before describing what the page said on that date. It also states the address the capture is of, which the Wayback Machine can resolve to a neighbouring form of the one asked about. This finds the capture and links to it. It does not return the page's contents.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`at`	No	Date to aim for, as YYYY-MM-DD or a full ISO 8601 timestamp. Omit for the newest capture.
`url`	Yes	Address to look up, such as 'lemonde.fr' or a full URL.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`notes`	Yes
`snapshot`	Yes
`requested_at`	Yes
`requested_url`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv1.5.0Aug 10, 2026

addedOutput schema / properties / snapshot / properties / address

Added value: +{
+  "description": "The address this capture is of. The Wayback Machine indexes a site under several addresses at once, such as its www form, its https form and a form carrying credentials, so this can differ from the address that was asked about.",
+  "type": "string"
+}

changedOutput schema / properties / snapshot / properties / days_from_requested / description

Previous value: -"Whole days between this capture and the date asked for. Null when no date was given."New value: +"Whole days between this capture and the moment asked for, counted down: a capture taken on the day asked about, when no time was given, is 0. Null when no date was given."

changedOutput schema / properties / snapshot / required

Previous value: -[
-  "captured_at",
-  "url",
-  "status",
-  "days_from_requested"
-]New value: +[
+  "captured_at",
+  "url",
+  "address",
+  "status",
+  "days_from_requested"
+]

Changed1 schema field changedv1.3.0Aug 7, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
First observedv0.1.0Aug 5, 2026

TDQS

A4.6/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Beyond the annotations (readOnlyHint, idempotentHint), the description adds significant behavioral context: the response always includes 'days_from_requested', the URL can resolve to a neighboring form, and it does not return the page's contents. These are not in the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is relatively long but front-loaded with the main purpose. Every sentence adds value, covering purpose, parameter usage, key caveats, and non-behavior, making it appropriately sized for the tool's complexity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with only two parameters, an output schema, and strong annotations, the description is thorough: it explains the main purpose, parameter semantics, important behavioral nuances, and explicitly states what the tool does not do. No significant gaps remain.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema already has 100% parameter coverage, and the description adds extra meaning by explaining how to use 'at' (omit for most recent) and that the URL may resolve to a neighboring form. This goes beyond the schema descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool finds the Wayback Machine capture of a web page closest to a given date, using a specific verb and resource. It also differentiates from sibling tools by noting it links to the capture but does not return page contents.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides clear guidance on when to use it (closest capture to a date) and explains the 'at' parameter's behavior, but does not explicitly name alternative tools for different needs, such as searching inside content.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server