Remote MCP · Endpoint

io.github.cyanheads/ilostat-mcp-server MCP server

No. io.github.cyanheads/ilostat-mcp-server answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://ilostat.caseyjhand.com/mcp

The last check completed an MCP handshake.

Registry name
io.github.cyanheads/ilostat-mcp-server
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
269 ms
Tools exposed
8 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Search ILOSTAT labour indicators, query and compare series, build country profiles, run SQL.
Listing
From the official MCP registry (active).
Recent checks of io.github.cyanheads/ilostat-mcp-server
CheckedResultHandshake
1 hour agoHandshake completed269 ms
2 days agoHandshake completed300 ms
5 days agoHandshake completed269 ms
7 days agoHandshake completed281 ms
9 days agoHandshake completed266 ms
11 days agoHandshake completed141 ms
13 days agoHandshake completed119 ms
15 days agoHandshake completed264 ms
17 days agoHandshake completed218 ms
19 days agoHandshake completed125 ms
20 days agoHandshake completed134 ms
21 days agoHandshake completed139 ms
23 days agoHandshake completed150 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 io.github.cyanheads/ilostat-mcp-server and makes no claim about it beyond what these checks measured.