commoncrawl
This server has a remotely hosted endpoint. Open its connector listing for connection details, authentication requirements, and setup instructions:
@pipeworx/commoncrawl
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.
Tools
commoncrawl_crawls(limit?, contains_date?)— the monthly crawl collections (CC-MAIN-2026-34and friends) with the capture window each one covers.contains_dateanswers "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 WARCfilename+offset+lengththat 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.
Related MCP server: MCP Wayback Machine Server
Auth
Keyless.
Data sources
https://index.commoncrawl.org/collinfo.json — the crawl collection list.
https://index.commoncrawl.org/{crawl}-index — the CDX index, JSON-lines.
<https://data.commoncrawl.org/{warc path}> — WARC records, HTTP range reads.
Things the next person would otherwise rediscover
The CDX host 502s sporadically under load. Measured 2026-09-17: the same
url=example.comquery alternated between 200 and nginx 502 inside a minute, so it is load, not the query.ccFetchretries 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."No captures" is a 404 with an English sentence, not JSON. Handled as an empty result set with an explicit
note, so an emptycapturesarray is never silently indistinguishable from an upstream failure.Each indexed record is its own gzip member, so a byte-range read of
offset..offset+length-1decompresses 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: itsTextDecoderConstructorOptionsrequiresignoreBOMtoo. Pass no options; non-fatal is the default anyway.A broad
match_type: "domain"query over a large domain is expensive upstream and is the first thing to 502. Narrow withmatch_type: "host"plus afiltersuch as=status:200.
Related packs
crawlgraph is our own link graph over sites we crawl. This pack reads the
Common Crawl Foundation's corpus — different data, different questions.
Quick Start
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"commoncrawl": {
"url": "https://gateway.pipeworx.io/commoncrawl/mcp"
}
}
}What this endpoint actually serves
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 routing is worth,
connect to the full gateway once rather than to several pack endpoints.
Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:
{
"mcpServers": {
"pipeworx": {
"url": "https://gateway.pipeworx.io/mcp"
}
}
}Both URLs reach the same gateway and the same 1863+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
No MCP client? Call it over HTTP
curl -X POST https://gateway.pipeworx.io/v1/tools/commoncrawl_crawls \
-H 'Content-Type: application/json' \
-d '{"limit":3}'No account needed for the first calls. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/commoncrawl_crawls. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.
Run it from npm
@pipeworx/mcp-commoncrawl is a local stdio bridge to the Pipeworx gateway: your MCP client
starts it with npx, and it forwards every call to the same
https://gateway.pipeworx.io/commoncrawl/mcp endpoint shown above. It needs network access;
there is no offline mode.
{
"mcpServers": {
"commoncrawl": {
"command": "npx",
"args": ["-y", "@pipeworx/mcp-commoncrawl"]
}
}
}Without a key it calls anonymously, capped at 50 calls a day. A free account
raises that to 200 a day: get a key at https://pipeworx.io/signup and add
"env": { "PIPEWORX_API_KEY": "<your key>" } to the server entry.
The key is sent as a Bearer token, the same way a hosted connection sends it,
so calls are metered and billed exactly as they are there.
It lists only this pack's tools by default. Set PIPEWORX_META_TOOLS=1 to
also list ask_pipeworx and the other gateway-wide tools.
Behind an HTTPS proxy: Node's built-in fetch does not read HTTPS_PROXY by
default. Newer Node releases honour it when NODE_USE_ENV_PROXY=1 is set; check
your Node version's documentation.
Using with ask_pipeworx
Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:
ask_pipeworx({ question: "your question about Commoncrawl data" })The gateway picks the right tool and fills the arguments automatically.
More
License
MIT
This server cannot be deployed
Maintenance
Related MCP Connectors
Wayback Machine for agents: closest archived copy of a URL with its text, and full capture history
Search the Wayback Machine and IA library (40M+ items), fetch snapshots, item metadata, and text.
EU archive of the machine-readable web: check a domain, order a time-stamped record or extract.
Capture web pages as cryptographically signed, tamper-evident evidence with WACZ archives.
Related MCP Servers
- AlicenseBqualityDmaintenanceProvides access to the Internet Archive Wayback Machine to list snapshots, fetch archived web pages, and search archive.org items. Enables retrieval of historical website content and metadata through natural language queries.35MIT
- AlicenseNot gradedqualityDmaintenanceEnables interaction with the Internet Archive's Wayback Machine to save web pages, retrieve archived versions, search historical snapshots, and check archive statistics without requiring API keys.961 npmCreative Commons Attribution Non Commercial Share Alike 4.0 International
- AlicenseAqualityCmaintenanceMCP server for the Internet Archive's Wayback Machine. Search archived snapshots, extract page text from a specific date, track how a site has changed over time, check if broken links are recoverable, and perform research across Internet Archive collections.640 PyPI3MIT
- AlicenseNot gradedqualityBmaintenanceEnables agents to retrieve the closest archived snapshot of a URL with extracted page text, and to query the complete capture history for a URL, prefix, host, or domain, with fallback to Common Crawl.23 npm1MIT