Remote MCP · Endpoint

com.scrapelads/scrapelads MCP server

No. com.scrapelads/scrapelads answered an MCP handshake 13 minutes ago.

UpLast checked 13 minutes ago

Server URL

https://scrapelads.com/mcp

The last check completed an MCP handshake.

Registry name
com.scrapelads/scrapelads
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
64 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
TikTok creator emails, YouTube channel contacts and video transcripts for AI assistants.
Listing
From the official MCP registry (active).
Recent checks of com.scrapelads/scrapelads
CheckedResultHandshake
13 minutes agoHandshake completed64 ms
9 days agoHandshake completed95 ms
9 days agoHandshake completed70 ms
11 days agoHandshake completed95 ms
12 days agoHandshake completed136 ms
13 days agoHandshake completed112 ms
14 days agoHandshake completed71 ms
15 days agoHandshake completed67 ms
16 days agoHandshake completed276 ms
19 days agoHandshake completed78 ms
21 days agoHandshake completed68 ms
24 days agoHandshake completed99 ms
26 days agoHandshake completed91 ms
28 days agoHandshake completed64 ms

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

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