Internet Archive Wayback MCP Server for LlamaIndex 10 tools — connect in under 2 minutes
LlamaIndex specializes in data-aware AI agents that connect LLMs to structured and unstructured sources. Add Internet Archive Wayback as an MCP tool provider through Vinkius and your agents can query, analyze, and act on live data alongside your existing indexes.
ASK AI ABOUT THIS MCP SERVER
Vinkius supports streamable HTTP and SSE.
import asyncio
from llama_index.tools.mcp import BasicMCPClient, McpToolSpec
from llama_index.core.agent.workflow import FunctionAgent
from llama_index.llms.openai import OpenAI
async def main():
# Your Vinkius token. get it at cloud.vinkius.com
mcp_client = BasicMCPClient("https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp")
mcp_tool_spec = McpToolSpec(client=mcp_client)
tools = await mcp_tool_spec.to_tool_list_async()
agent = FunctionAgent(
tools=tools,
llm=OpenAI(model="gpt-4o"),
system_prompt=(
"You are an assistant with access to Internet Archive Wayback. "
"You have 10 tools available."
),
)
response = await agent.run(
"What tools are available in Internet Archive Wayback?"
)
print(response)
asyncio.run(main())
* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
About Internet Archive Wayback MCP Server
Connect the Internet Archive Wayback Machine to any AI agent and access the world's largest web archive — 800B+ archived web pages spanning 25+ years of internet history.
LlamaIndex agents combine Internet Archive Wayback tool responses with indexed documents for comprehensive, grounded answers. Connect 10 tools through Vinkius and query live data alongside vector stores and SQL databases in a single turn. ideal for hybrid search, data enrichment, and analytical workflows.
What you can do
- URL Availability Check — Verify if any URL has been archived and find the latest snapshot
- Full CDX Capture History — Get detailed capture history with timestamps, status codes, MIME types, and sizes
- Filter by Year — Find all captures from a specific year for temporal analysis
- Filter by HTTP Status — Find captures that returned specific status codes (200, 404, 301, 500)
- Filter by MIME Type — Find captures of specific resource types (HTML, images, PDFs, CSS)
- First Capture — Find when a URL was first archived
- Latest Capture — Find the most recent archived version of a URL
- Capture Count — Get the total number of times a URL has been archived
- Deduplicated Captures — Get unique captures collapsed by URL key
- Subdomain Discovery — Find all archived subdomains of a domain
The Internet Archive Wayback MCP Server exposes 10 tools through the Vinkius. Connect it to LlamaIndex in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.
How to Connect Internet Archive Wayback to LlamaIndex via MCP
Follow these steps to integrate the Internet Archive Wayback MCP Server with LlamaIndex.
Install dependencies
Run pip install llama-index-tools-mcp llama-index-llms-openai
Replace the token
Replace [YOUR_TOKEN_HERE] with your Vinkius token
Run the agent
Save to agent.py and run: python agent.py
Explore tools
The agent discovers 10 tools from Internet Archive Wayback
Why Use LlamaIndex with the Internet Archive Wayback MCP Server
LlamaIndex provides unique advantages when paired with Internet Archive Wayback through the Model Context Protocol.
Data-first architecture: LlamaIndex agents combine Internet Archive Wayback tool responses with indexed documents for comprehensive, grounded answers
Query pipeline framework lets you chain Internet Archive Wayback tool calls with transformations, filters, and re-rankers in a typed pipeline
Multi-source reasoning: agents can query Internet Archive Wayback, a vector store, and a SQL database in a single turn and synthesize results
Observability integrations show exactly what Internet Archive Wayback tools were called, what data was returned, and how it influenced the final answer
Internet Archive Wayback + LlamaIndex Use Cases
Practical scenarios where LlamaIndex combined with the Internet Archive Wayback MCP Server delivers measurable value.
Hybrid search: combine Internet Archive Wayback real-time data with embedded document indexes for answers that are both current and comprehensive
Data enrichment: query Internet Archive Wayback to augment indexed data with live information before generating user-facing responses
Knowledge base agents: build agents that maintain and update knowledge bases by periodically querying Internet Archive Wayback for fresh data
Analytical workflows: chain Internet Archive Wayback queries with LlamaIndex's data connectors to build multi-source analytical reports
Internet Archive Wayback MCP Tools for LlamaIndex (10)
These 10 tools become available when you connect Internet Archive Wayback to LlamaIndex via MCP:
check_availability
Returns the closest (most recent) snapshot timestamp and availability status. Use this to verify if a page is preserved and find its latest archived version. Check if a URL has been archived by the Wayback Machine
get_capture_count
Use this to measure how frequently a page has been preserved over time. Get the total number of captures for a URL
get_captures_by_mime_type
Common types: "text/html" (web pages), "image/jpeg" (JPEG images), "application/pdf" (PDFs), "text/css" (stylesheets). Use this to find specific resource types in the archive. Get captures filtered by MIME type
get_captures_by_status
Common codes: "200" (OK), "404" (Not Found), "301" (Redirect), "500" (Server Error). Use this to analyze site availability patterns over time. Get captures filtered by HTTP status code
get_captures_by_year
Use this to analyze archival frequency or find snapshots from a particular year. Year should be 4-digit format (e.g., "2020"). Get captures filtered by a specific year
get_captures_collapsed
This shows unique page captures without redundant entries for the same page. Use this for a cleaner view of archived content. Get captures deduplicated by URL key
get_cdx_captures
Each capture includes timestamp, original URL, MIME type, HTTP status code, and file size. Use this for comprehensive archival analysis. Optional limit parameter controls maximum results. Get detailed capture history from the CDX server
get_first_capture
Includes the timestamp, status code, and original URL. Use this to find when a page was first preserved. Get the first (earliest) capture of a URL
get_latest_capture
Includes timestamp, status code, and URL. Use this to find the newest preserved version of a page. Get the most recent capture of a URL
get_subdomain_captures
g., *.example.com). Use this to discover the archival footprint of an entire domain, finding all subdomains that have been preserved. Get captures for all subdomains of a domain
Example Prompts for Internet Archive Wayback in LlamaIndex
Ready-to-use prompts you can give your LlamaIndex agent to start working with Internet Archive Wayback immediately.
"Check if https://example.com has been archived."
"Show me all captures of https://example.com from 2020."
"Find all subdomains of archive.org that have been captured."
Troubleshooting Internet Archive Wayback MCP Server with LlamaIndex
Common issues when connecting Internet Archive Wayback to LlamaIndex through the Vinkius, and how to resolve them.
BasicMCPClient not found
pip install llama-index-tools-mcpInternet Archive Wayback + LlamaIndex FAQ
Common questions about integrating Internet Archive Wayback MCP Server with LlamaIndex.
How does LlamaIndex connect to MCP servers?
Can I combine MCP tools with vector stores?
Does LlamaIndex support async MCP calls?
Connect Internet Archive Wayback with your favorite client
Step-by-step setup guides for every MCP-compatible client and framework:
Anthropic's native desktop app for Claude with built-in MCP support.
AI-first code editor with integrated LLM-powered coding assistance.
GitHub Copilot in VS Code with Agent mode and MCP support.
Purpose-built IDE for agentic AI coding workflows.
Autonomous AI coding agent that runs inside VS Code.
Anthropic's agentic CLI for terminal-first development.
Python SDK for building production-grade OpenAI agent workflows.
Google's framework for building production AI agents.
Type-safe agent development for Python with first-class MCP support.
TypeScript toolkit for building AI-powered web applications.
TypeScript-native agent framework for modern web stacks.
Python framework for orchestrating collaborative AI agent crews.
Leading Python framework for composable LLM applications.
Data-aware AI agent framework for structured and unstructured sources.
Microsoft's framework for multi-agent collaborative conversations.
Connect Internet Archive Wayback to LlamaIndex
Get your token, paste the configuration, and start using 10 tools in under 2 minutes. No API key management needed.