Remote MCP · Endpoint

ScrapeField MCP server

No. ScrapeField answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://scrapefield.com/mcp

The last check completed an MCP handshake.

Registry name
com.scrapefield/scrapefield
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
313 ms
Tools exposed
47 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Google Maps, LinkedIn, Instagram, TikTok and X data as tools. Demo mode needs no key.
Listing
From the official MCP registry (active).
Recent checks of ScrapeField
CheckedResultHandshake
2 hours agoHandshake completed313 ms
1 day agoHandshake completed117 ms
3 days agoHandshake completed114 ms
3 days agoHandshake completed105 ms
4 days agoHandshake completed101 ms
5 days agoHandshake completed94 ms
7 days agoHandshake completed119 ms
10 days agoHandshake completed281 ms
12 days agoHandshake completed89 ms
15 days agoHandshake completed105 ms
17 days agoHandshake completed110 ms
19 days agoHandshake completed99 ms
21 days agoHandshake completed114 ms
23 days agoHandshake completed129 ms
25 days agoHandshake completed108 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 ScrapeField and makes no claim about it beyond what these checks measured.