Handoff
https://app.usehandoff.com.br/api/mcpIT asset management — track equipment, allocations, and digital responsibility terms for your team.
Reliability & health
Uptime and response time from our own unpaid probes, plus the reliability score built from them.
Uptime
100.0% avgResponse time
p50 2011ms · p95 2501msData table
| Bucket | Uptime | Probes | Response time |
|---|---|---|---|
| 7/23/2026, 12:00:00 AM | 100% | 1 | 673ms |
| 7/24/2026, 12:00:00 AM | 100% | 1 | 1403ms |
| 7/25/2026, 12:00:00 AM | 100% | 1 | 2230ms |
| 7/26/2026, 12:00:00 AM | 100% | 1 | 2260ms |
| 7/27/2026, 12:00:00 AM | 100% | 1 | 1267ms |
| 7/28/2026, 12:00:00 AM | 100% | 1 | 2215ms |
| 7/29/2026, 12:00:00 AM | 100% | 1 | 2488ms |
| 7/30/2026, 12:00:00 AM | 100% | 1 | 2288ms |
| 7/31/2026, 12:00:00 AM | 100% | 1 | 1260ms |
| 8/1/2026, 12:00:00 AM | 100% | 1 | 2028ms |
| 8/2/2026, 12:00:00 AM | 100% | 1 | 2231ms |
| 8/3/2026, 12:00:00 AM | 100% | 1 | 2363ms |
| 8/4/2026, 12:00:00 AM | 100% | 1 | 1503ms |
| 8/5/2026, 12:00:00 AM | 100% | 1 | 2240ms |
| 8/6/2026, 12:00:00 AM | 100% | 1 | 2277ms |
| 8/7/2026, 12:00:00 AM | 100% | 1 | 1511ms |
| 8/8/2026, 12:00:00 AM | 100% | 1 | 2211ms |
| 8/9/2026, 12:00:00 AM | 100% | 1 | 2109ms |
| 8/10/2026, 12:00:00 AM | 100% | 1 | 2098ms |
| 8/11/2026, 12:00:00 AM | 100% | 1 | 1394ms |
| 8/12/2026, 12:00:00 AM | 100% | 1 | 1463ms |
| 8/13/2026, 12:00:00 AM | 100% | 1 | 1610ms |
| 8/14/2026, 12:00:00 AM | 100% | 1 | 1514ms |
| 8/15/2026, 12:00:00 AM | 100% | 1 | 1377ms |
| 8/16/2026, 12:00:00 AM | 100% | 1 | 1241ms |
| 8/17/2026, 12:00:00 AM | 100% | 1 | 2433ms |
| 8/18/2026, 12:00:00 AM | 100% | 1 | 1558ms |
| 8/19/2026, 12:00:00 AM | 100% | 20 | 1551ms |
| 8/20/2026, 12:00:00 AM | 100% | 21 | 1820ms |
| 8/21/2026, 12:00:00 AM | 100% | 1 | 368ms |
- Availability
- 100
- Latency
- 36
- Security
- 100
- Transparency
- 30
- 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
- —
- 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.