Remote MCP · Endpoint

Kosis Kr MCP server

No. Kosis Kr answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://gateway.pipeworx.io/kosis-kr/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/kosis-kr
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
74 ms
Tools exposed
44 tools
Uptime, last 30 days
100% from 16 checks
Described by its publisher as
Korean national statistics (KOSIS) — browse, search and pull time series from Statistics Korea's…
Listing
From the official MCP registry (active).
Recent checks of Kosis Kr
CheckedResultHandshake
1 hour agoHandshake completed74 ms
2 days agoHandshake completed62 ms
4 days agoHandshake completed85 ms
6 days agoHandshake completed57 ms
7 days agoHandshake completed82 ms
9 days agoHandshake completed69 ms
10 days agoHandshake completed219 ms
11 days agoHandshake completed59 ms
14 days agoHandshake completed43 ms
16 days agoHandshake completed41 ms
17 days agoHandshake completed179 ms
19 days agoHandshake completed121 ms
20 days agoHandshake completed47 ms
21 days agoHandshake completed43 ms
22 days agoHandshake completed41 ms
22 days agoHandshake completed43 ms

The last 16 checks. Full history is kept for 30 days; the all-time counter stands at 16 responding of 16.

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