Wikivibe MCP
https://wikivibe.ru/mcpSearch and read public Wikivibe articles about AI coding, agents, MCP, GEO, bots and deployment.
Reliability & health
Uptime and response time from our own unpaid probes, plus the reliability score built from them.
Uptime
99.2% avgResponse time
p50 686ms · p95 1339msData table
| Bucket | Uptime | Probes | Response time |
|---|---|---|---|
| 8/8/2026, 12:00:00 AM | 100% | 1 | 1061ms |
| 8/9/2026, 12:00:00 AM | 100% | 1 | 631ms |
| 8/10/2026, 12:00:00 AM | 100% | 1 | 939ms |
| 8/11/2026, 12:00:00 AM | 100% | 1 | 998ms |
| 8/12/2026, 12:00:00 AM | 100% | 1 | 910ms |
| 8/13/2026, 12:00:00 AM | 100% | 1 | 974ms |
| 8/14/2026, 12:00:00 AM | 100% | 1 | 968ms |
| 8/15/2026, 12:00:00 AM | 100% | 1 | 972ms |
| 8/16/2026, 12:00:00 AM | 100% | 1 | 806ms |
| 8/17/2026, 12:00:00 AM | 100% | 1 | 833ms |
| 8/18/2026, 12:00:00 AM | 100% | 1 | 1008ms |
| 8/19/2026, 12:00:00 AM | 100% | 21 | 758ms |
| 8/20/2026, 12:00:00 AM | 100% | 20 | 856ms |
| 8/21/2026, 12:00:00 AM | 95% | 22 | 865ms |
| 8/22/2026, 12:00:00 AM | 100% | 24 | 934ms |
| 8/23/2026, 12:00:00 AM | 100% | 20 | 906ms |
| 8/24/2026, 12:00:00 AM | 100% | 21 | 940ms |
| 8/25/2026, 12:00:00 AM | 100% | 15 | 917ms |
| 8/26/2026, 12:00:00 AM | 89% | 9 | 860ms |
| 8/27/2026, 12:00:00 AM | 100% | 14 | 929ms |
| 8/28/2026, 12:00:00 AM | 100% | 20 | 852ms |
| 8/29/2026, 12:00:00 AM | 100% | 21 | 966ms |
| 8/30/2026, 12:00:00 AM | 100% | 21 | 994ms |
| 8/31/2026, 12:00:00 AM | 95% | 21 | 953ms |
| 9/1/2026, 12:00:00 AM | 100% | 20 | 930ms |
| 9/2/2026, 12:00:00 AM | 100% | 21 | 630ms |
| 9/3/2026, 12:00:00 AM | 100% | 21 | 622ms |
| 9/4/2026, 12:00:00 AM | 100% | 20 | 574ms |
| 9/5/2026, 12:00:00 AM | 95% | 21 | 580ms |
| 9/6/2026, 12:00:00 AM | 100% | 15 | 592ms |
- Availability
- 99
- Latency
- 87
- Security
- 99
- Transparency
- 42
- 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
- xorekcloud-hel
- Hosting country
- FI
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.