ChiefLab
https://api.chieflab.io/api/mcpOpen execution contract for agents doing business work. 6 operators, one MIT-licensed spec.
Reliability & health
Uptime and response time from our own unpaid probes, plus the reliability score built from them.
Uptime
100.0% avgResponse time
p50 136ms · p95 281msData table
| Bucket | Uptime | Probes | Response time |
|---|---|---|---|
| 9/5/2026, 12:00:00 AM | 100% | 20 | 147ms |
| 9/6/2026, 12:00:00 AM | 100% | 17 | 141ms |
| 9/7/2026, 12:00:00 AM | 100% | 15 | 150ms |
| 9/8/2026, 12:00:00 AM | 100% | 21 | 138ms |
| 9/9/2026, 12:00:00 AM | 100% | 20 | 140ms |
| 9/10/2026, 12:00:00 AM | 100% | 14 | 155ms |
| 9/11/2026, 12:00:00 AM | 100% | 10 | 165ms |
| 9/12/2026, 12:00:00 AM | 100% | 9 | 143ms |
| 9/13/2026, 12:00:00 AM | 100% | 16 | 186ms |
| 9/14/2026, 12:00:00 AM | 100% | 15 | 146ms |
| 9/15/2026, 12:00:00 AM | 100% | 16 | 150ms |
| 9/16/2026, 12:00:00 AM | 100% | 16 | 142ms |
| 9/17/2026, 12:00:00 AM | 100% | 15 | 155ms |
| 9/18/2026, 12:00:00 AM | 100% | 13 | 191ms |
| 9/19/2026, 12:00:00 AM | 100% | 13 | 142ms |
| 9/20/2026, 12:00:00 AM | 100% | 12 | 125ms |
| 9/21/2026, 12:00:00 AM | 100% | 12 | 150ms |
| 9/22/2026, 12:00:00 AM | 100% | 12 | 129ms |
| 9/23/2026, 12:00:00 AM | 100% | 12 | 128ms |
| 9/24/2026, 12:00:00 AM | 100% | 14 | 142ms |
| 9/25/2026, 12:00:00 AM | 100% | 13 | 142ms |
| 9/26/2026, 12:00:00 AM | 100% | 14 | 132ms |
| 9/27/2026, 12:00:00 AM | 100% | 13 | 125ms |
| 9/28/2026, 12:00:00 AM | 100% | 13 | 143ms |
| 9/29/2026, 12:00:00 AM | 100% | 12 | 143ms |
| 9/30/2026, 12:00:00 AM | 100% | 11 | 145ms |
| 10/1/2026, 12:00:00 AM | 100% | 12 | 142ms |
| 10/2/2026, 12:00:00 AM | 100% | 12 | 123ms |
| 10/3/2026, 12:00:00 AM | 100% | 12 | 134ms |
| 10/4/2026, 12:00:00 AM | 100% | 6 | 138ms |
- Availability
- 100
- Latency
- 100
- Security
- 100
- Transparency
- 61
- 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
- —
- Domain registered
- —
- Hosting network
- VERCEL-01
- 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.
Response schema
{
"type": "object"
}