Remote MCP · Endpoint

Korean Law MCP MCP server

No. Korean Law MCP answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.gomdori.app/law

The last check completed an MCP handshake.

Registry name
io.github.chrisryugj/korean-law-mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
258 ms
Tools exposed
10 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Korean law: statutes, precedents, ordinances, treaties and citation verification (법제처 API).
Listing
From the official MCP registry (active).
Recent checks of Korean Law MCP
CheckedResultHandshake
1 hour agoHandshake completed258 ms
1 day agoHandshake completed270 ms
2 days agoHandshake completed462 ms
2 days agoHandshake completed449 ms
4 days agoHandshake completed274 ms
6 days agoHandshake completed259 ms
9 days agoHandshake completed257 ms
11 days agoHandshake completed279 ms
14 days agoHandshake completed268 ms
16 days agoHandshake completed264 ms
18 days agoHandshake completed259 ms
20 days agoHandshake completed291 ms
22 days agoHandshake completed260 ms
23 days agoHandshake completed268 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 Korean Law MCP and makes no claim about it beyond what these checks measured.