Remote MCP · Endpoint

Criora climate risk MCP server

No. Criora climate risk answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://criora.com/mcp

The last check completed an MCP handshake.

Registry name
com.criora/criora
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
154 ms
Tools exposed
15 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Climate and disaster risk for any place: warnings, floods, heat, storms, quakes, countries, map
Listing
From the official MCP registry (active).
Recent checks of Criora climate risk
CheckedResultHandshake
2 hours agoHandshake completed154 ms
2 days agoHandshake completed514 ms
4 days agoHandshake completed453 ms
6 days agoHandshake completed453 ms
8 days agoHandshake completed475 ms
10 days agoHandshake completed192 ms
12 days agoHandshake completed146 ms
14 days agoHandshake completed464 ms
15 days agoHandshake completed463 ms
16 days agoHandshake completed529 ms
18 days agoHandshake completed145 ms
20 days agoHandshake completed506 ms
22 days agoHandshake completed452 ms
23 days agoHandshake completed159 ms

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