Remote MCP · Endpoint
Taifoon coordination layer MCP server
No. Taifoon coordination layer answered an MCP handshake 4 days ago.
UpLast checked 4 days ago
Server URL
https://www.taifoon.io/api/mcp
The last check completed an MCP handshake.
- Registry name
- io.taifoon/coordination-layer
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 212 ms
- Tools exposed
- 15 tools
- Uptime, last 30 days
- 100% from 16 checks
- Described by its publisher as
- Cross-chain V5 proofs, ERC-8004/8183 hiring, graded settlement and Grid tools over streamable HTTP
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 4 days ago | Handshake completed | 212 ms |
| 4 days ago | Handshake completed | 200 ms |
| 5 days ago | Handshake completed | 563 ms |
| 7 days ago | Handshake completed | 215 ms |
| 8 days ago | Handshake completed | 230 ms |
| 9 days ago | Handshake completed | 267 ms |
| 10 days ago | Handshake completed | 160 ms |
| 11 days ago | Handshake completed | 180 ms |
| 12 days ago | Handshake completed | 549 ms |
| 15 days ago | Handshake completed | 188 ms |
| 18 days ago | Handshake completed | 431 ms |
| 20 days ago | Handshake completed | 221 ms |
| 22 days ago | Handshake completed | 1.40 s |
| 24 days ago | Handshake completed | 522 ms |
| 26 days ago | Handshake completed | 155 ms |
| 28 days ago | Handshake completed | 422 ms |
| 30 days ago | Handshake completed | 158 ms |
| 32 days ago | Handshake completed | 169 ms |
| 33 days ago | Handshake completed | 198 ms |
The last 19 checks. Full history is kept for 30 days; the all-time counter stands at 26 responding of 26.
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 Taifoon coordination layer and makes no claim about it beyond what these checks measured.