Renewly
https://renewly.gg/api/mcpRead contracts, track renewals, surface vendor leverage, and draft cancellation/renewal emails.
Reliability & health
Uptime and response time from our own unpaid probes, plus the reliability score built from them.
Uptime
100.0% avgResponse time
p50 1122ms · p95 1363msData table
| Bucket | Uptime | Probes | Response time |
|---|---|---|---|
| 8/9/2026, 12:00:00 AM | 100% | 1 | 879ms |
| 8/10/2026, 12:00:00 AM | 100% | 1 | 853ms |
| 8/11/2026, 12:00:00 AM | 100% | 1 | 928ms |
| 8/12/2026, 12:00:00 AM | 100% | 1 | 238ms |
| 8/13/2026, 12:00:00 AM | 100% | 1 | 315ms |
| 8/14/2026, 12:00:00 AM | 100% | 1 | 990ms |
| 8/15/2026, 12:00:00 AM | 100% | 1 | 1528ms |
| 8/16/2026, 12:00:00 AM | 100% | 1 | 1015ms |
| 8/17/2026, 12:00:00 AM | 100% | 1 | 1035ms |
| 8/18/2026, 12:00:00 AM | 100% | 1 | 1013ms |
| 8/19/2026, 12:00:00 AM | 100% | 20 | 986ms |
| 8/20/2026, 12:00:00 AM | 100% | 21 | 980ms |
| 8/21/2026, 12:00:00 AM | 100% | 22 | 974ms |
| 8/22/2026, 12:00:00 AM | 100% | 21 | 945ms |
| 8/23/2026, 12:00:00 AM | 100% | 21 | 956ms |
| 8/24/2026, 12:00:00 AM | 100% | 21 | 1195ms |
| 8/25/2026, 12:00:00 AM | 100% | 15 | 1115ms |
| 8/26/2026, 12:00:00 AM | 100% | 9 | 1066ms |
| 8/27/2026, 12:00:00 AM | 100% | 14 | 1112ms |
| 8/28/2026, 12:00:00 AM | 100% | 20 | 1142ms |
| 8/29/2026, 12:00:00 AM | 100% | 21 | 1146ms |
| 8/30/2026, 12:00:00 AM | 100% | 21 | 1112ms |
| 8/31/2026, 12:00:00 AM | 100% | 20 | 1120ms |
| 9/1/2026, 12:00:00 AM | 100% | 21 | 1108ms |
| 9/2/2026, 12:00:00 AM | 100% | 21 | 1118ms |
| 9/3/2026, 12:00:00 AM | 100% | 21 | 1118ms |
| 9/4/2026, 12:00:00 AM | 100% | 20 | 1118ms |
| 9/5/2026, 12:00:00 AM | 100% | 21 | 1119ms |
| 9/6/2026, 12:00:00 AM | 100% | 17 | 1132ms |
| 9/7/2026, 12:00:00 AM | 100% | 3 | 1097ms |
- Availability
- 100
- Latency
- 70
- 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
- —
- Domain registered
- —
- Hosting network
- VERCEL-09
- 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.