Remote MCP · Endpoint

Scrapingant MCP server

No. Scrapingant answered an MCP handshake 1 day ago.

UpLast checked 1 day ago

Server URL

https://gateway.pipeworx.io/scrapingant/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/scrapingant
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
50 ms
Tools exposed
39 tools
Uptime, last 30 days
93.8% from 16 checks
Described by its publisher as
ScrapingAnt MCP — wraps the ScrapingAnt web scraping API (scrapingant.com)
Listing
From the official MCP registry (active).
Recent checks of Scrapingant
CheckedResultHandshake
1 day agoHandshake completed50 ms
3 days agoHandshake completed71 ms
5 days agoFailed - the request timed out—
7 days agoHandshake completed79 ms
8 days agoHandshake completed58 ms
9 days agoHandshake completed51 ms
11 days agoHandshake completed53 ms
13 days agoHandshake completed44 ms
15 days agoHandshake completed81 ms
16 days agoHandshake completed47 ms
17 days agoHandshake completed41 ms
19 days agoHandshake completed35 ms
20 days agoHandshake completed59 ms
20 days agoHandshake completed36 ms
21 days agoHandshake completed54 ms
22 days agoHandshake completed53 ms

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