Remote MCP · Endpoint

MyFSS MCP server

No. MyFSS answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://myfss.eocpa.kr/mcp

The last check completed an MCP handshake.

Registry name
kr.eocpa/myfss
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
272 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Full-text search over FSS/FSC accounting supervision documents for Korean accounting professionals
Listing
From the official MCP registry (active).
Recent checks of MyFSS
CheckedResultHandshake
1 hour agoHandshake completed272 ms
2 days agoHandshake completed209 ms
4 days agoHandshake completed397 ms
5 days agoHandshake completed398 ms
7 days agoHandshake completed230 ms
8 days agoHandshake completed218 ms
9 days agoHandshake completed1.05 s
12 days agoHandshake completed358 ms
13 days agoHandshake completed2.24 s
15 days agoHandshake completed617 ms
17 days agoHandshake completed207 ms
18 days agoHandshake completed200 ms
19 days agoHandshake completed205 ms
20 days agoHandshake completed199 ms
21 days agoHandshake completed207 ms
21 days agoHandshake completed291 ms
23 days agoHandshake completed219 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 MyFSS and makes no claim about it beyond what these checks measured.