Remote MCP · Endpoint

Geonode Scraper API MCP server

No. Geonode Scraper API answered an MCP handshake 17 minutes ago.

UpLast checked 17 minutes ago

Server URL

https://scraper.geonode.io/mcp

The last check completed an MCP handshake.

Registry name
io.geonode/scraper
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
588 ms
Tools exposed
16 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Extract web pages, crawl and map sites, search the web. Extract needs no key; other tools need one.
Listing
From the official MCP registry (deprecated).
Recent checks of Geonode Scraper API
CheckedResultHandshake
17 minutes agoHandshake completed588 ms
9 days agoHandshake completed336 ms
9 days agoHandshake completed296 ms
11 days agoHandshake completed296 ms
12 days agoHandshake completed308 ms
13 days agoHandshake completed411 ms
14 days agoHandshake completed498 ms
14 days agoHandshake completed340 ms
16 days agoHandshake completed464 ms
19 days agoHandshake completed301 ms
21 days agoHandshake completed299 ms
24 days agoHandshake completed318 ms
26 days agoHandshake completed290 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 Geonode Scraper API and makes no claim about it beyond what these checks measured.