Common Crawl's public web archive — find every time a URL was crawled since 2008 and read the…
MCPpedia last refreshed this data
io.github.pipeworx-io/commoncrawl is an MCP server that common Crawl's public web archive — find every time a URL was crawled since 2008 and read the…. Its tool list has not been published yet over http, requires no API key, and scores 87/100 on MCPpedia's security, maintenance and efficiency rubric.
Config is the same across clients - only the file and path differ.
{
"mcpServers": {
"commoncrawl": {
"url": "https://gateway.pipeworx.io/commoncrawl/mcp"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Common Crawl's public web archive — find every time a URL was crawled since 2008 and read the…
This server supports HTTP transport. Be the first to test it - help the community know if it works.
Five weighted categories - click any category to see the underlying evidence.
No known CVEs.
Checked @pipeworx/mcp-commoncrawl against OSV.dev.
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience - it helps other developers decide.
Sign in to write a review.
Others in browser
Open-source web scraper for AI agents with scrape, crawl, and map tools
Extract data from any website with thousands of scrapers, crawlers, and automations on Apify Store ⚡
Search-first MCP server for JavaScript reverse engineering: 735 tools across 36 domains.
Firecrawl, the context API for AI agents: search, scrape, interact with the web, plus paper search.
MCP Security Weekly
Get CVE alerts and security updates for io.github.pipeworx-io/commoncrawl and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
Common Crawl's public web archive — find every time a URL was crawled since 2008 and read back the exact page bytes that were captured.
Part of Pipeworx — an MCP gateway connecting AI agents to 1863+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.
commoncrawl_crawls(limit?, contains_date?) — the monthly crawl collections
(CC-MAIN-2026-34 and friends) with the capture window each one covers.
contains_date answers "which snapshot would have seen my page on that day".commoncrawl_index_search(url, crawl?, match_type?, limit?, page?, filter?, from?, to?) —
CDX index lookup for a URL, host or whole domain. Returns capture timestamp,
HTTP status, MIME type, detected language, content digest, and the WARC
filename + offset + length that the next tool needs.commoncrawl_fetch_record(filename, offset, length, max_body_bytes?) — reads
one archived record back by byte range: WARC headers, the captured HTTP
response headers, and the page body as crawled.Keyless.
url=example.com query alternated between 200 and nginx 502 inside a minute,
so it is load, not the query. ccFetch retries a 5xx twice with a short
backoff. Without that a caller reads transient nginx noise as "Common Crawl
has no record of this URL", which is a different and wrong answer.note, so an empty captures array is
never silently indistinguishable from an upstream failure.offset..offset+length-1 decompresses standalone — no need to stream the
whole 1 GB WARC. DecompressionStream('gzip') handles it in the Workers
runtime.new TextDecoder('utf-8', { fatal: false }) does not typecheck against
@cloudflare/workers-types: its TextDecoderConstructorOptions requires
ignoreBOM too. Pass no options; non-fatal is the default anyway.match_type: "domain" query over a large domain is expensive upstream
and is the first thing to 502. Narrow with match_type: "host" plus a
filter such as =status:200.crawlgraph is our own link graph over sites we crawl. This pack reads the
Common Crawl Foundation's corpus — different data, different questions.
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"commoncrawl": {
"url": "https://gateway.pipeworx.io/commoncrawl/mcp"
}
}
}
tools/list at https://gateway.pipeworx.io/commoncrawl/mcp returns the tools in the table
above plus the shared Pipeworx meta-tools — ask_pipeworx,
discover_tools, search_within, remember/recall and the rest of the
gateway-wide set. So the tool count you see is larger than this table: a
single-pack endpoint currently lists roughly 30 shared tools alongside the
pack's own. The connection's initialize response states its exact scope, and
is the authoritative answer for a given day.
This is deliberate, not multiplexing by accident. The meta-tools are what let a
scoped connection answer a question this pack does not cover — via
ask_pipeworx, which routes across the whole catalog — without you adding a
second MCP server. There is currently no way to mount a pack endpoint without
them; if the extra schemas cost you more context than the rou