Remote MCP · Endpoint

台灣加密貨幣資料 MCP server

No. 台灣加密貨幣資料 answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://tw-crypto-api.panda198271.workers.dev/mcp

The last check completed an MCP handshake.

Registry name
dev.workers.panda198271.tw-crypto-api/crypto-api
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
155 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
台灣合規虛擬資產業者名單、詐騙網址檢查與加密貨幣稅務估算。
Listing
From the official MCP registry (active).
Recent checks of 台灣加密貨幣資料
CheckedResultHandshake
1 hour agoHandshake completed155 ms
2 days agoHandshake completed94 ms
4 days agoHandshake completed116 ms
6 days agoHandshake completed108 ms
8 days agoHandshake completed98 ms
10 days agoHandshake completed95 ms
11 days agoHandshake completed61 ms
13 days agoHandshake completed44 ms
14 days agoHandshake completed64 ms
15 days agoHandshake completed104 ms
18 days agoHandshake completed67 ms
19 days agoHandshake completed55 ms
21 days agoHandshake completed94 ms
22 days agoHandshake completed60 ms
23 days agoHandshake completed50 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 台灣加密貨幣資料 and makes no claim about it beyond what these checks measured.