Skip to main content
Glama
badchars

osint-mcp-server

by badchars

wayback_urls

Retrieve archived URLs from Wayback Machine to discover historical endpoints, hidden paths, and removed content for domain analysis.

Instructions

Search Wayback Machine for archived URLs of a domain. Returns unique URLs with timestamps, status codes, and MIME types. Useful for finding old endpoints, hidden paths, and removed content.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainYesDomain to search archived URLs for
match_typeNoCDX match type (exact, prefix, host, domain)
filterNoCDX filter (e.g. 'statuscode:200', 'mimetype:text/html')
limitNoMaximum URLs to return (default: 1000)

Implementation Reference

  • The handler function that executes the wayback_urls logic by querying the Wayback Machine CDX API.
    export async function waybackUrls(
      domain: string,
      matchType?: string,
      filter?: string,
      limit = 1000,
    ): Promise<WaybackUrlsResult> {
      await limiter.acquire();
    
      const params = new URLSearchParams({
        url: `*.${domain}/*`,
        output: "json",
        fl: "original,timestamp,statuscode,mimetype",
        collapse: "urlkey",
        limit: String(limit),
      });
      if (matchType) params.set("matchType", matchType);
      if (filter) params.set("filter", filter);
    
      const controller = new AbortController();
      const timeout = setTimeout(() => controller.abort(), 30000);
    
      try {
        const res = await fetch(`https://web.archive.org/cdx/search/cdx?${params}`, { signal: controller.signal });
        if (!res.ok) throw new Error(`Wayback CDX returned ${res.status}`);
    
        const data: string[][] = await res.json();
        // First row is header: ["original", "timestamp", "statuscode", "mimetype"]
        const rows = data.slice(1);
    
        const urls: WaybackUrl[] = rows.map((row) => ({
          url: row[0] ?? "",
          timestamp: row[1] ?? "",
          statusCode: row[2] ?? "",
          mimeType: row[3] ?? "",
        }));
    
        return { domain, totalUrls: urls.length, urls };
      } finally {
        clearTimeout(timeout);
      }
    }
  • Type definitions for the result of wayback_urls tool.
    interface WaybackUrl {
      url: string;
      timestamp: string;
      statusCode: string;
      mimeType: string;
    }
    
    interface WaybackUrlsResult {
      domain: string;
      totalUrls: number;
      urls: WaybackUrl[];
    }
  • Registration of the wayback_urls tool in the protocol layer.
    const waybackUrlsTool: ToolDef = {
      name: "wayback_urls",
      description: "Search Wayback Machine for archived URLs of a domain. Returns unique URLs with timestamps, status codes, and MIME types. Useful for finding old endpoints, hidden paths, and removed content.",
      schema: {
        domain: z.string().describe("Domain to search archived URLs for"),
        match_type: z.string().optional().describe("CDX match type (exact, prefix, host, domain)"),
        filter: z.string().optional().describe("CDX filter (e.g. 'statuscode:200', 'mimetype:text/html')"),
        limit: z.number().optional().describe("Maximum URLs to return (default: 1000)"),
      },
      execute: async (args) =>
        json(await waybackUrls(
          args.domain as string,
          args.match_type as string | undefined,
          args.filter as string | undefined,
          args.limit as number | undefined,
        )),
    };
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions what the tool returns ('unique URLs with timestamps, status codes, and MIME types') but lacks details on permissions, rate limits, error handling, or whether it's a read-only operation. For a tool with no annotations, this is insufficient for safe and effective use.

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?

The description is front-loaded with the core purpose, followed by return details and use cases in two concise sentences. Every sentence adds value without redundancy, making it efficient and easy to parse.

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

Completeness3/5

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

Given the tool has no annotations and no output schema, the description provides basic purpose and return format but lacks details on behavioral aspects like error handling or performance constraints. It is minimally adequate for understanding what the tool does but incomplete for reliable agent invocation without further context.

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?

The schema description coverage is 100%, so the schema already documents all parameters thoroughly. The description does not add any additional meaning or examples beyond what the schema provides (e.g., it doesn't explain CDX match types or filter syntax further). This meets the baseline for high schema coverage.

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 specific action ('Search Wayback Machine for archived URLs of a domain') and resource ('domain'), distinguishing it from sibling tools like 'wayback_snapshots' by focusing on URL discovery rather than snapshot retrieval. It provides concrete examples of use cases ('finding old endpoints, hidden paths, and removed content').

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

Usage Guidelines3/5

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

The description implies usage through the phrase 'Useful for finding old endpoints, hidden paths, and removed content,' which gives some context for when to use this tool. However, it does not explicitly state when not to use it or name alternatives (e.g., 'wayback_snapshots' for specific snapshots), leaving room for ambiguity.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/badchars/osint-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server