Remote MCP · Endpoint

ScrapeMole Domains MCP server

No. ScrapeMole Domains answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

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

The last check completed an MCP handshake.

Registry name
dev.pages.scrapemole/domains
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
545 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Pay-per-call x402 DNS, WHOIS/RDAP, availability, email security, SSL check, CT subdomains.
Listing
From the official MCP registry (active).
Recent checks of ScrapeMole Domains
CheckedResultHandshake
1 hour agoHandshake completed545 ms
1 day agoHandshake completed664 ms
2 days agoHandshake completed306 ms
3 days agoHandshake completed745 ms
4 days agoHandshake completed317 ms
5 days agoHandshake completed68 ms
6 days agoHandshake completed410 ms
9 days agoHandshake completed375 ms
11 days agoHandshake completed307 ms
14 days agoHandshake completed303 ms
16 days agoHandshake completed311 ms
18 days agoHandshake completed675 ms
20 days agoHandshake completed415 ms
22 days agoHandshake completed361 ms
24 days agoHandshake completed301 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 ScrapeMole Domains and makes no claim about it beyond what these checks measured.