Remote MCP · Endpoint

Ecos Kr MCP server

No. Ecos Kr answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

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

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/ecos-kr
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
97 ms
Tools exposed
48 tools
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
ECOS — Bank of Korea Economic Statistics System.
Listing
From the official MCP registry (active).
Recent checks of Ecos Kr
CheckedResultHandshake
2 hours agoHandshake completed97 ms
1 day agoHandshake completed68 ms
2 days agoHandshake completed94 ms
3 days agoHandshake completed71 ms
4 days agoHandshake completed95 ms
5 days agoHandshake completed156 ms
7 days agoHandshake completed251 ms
9 days agoHandshake completed165 ms
11 days agoHandshake completed480 ms
14 days agoHandshake completed114 ms
16 days agoHandshake completed75 ms
18 days agoHandshake completed62 ms
20 days agoHandshake completed584 ms
22 days agoHandshake completed66 ms
24 days agoHandshake completed54 ms
26 days agoHandshake completed51 ms
27 days agoHandshake completed134 ms
29 days agoHandshake completed158 ms

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

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