Remote MCP · Endpoint

Semscraper MCP server

No. Semscraper answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.semscraper.com/mcp

The last check completed an MCP handshake.

Registry name
com.semscraper/semscraper
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
269 ms
Tools exposed
8 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Real Google and Google Maps SERPs for AI assistants: pixel positions, AI Overviews and sources.
Listing
From the official MCP registry (active).
Recent checks of Semscraper
CheckedResultHandshake
1 hour agoHandshake completed269 ms
1 day agoHandshake completed285 ms
2 days agoHandshake completed253 ms
2 days agoHandshake completed261 ms
4 days agoHandshake completed255 ms
7 days agoHandshake completed259 ms
9 days agoHandshake completed255 ms
12 days agoHandshake completed258 ms
14 days agoHandshake completed257 ms
16 days agoHandshake completed264 ms
18 days agoHandshake completed264 ms
20 days agoCredentials required—
22 days agoCredentials required—
24 days agoCredentials required—

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