Remote MCP · Endpoint

ScrapeMole Search MCP server

Yes, as of 20 minutes ago: the server returned an HTTP error.

DownLast checked 20 minutes ago

Server URL

https://search.scrapemole.workers.dev/mcp

The last check failed: the server returned an HTTP error.

Registry name
dev.pages.scrapemole/search
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
3 tools
Uptime, last 30 days
92.9% from 14 checks
Described by its publisher as
Pay-per-call x402 web search results, news search and search autocomplete suggestions for agents.
Listing
From the official MCP registry (active).
Recent checks of ScrapeMole Search
CheckedResultHandshake
20 minutes agoFailed - the server returned an HTTP error—
9 days agoHandshake completed298 ms
9 days agoHandshake completed250 ms
11 days agoHandshake completed272 ms
12 days agoHandshake completed241 ms
13 days agoHandshake completed458 ms
14 days agoHandshake completed589 ms
14 days agoHandshake completed262 ms
16 days agoHandshake completed399 ms
19 days agoHandshake completed480 ms
21 days agoHandshake completed88 ms
24 days agoHandshake completed763 ms
26 days agoHandshake completed441 ms
28 days agoHandshake completed398 ms

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

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 ScrapeMole Search and makes no claim about it beyond what these checks measured.