Remote MCP · Endpoint

Taifoon coordination layer MCP server

No. Taifoon coordination layer answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://coord.taifoon.dev/mcp?ref=mcp-registry

The last check completed an MCP handshake.

Registry name
io.taifoon/coordination-layer
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
1.85 s
Tools exposed
15 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Start here: a free key in one call, then a demand in words that is hired, graded and settled
Listing
From the official MCP registry (active).
Recent checks of Taifoon coordination layer
CheckedResultHandshake
1 hour agoHandshake completed1.85 s
2 days agoHandshake completed1.45 s
4 days agoHandshake completed1.84 s
6 days agoHandshake completed900 ms
8 days agoHandshake completed1.89 s
10 days agoHandshake completed1.73 s
13 days agoHandshake completed1.54 s
14 days agoHandshake completed1.91 s
16 days agoHandshake completed300 ms
17 days agoHandshake completed201 ms
18 days agoHandshake completed184 ms
21 days agoHandshake completed338 ms
22 days agoHandshake completed268 ms
24 days agoHandshake completed219 ms

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

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.