Remote MCP · Endpoint

MyKIFRS MCP server

No. MyKIFRS answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mykifrs.eocpa.kr/mcp

The last check completed an MCP handshake.

Registry name
kr.eocpa/mykifrs
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
273 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Full-text search over K-IFRS/K-GAAP standards and KASB accounting Q&A for Korean accountants
Listing
From the official MCP registry (active).
Recent checks of MyKIFRS
CheckedResultHandshake
1 hour agoHandshake completed273 ms
2 days agoHandshake completed246 ms
4 days agoHandshake completed496 ms
5 days agoHandshake completed328 ms
7 days agoHandshake completed391 ms
8 days agoHandshake completed390 ms
9 days agoHandshake completed284 ms
12 days agoHandshake completed675 ms
13 days agoHandshake completed215 ms
15 days agoHandshake completed205 ms
17 days agoHandshake completed378 ms
18 days agoHandshake completed288 ms
19 days agoHandshake completed378 ms
20 days agoHandshake completed226 ms
21 days agoHandshake completed399 ms
21 days agoHandshake completed200 ms
23 days agoHandshake completed208 ms

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

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