SiteCheck Web Intel

Internet Archive Wayback Machine CDX index: archived

search_wayback_cdx

Read-only

Internet Archive Wayback Machine CDX index: archived snapshots of a URL or domain (timestamp, original URL, MIME type, HTTP status, length) with a link to each capture. Public, no key; the index lists captures, not page text. Price: $0.002 in USDC per successful call, paid with x402 (Base, Solana or Arc); failed calls are not charged.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "url": "<url>"
    },
    "name": "search_wayback_cdx"
  }
}

Input Schema

Name	Required	Description	Default
`url`	Yes	URL or domain to look up, e.g. example.com or https://example.com/page
`limit`	No	How many snapshots, 1 to 50 (default 10)

Output Schema

Name	Required	Description	Default
`url`	No
`count`	No
`source`	No
`checkedAt`	No
`snapshots`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, yet the description still adds real behavioral facts: no API key required, x402 payment on Base/Solana/Arc at $0.002 USDC per successful call, and no charge for failed calls. That cost-and-auth disclosure is genuinely decision-relevant for an agent. It does not cover result ordering, deduplication of captures, or rate limits, which keeps it from a top score.

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?

A single, front-loaded passage that leads with what the tool returns before adding the access and pricing details. Every clause carries information; the semicolon-chained pricing sentence is slightly dense but not padded. No redundant restatement of the title beyond the opening clause.

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

Completeness4/5

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

For a two-parameter read-only lookup with an output schema (so return values need not be explained) and annotations covering safety and open-world scope, the description covers purpose, auth, and cost adequately. The only omissions are result ordering/pagination behavior and any rate limits, which are minor for this tool's complexity.

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%, so both `url` (domain or full URL, with examples) and `limit` (1–50, default 10) are already fully documented in the schema. The description adds no syntax, format, or edge-case guidance for either parameter. Baseline 3 is the correct score when the schema does all the work.

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 names a specific verb and resource (the Wayback CDX index of archived snapshots) and enumerates exactly what a record contains: timestamp, original URL, MIME type, HTTP status, length, and a capture link. It also draws a sharp boundary against content-fetching siblings by stating 'the index lists captures, not page text', so an agent can distinguish it from crawler/extractor tools without opening any schema.

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?

Usage context is clear: look up a URL or domain to enumerate historical captures, and use something else if you need page text. The 'not page text' exclusion is the key routing signal. It stops short of naming a concrete alternative sibling (e.g., search_website_content_crawler) by name, so it is strong but not fully explicit.

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

All SiteCheck Web Intel tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?