Remote MCP · Endpoint

ScrapeMole MCP server

No. ScrapeMole answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://scrapemole-api-mainnet.scrapemole.workers.dev/mcp

The last check completed an MCP handshake.

Registry name
dev.pages.scrapemole/scrapemole
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
906 ms
Tools exposed
9 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Pay-per-call YouTube data via x402 (USDC, Base): search, channels, playlists, video details, comment
Listing
From the official MCP registry (active).
Recent checks of ScrapeMole
CheckedResultHandshake
1 hour agoHandshake completed906 ms
1 day agoHandshake completed1.29 s
2 days agoHandshake completed665 ms
3 days agoHandshake completed473 ms
4 days agoHandshake completed386 ms
5 days agoHandshake completed395 ms
6 days agoHandshake completed75 ms
9 days agoHandshake completed366 ms
11 days agoHandshake completed51 ms
14 days agoHandshake completed693 ms
16 days agoHandshake completed764 ms
18 days agoHandshake completed387 ms
20 days agoHandshake completed72 ms
22 days agoHandshake completed357 ms
24 days agoHandshake completed433 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 and makes no claim about it beyond what these checks measured.