Remote MCP · Endpoint

ScrapingBot MCP server

No. ScrapingBot answered an MCP handshake 7 hours ago.

UpLast checked 7 hours ago

Server URL

https://scrapingbot.io/api/mcp

The last check completed an MCP handshake.

Registry name
io.scrapingbot/scrapingbot
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
196 ms
Tools exposed
23 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Public web data for AI agents: scrape any page, plus Google, TikTok, Instagram and Amazon as JSON.
Listing
From the official MCP registry (active).
Recent checks of ScrapingBot
CheckedResultHandshake
7 hours agoHandshake completed196 ms
2 days agoHandshake completed167 ms
5 days agoHandshake completed192 ms
7 days agoHandshake completed230 ms
9 days agoHandshake completed213 ms
11 days agoHandshake completed174 ms
13 days agoHandshake completed194 ms
15 days agoHandshake completed164 ms
17 days agoHandshake completed1.14 s
19 days agoHandshake completed252 ms
20 days agoHandshake completed234 ms
21 days agoHandshake completed144 ms
23 days agoHandshake completed189 ms

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

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