Remote MCP · Endpoint
台灣勞健保勞退試算 MCP server
No. 台灣勞健保勞退試算 answered an MCP handshake 2 hours ago.
UpLast checked 2 hours ago
Server URL
https://taiwan-payroll.simoko.workers.dev/mcp
The last check completed an MCP handshake.
- Registry name
- io.github.supra126/taiwan-payroll
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 145 ms
- Tools exposed
- 9 tools
- Uptime, last 30 days
- 4 checks from 4 checks
- Described by its publisher as
- 台灣勞保、健保、勞退、職災與二代健保補充保費試算，含薪資扣繳、破月與勞保老年給付。資料取自主管機關公告，對官方範例逐位元驗證。
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 2 hours ago | Handshake completed | 145 ms |
| 10 hours ago | Handshake completed | 143 ms |
| 1 day ago | Handshake completed | 305 ms |
| 2 days ago | Handshake completed | 131 ms |
The last 4 checks. Full history is kept for 30 days; the all-time counter stands at 4 responding of 4.
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 台灣勞健保勞退試算 and makes no claim about it beyond what these checks measured.