io.github.iwanek86/pricemyrepair-mcp
https://app.pricemyrepair.co.uk/functions/pmrMcpUK car repair and servicing cost ranges per car model, in GBP, from PriceMyRepair.
Reliability & health
Uptime and response time from our own unpaid probes, plus the reliability score built from them.
Uptime
100.0% avgResponse time
p50 386ms · p95 580msData table
| Bucket | Uptime | Probes | Response time |
|---|---|---|---|
| 9/4/2026, 9:00:00 PM | 100% | 1 | 239ms |
| 9/4/2026, 10:00:00 PM | 100% | 1 | 336ms |
| 9/4/2026, 11:00:00 PM | 100% | 1 | 407ms |
| 9/5/2026, 12:00:00 AM | 100% | 1 | 472ms |
| 9/5/2026, 1:00:00 AM | 100% | 1 | 294ms |
| 9/5/2026, 3:00:00 AM | 100% | 1 | 456ms |
| 9/5/2026, 4:00:00 AM | 100% | 1 | 482ms |
| 9/5/2026, 5:00:00 AM | 100% | 1 | 401ms |
| 9/5/2026, 6:00:00 AM | 100% | 1 | 516ms |
| 9/5/2026, 7:00:00 AM | 100% | 1 | 199ms |
| 9/5/2026, 8:00:00 AM | 100% | 1 | 461ms |
| 9/5/2026, 10:00:00 AM | 100% | 1 | 233ms |
| 9/5/2026, 11:00:00 AM | 100% | 1 | 359ms |
| 9/5/2026, 12:00:00 PM | 100% | 1 | 335ms |
| 9/5/2026, 1:00:00 PM | 100% | 1 | 351ms |
| 9/5/2026, 2:00:00 PM | 100% | 1 | 497ms |
| 9/5/2026, 3:00:00 PM | 100% | 1 | 643ms |
| 9/5/2026, 5:00:00 PM | 100% | 1 | 249ms |
| 9/5/2026, 6:00:00 PM | 100% | 1 | 413ms |
| 9/5/2026, 7:00:00 PM | 100% | 1 | 433ms |
| 9/5/2026, 8:00:00 PM | 100% | 1 | 267ms |
| 9/5/2026, 9:00:00 PM | 100% | 1 | 202ms |
| 9/5/2026, 10:00:00 PM | 100% | 1 | 594ms |
| 9/6/2026, 12:00:00 AM | 100% | 1 | 310ms |
| 9/6/2026, 1:00:00 AM | 100% | 1 | 362ms |
| 9/6/2026, 2:00:00 AM | 100% | 1 | 308ms |
| 9/6/2026, 3:00:00 AM | 100% | 1 | 575ms |
| 9/6/2026, 4:00:00 AM | 100% | 1 | 451ms |
| 9/6/2026, 5:00:00 AM | 100% | 1 | 279ms |
| 9/6/2026, 7:00:00 AM | 100% | 1 | 234ms |
| 9/6/2026, 8:00:00 AM | 100% | 1 | 410ms |
| 9/6/2026, 9:00:00 AM | 100% | 1 | 387ms |
| 9/6/2026, 10:00:00 AM | 100% | 1 | 527ms |
| 9/6/2026, 11:00:00 AM | 100% | 1 | 429ms |
| 9/6/2026, 12:00:00 PM | 100% | 1 | 383ms |
- Availability
- 100
- Latency
- 97
- 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 70% — 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
- Nominet UK
- Domain registered
- —
- Hosting network
- RS-1125
- 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.