Remote MCP · Endpoint

Health Statistics MCP server

No. Health Statistics answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://monit.ly/api/mcp/health

The last check completed an MCP handshake.

Registry name
io.github.ContentWriterco/health-statistics
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
407 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Health statistics for AI agents: life expectancy, causes of death, health spending, WHO data.
Listing
From the official MCP registry (active).
Recent checks of Health Statistics
CheckedResultHandshake
1 hour agoHandshake completed407 ms
22 hours agoHandshake completed426 ms
1 day agoHandshake completed153 ms
2 days agoHandshake completed170 ms
4 days agoHandshake completed437 ms
7 days agoHandshake completed455 ms
9 days agoHandshake completed416 ms
12 days agoHandshake completed167 ms
14 days agoHandshake completed395 ms
16 days agoHandshake completed392 ms
18 days agoHandshake completed393 ms
20 days agoHandshake completed412 ms
22 days agoHandshake completed413 ms
24 days agoHandshake completed422 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 Health Statistics and makes no claim about it beyond what these checks measured.