Commoncrawl
NPM · @PIPEWORX/MCP-COMMONCRAWL · 2 COMPONENTS
Common Crawl's public web archive — find every time a URL was crawled since 2008 and read the…
Available components
Last scanned (9 hours ago)
Scores higher than 79% of npm servers
Category Web Scraping
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-commoncrawl). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 10 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability64
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 859 tokens (~286/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management43
- Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 10 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 6 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
- Package version: 0.2.0 → 0.2.1 functional
- 30 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 29 Oct 26 79
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 11 Nov 2026 · Analysed npm/@pipeworx/mcp-commoncrawl@0.2.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | pipeworx-io/mcp-commoncrawl |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-commoncrawl/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3612196442 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:d0ba8d362f2c7df5abb424f7d350ec716d00b1660b5405d3e80d5e32de183af900cb1837683c0a5add3a13130dc04b8ad9356f5af57d0847625953abb |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
commoncrawl_crawls ~157
List the Common Crawl monthly crawl collections (crawl ids like "CC-MAIN-2026-34") with the date range each one covers. AUTHORITATIVE for "which Common Crawl snapshot covers <date>" — call this first to pick the crawl id that commoncrawl_index_search needs. Newest first. Keyless.
| Name | Type | Req | Description |
|---|---|---|---|
| contains_date | string | – | Optional ISO date, e.g. "2025-01-15". Returns only the crawl(s) whose capture window covers that date — the answer to "which snapshot would have seen my page then". |
| limit | number | – | How many crawls to return, newest first. Default 20, max 120 (the full history back to 2008). |
No output schema declared.
No examples provided.
commoncrawl_fetch_record ~264
Read one archived page back out of Common Crawl by byte range — pass the filename, offset and length from a commoncrawl_index_search result and get the WARC headers, the captured HTTP response headers, and the page body as it was crawled. AUTHORITATIVE for "what did this page actually say when it was crawled", including pages that have since changed or gone offline. The body is truncated to a byte cap you control. Keyless.
| Name | Type | Req | Description |
|---|---|---|---|
| filename | string | yes | WARC path from a capture row, e.g. "crawl-data/CC-MAIN-2025-05/segments/1736703361969.6/warc/CC-MAIN-20250112194358-20250112224358-00433.warc.gz". |
| length | number | yes | Compressed byte length of the record (the capture row's "length"). Max 10485760 (10 MB). |
| max_body_bytes | number | – | Truncate the decoded page body to this many bytes before returning it. Default 20000, max 200000. WARC headers and HTTP headers are always returned in full. |
| offset | number | yes | Byte offset of the record within that WARC file (the capture row's "offset"). |
No output schema declared.
No examples provided.
commoncrawl_index_search ~386
Search one Common Crawl collection's CDX index for archived captures of a URL, host, or whole domain. PREFER OVER WEB SEARCH when the question is "what did this page look like in <month>", "did Common Crawl ever see this URL", or "list the URLs crawled under this domain" — it returns the crawl record (timestamp, HTTP status, MIME type, detected language, content digest) plus the WARC filename/offset/length that commoncrawl_fetch_record needs to read the page bytes. Keyless.
| Name | Type | Req | Description |
|---|---|---|---|
| crawl | string | – | Crawl collection id from commoncrawl_crawls, e.g. "CC-MAIN-2026-34". Defaults to the most recent crawl. |
| filter | string | – | Optional CDX field filter, e.g. "=status:200" (only successful captures), "=mime:text/html", "~url:.*blog.*". Repeatable filters are not supported here — pass one. |
| from | string | – | Optional lower bound on capture timestamp, as YYYY, YYYYMM, or YYYYMMDD, e.g. "202501". |
| limit | number | – | Maximum captures to return. Default 20, max 200. |
| match_type | string | – | How to match `url`: "exact" (that URL only), "prefix" (that path and everything under it), "host" (every URL on that exact host), "domain" (that host and all subdomains). Default "exact". |
| page | number | – | Zero-based page number for paging through a large domain query. Default 0. |
| to | string | – | Optional upper bound on capture timestamp, same format as `from`. |
| url | string | yes | URL, host, or domain to look up, e.g. "example.com", "https://www.nasa.gov/news", "*.python.org". |
No output schema declared.
No examples provided.
How do I install the Commoncrawl MCP server?
Commoncrawl runs locally as an npm package, launched with npx -y @pipeworx/mcp-commoncrawl. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @pipeworx/mcp-commoncrawl
claude mcp add pipeworx-io-commoncrawl -- npx -y @pipeworx/mcp-commoncrawl
What is the Commoncrawl MCP server?
Commoncrawl is an MCP server listed in the public MCP registry as io.github.pipeworx-io/commoncrawl. Common Crawl's public web archive, find every time a URL was crawled since 2008 and read the… This page covers its npm package (@pipeworx/mcp-commoncrawl).
Is the Commoncrawl MCP server safe to use?
Commoncrawl scores 85 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 11 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Commoncrawl MCP server expose?
Commoncrawl exposes 3 tools: commoncrawl_crawls, commoncrawl_index_search, commoncrawl_fetch_record. Their descriptions and schemas cost roughly 807 tokens of context every time the server is loaded.
Is the Commoncrawl MCP server still maintained?
Commoncrawl is still listed as active in the MCP registry. We last reached this channel on 11 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Commoncrawl MCP server under?
Commoncrawl declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the Commoncrawl MCP server?
VerifyMCP ran 16 checks on Commoncrawl, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.