Remote MCP · Endpoint

Worldpop MCP server

No. Worldpop answered an MCP handshake 1 day ago.

UpLast checked 1 day ago

Server URL

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

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/worldpop
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
103 ms
Tools exposed
44 tools
Uptime, last 30 days
93.3% from 15 checks
Described by its publisher as
WorldPop 100 m gridded population estimates from the University of Southampton — total population…
Listing
From the official MCP registry (active).
Recent checks of Worldpop
CheckedResultHandshake
1 day agoHandshake completed103 ms
3 days agoHandshake completed50 ms
5 days agoHandshake completed60 ms
7 days agoHandshake completed56 ms
8 days agoHandshake completed93 ms
10 days agoHandshake completed191 ms
11 days agoHandshake completed43 ms
13 days agoHandshake completed41 ms
15 days agoHandshake completed54 ms
17 days agoHandshake completed50 ms
18 days agoFailed - the request timed out—
19 days agoHandshake completed50 ms
20 days agoHandshake completed987 ms
22 days agoHandshake completed69 ms
22 days agoHandshake completed234 ms

The last 15 checks. Full history is kept for 30 days; the all-time counter stands at 14 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 Worldpop and makes no claim about it beyond what these checks measured.