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).
Recent checks of Taifoon coordination layer
CheckedResultHandshake
4 days agoHandshake completed212 ms
4 days agoHandshake completed200 ms
5 days agoHandshake completed563 ms
7 days agoHandshake completed215 ms
8 days agoHandshake completed230 ms
9 days agoHandshake completed267 ms
10 days agoHandshake completed160 ms
11 days agoHandshake completed180 ms
12 days agoHandshake completed549 ms
15 days agoHandshake completed188 ms
18 days agoHandshake completed431 ms
20 days agoHandshake completed221 ms
22 days agoHandshake completed1.40 s
24 days agoHandshake completed522 ms
26 days agoHandshake completed155 ms
28 days agoHandshake completed422 ms
30 days agoHandshake completed158 ms
32 days agoHandshake completed169 ms
33 days agoHandshake completed198 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.