Taifoon coordination layer
https://coord.taifoon.dev/mcpStart here: a free key in one call, then a demand in words that is hired, graded and settled
Reliability & health
Uptime and response time from our own unpaid probes, plus the reliability score built from them.
Uptime
100.0% avgResponse time
p50 339ms · p95 971msData table
| Bucket | Uptime | Probes | Response time |
|---|---|---|---|
| 9/30/2026, 3:00:00 AM | 100% | 1 | 261ms |
| 9/30/2026, 5:00:00 AM | 100% | 1 | 890ms |
| 9/30/2026, 7:00:00 AM | 100% | 1 | 216ms |
| 9/30/2026, 9:00:00 AM | 100% | 1 | 412ms |
| 9/30/2026, 11:00:00 AM | 100% | 1 | 355ms |
| 9/30/2026, 1:00:00 PM | 100% | 1 | 974ms |
| 9/30/2026, 3:00:00 PM | 100% | 1 | 210ms |
| 9/30/2026, 5:00:00 PM | 100% | 1 | 342ms |
| 9/30/2026, 7:00:00 PM | 100% | 1 | 266ms |
| 9/30/2026, 9:00:00 PM | 100% | 1 | 118ms |
| 9/30/2026, 11:00:00 PM | 100% | 1 | 184ms |
| 10/1/2026, 1:00:00 AM | 100% | 1 | 829ms |
| 10/1/2026, 3:00:00 AM | 100% | 1 | 760ms |
| 10/1/2026, 5:00:00 AM | 100% | 1 | 965ms |
| 10/1/2026, 7:00:00 AM | 100% | 1 | 687ms |
| 10/1/2026, 9:00:00 AM | 100% | 1 | 1193ms |
| 10/1/2026, 11:00:00 AM | 100% | 1 | 432ms |
| 10/1/2026, 1:00:00 PM | 100% | 1 | 358ms |
| 10/1/2026, 3:00:00 PM | 100% | 1 | 893ms |
| 10/1/2026, 5:00:00 PM | 100% | 1 | 408ms |
| 10/1/2026, 7:00:00 PM | 100% | 1 | 938ms |
| 10/1/2026, 9:00:00 PM | 100% | 1 | 1120ms |
| 10/1/2026, 11:00:00 PM | 100% | 1 | 266ms |
| 10/2/2026, 1:00:00 AM | 100% | 1 | 227ms |
| 10/2/2026, 3:00:00 AM | 100% | 1 | 210ms |
| 10/2/2026, 5:00:00 AM | 100% | 1 | 765ms |
| 10/2/2026, 7:00:00 AM | 100% | 1 | 841ms |
| 10/2/2026, 9:00:00 AM | 100% | 1 | 351ms |
| 10/2/2026, 11:00:00 AM | 100% | 1 | 558ms |
| 10/2/2026, 1:00:00 PM | 100% | 1 | 672ms |
| 10/2/2026, 3:00:00 PM | 100% | 1 | 977ms |
| 10/2/2026, 5:00:00 PM | 100% | 1 | 237ms |
| 10/2/2026, 7:00:00 PM | 100% | 1 | 908ms |
| 10/2/2026, 9:00:00 PM | 100% | 1 | 336ms |
| 10/2/2026, 11:00:00 PM | 100% | 1 | 206ms |
| 10/3/2026, 12:00:00 AM | 100% | 1 | 294ms |
| 10/3/2026, 2:00:00 AM | 100% | 1 | 865ms |
| 10/3/2026, 4:00:00 AM | 100% | 1 | 252ms |
| 10/3/2026, 6:00:00 AM | 100% | 1 | 344ms |
| 10/3/2026, 8:00:00 AM | 100% | 1 | 531ms |
| 10/3/2026, 10:00:00 AM | 100% | 1 | 311ms |
| 10/3/2026, 12:00:00 PM | 100% | 1 | 262ms |
| 10/3/2026, 2:00:00 PM | 100% | 1 | 323ms |
| 10/3/2026, 4:00:00 PM | 100% | 1 | 287ms |
| 10/3/2026, 6:00:00 PM | 100% | 1 | 277ms |
| 10/3/2026, 8:00:00 PM | 100% | 1 | 262ms |
| 10/3/2026, 11:00:00 PM | 100% | 1 | 245ms |
| 10/4/2026, 1:00:00 AM | 100% | 1 | 401ms |
| 10/4/2026, 3:00:00 AM | 100% | 1 | 614ms |
| 10/4/2026, 5:00:00 AM | 100% | 1 | 746ms |
| 10/4/2026, 7:00:00 AM | 100% | 1 | 645ms |
| 10/4/2026, 9:00:00 AM | 100% | 1 | 313ms |
| 10/4/2026, 1:00:00 PM | 100% | 1 | 238ms |
| 10/4/2026, 3:00:00 PM | 100% | 1 | 244ms |
| 10/4/2026, 5:00:00 PM | 100% | 1 | 732ms |
| 10/4/2026, 7:00:00 PM | 100% | 1 | 674ms |
| 10/4/2026, 9:00:00 PM | 100% | 1 | 260ms |
| 10/5/2026, 2:00:00 AM | 100% | 1 | 181ms |
| 10/5/2026, 7:00:00 AM | 100% | 1 | 196ms |
| 10/5/2026, 9:00:00 AM | 100% | 1 | 142ms |
| 10/5/2026, 11:00:00 AM | 100% | 1 | 220ms |
| 10/5/2026, 1:00:00 PM | 100% | 1 | 591ms |
| 10/5/2026, 2:00:00 PM | 100% | 1 | 182ms |
| 10/5/2026, 4:00:00 PM | 100% | 1 | 177ms |
| 10/5/2026, 6:00:00 PM | 100% | 1 | 270ms |
| 10/5/2026, 8:00:00 PM | 100% | 1 | 668ms |
| 10/5/2026, 10:00:00 PM | 100% | 1 | 268ms |
| 10/6/2026, 1:00:00 AM | 100% | 1 | 180ms |
- Availability
- 100
- Latency
- 99
- Security
- 100
- Transparency
- 36
- Activity
- not yet measured
How often it was reachable when we probed it (weight 35%).
How quickly it answers when it is up — fast scores high (weight 20%).
Whether it serves over working TLS / https (weight 15%).
Whether the operator disclosed what it does — description, schema, identity (weight 15%).
Observed on-chain payments to this endpoint's wallet — transactions, volume, and distinct paying wallets over the last month (weight 15%; not yet measured when we have not seen its wallet settle).
Confidence 100% — how much probe evidence backs this score. A thin history is flagged, not hidden.
See the scoring methodology for exactly how each number is computed.
Payment
- Currencies
- —
- Networks
- —
- Facilitator
- unknown
- SDK
- unknown
Operator
- Company
- inferred — unknown
- Jurisdiction
- —
- Registrar
- Porkbun LLC
- Domain registered
- 2026-02-03
- Hosting network
- VERCEL-02
- Hosting country
- —
Operator context is derived from public RDAP/TLS records and unverified. Company and country are only available for endpoints that publish them (an OV/EV TLS certificate or a non-redacted domain record); most endpoints are CDN-fronted and disclose neither.
Linked by wallet — likely same operator
On-chain agent identity and the x402 endpoint that shares its settlement wallet.