Remote MCP · Endpoint

Commoncrawl MCP server

No. Commoncrawl answered an MCP handshake 1 day ago.

UpLast checked 1 day ago

Server URL

https://gateway.pipeworx.io/commoncrawl/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/commoncrawl
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
76 ms
Tools exposed
44 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Common Crawl's public web archive — find every time a URL was crawled since 2008 and read the…
Listing
From the official MCP registry (active).
Recent checks of Commoncrawl
CheckedResultHandshake
1 day agoHandshake completed76 ms
3 days agoHandshake completed50 ms
5 days agoHandshake completed57 ms
7 days agoHandshake completed73 ms
8 days agoHandshake completed333 ms
9 days agoHandshake completed183 ms
11 days agoHandshake completed59 ms
13 days agoHandshake completed91 ms
15 days agoHandshake completed56 ms
17 days agoHandshake completed250 ms
18 days agoHandshake completed44 ms
19 days agoHandshake completed38 ms
20 days agoHandshake completed47 ms
21 days agoHandshake completed48 ms
21 days agoHandshake completed45 ms

The last 15 checks. Full history is kept for 30 days; the all-time counter stands at 15 responding of 15.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with Commoncrawl and makes no claim about it beyond what these checks measured.