Remote MCP · Endpoint

회계위키 (AccountingWiki) MCP server

No. 회계위키 (AccountingWiki) answered an MCP handshake 21 minutes ago.

UpLast checked 21 minutes ago

Server URL

https://accountingwiki.co.kr/api/mcp

The last check completed an MCP handshake.

Registry name
kr.co.accountingwiki/accountingwiki
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
98 ms
Tools exposed
12 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Korean accounting standards (K-IFRS, K-GAAP, audit, ICFR) and official Q&A, cited by paragraph.
Listing
From the official MCP registry (active).
Recent checks of 회계위키 (AccountingWiki)
CheckedResultHandshake
21 minutes agoHandshake completed98 ms
9 days agoHandshake completed96 ms
9 days agoHandshake completed57 ms
11 days agoHandshake completed80 ms
12 days agoHandshake completed90 ms
13 days agoHandshake completed86 ms
14 days agoHandshake completed77 ms
15 days agoHandshake completed101 ms
16 days agoHandshake completed65 ms
19 days agoHandshake completed108 ms
21 days agoHandshake completed114 ms
24 days agoHandshake completed94 ms
26 days agoHandshake completed80 ms
28 days agoHandshake completed84 ms

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

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 회계위키 (AccountingWiki) and makes no claim about it beyond what these checks measured.