Remote MCP · Endpoint

Taiwan Companies MCP server

No. Taiwan Companies answered an MCP handshake 1 day ago.

UpLast checked 1 day ago

Server URL

https://gateway.pipeworx.io/taiwan-companies/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/taiwan-companies
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
121 ms
Tools exposed
44 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Taiwan's statutory company register: every incorporated company, its 統一編號, capital, registered…
Listing
From the official MCP registry (active).
Recent checks of Taiwan Companies
CheckedResultHandshake
1 day agoHandshake completed121 ms
3 days agoHandshake completed60 ms
5 days agoHandshake completed59 ms
7 days agoHandshake completed56 ms
9 days agoHandshake completed96 ms
10 days agoHandshake completed198 ms
11 days agoHandshake completed44 ms
14 days agoHandshake completed39 ms
15 days agoHandshake completed58 ms
17 days agoHandshake completed41 ms
18 days agoHandshake completed46 ms
20 days agoHandshake completed43 ms
21 days agoHandshake completed46 ms
22 days agoHandshake completed58 ms
22 days agoHandshake completed44 ms

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

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