Remote MCP · Endpoint

XBOSS MCP server

No. XBOSS answered an MCP handshake 3 hours ago.

UpLast checked 3 hours ago

Server URL

https://api.xdata.kr/mcp

The last check completed an MCP handshake.

Registry name
kr.xdata/xdata-mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
225 ms
Tools exposed
266 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Korean national tax and social insurance filings, invoices and payroll data as MCP tools.
Listing
From the official MCP registry (active).
Recent checks of XBOSS
CheckedResultHandshake
3 hours agoHandshake completed225 ms
2 days agoHandshake completed232 ms
4 days agoHandshake completed254 ms
5 days agoHandshake completed1.36 s
7 days agoHandshake completed224 ms
8 days agoHandshake completed254 ms
9 days agoHandshake completed225 ms
12 days agoHandshake completed222 ms
13 days agoHandshake completed221 ms
15 days agoHandshake completed226 ms
16 days agoHandshake completed223 ms
17 days agoHandshake completed222 ms
18 days agoHandshake completed210 ms
19 days agoHandshake completed214 ms
20 days agoHandshake completed216 ms
21 days agoHandshake completed218 ms
22 days agoHandshake completed262 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 XBOSS and makes no claim about it beyond what these checks measured.