Skip to main content
Glama
robyroro

osint-mcp-server

by robyroro
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Wayback Machine snapshots

wayback
Read-onlyIdempotent

Look up archived snapshots of a URL or domain to track how a page changed over time or find pages that no longer exist. Returns timestamps and archive links, not page content.

Instructions

Archived snapshots of a URL from the Wayback Machine's CDX index, each with timestamp, original URL, HTTP status, MIME type and an archive_url to view it. Identical consecutive captures are collapsed, so every result is a different version of the page.

Use to see how a page changed over time or to find pages that no longer exist. It doesn't return page content, open archive_url for that. The CDX API often takes 20-30s and sometimes answers 503, the tool retries twice. Cached for 6h.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesURL or domain to look up, e.g. "example.com/about". End it with /* ("example.com/*") to list everything archived under that path.
limitNoHow many snapshots to return, 1-500. Values outside that range are clamped.
year_toNoOnly snapshots up to and including this year.
year_fromNoOnly snapshots from this year on, e.g. 2015. The archive starts in 1996.
newest_firstNotrue returns the most recent snapshots, false the oldest ones.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.2.2
    • addedInput schema / properties / limit / description
      Added value: +"How many snapshots to return, 1-500. Values outside that range are clamped."
    • addedInput schema / properties / newest_first / description
      Added value: +"true returns the most recent snapshots, false the oldest ones."
    • addedInput schema / properties / url / description
      Added value: +"URL or domain to look up, e.g. \"example.com/about\". End it with /* (\"example.com/*\") to list everything archived under that path."
    • addedInput schema / properties / year_from / description
      Added value: +"Only snapshots from this year on, e.g. 2015. The archive starts in 1996."
    • addedInput schema / properties / year_to / description
      Added value: +"Only snapshots up to and including this year."
  2. First observedv0.2.0

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already cover safety (readOnly, idempotent, openWorld, non-destructive), and the description adds genuinely new operational context: identical consecutive captures are collapsed, results are metadata only (open archive_url for content), the upstream CDX API often takes 20-30s, may return 503, and the tool retries twice and caches for 6h. That is exactly the latency/failure behavior an agent needs before calling.

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

Conciseness5/5

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

Three tight paragraphs: what it returns, when to use it and its limits, then operational caveats. Front-loaded with the resource and output shape, and no sentence is filler.

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?

No output schema exists, and the description compensates by listing timestamp, original URL, HTTP status, MIME type, and archive_url, plus the deduplication rule. Combined with latency/retry/cache disclosure, an agent has everything needed to call and interpret it.

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

Parameters3/5

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

Schema description coverage is 100% and each of the five parameters is documented in-schema (including the /* prefix convention and clamping semantics), so the schema carries the burden. The description's enumeration of returned fields is about output shape, not parameter meaning, so it adds little here.

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?

States a specific verb+resource: archived snapshots of a URL from the Wayback Machine's CDX index, and enumerates the fields each result carries. It is trivially distinguishable from the sibling recon/WHOIS/DNS tools, which operate on live infrastructure rather than historical archives.

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?

Gives concrete use cases ('see how a page changed over time', 'find pages that no longer exist') and clarifies the boundary that it returns metadata, not content. It stops short of naming an alternative tool or a when-not-to-use condition, but the use context is unambiguous.

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

Deploy Server

Other Tools