ALM X++ MCP Server
https://www.almxpp.com/mcpD365 F&O: 90 AI tools over 200K+ indexed objects, 25M+ cross-references, 392K+ labels.
Reliability & health
Uptime and response time from our own unpaid probes, plus the reliability score built from them.
Uptime
85.7% avgResponse time
p50 360ms · p95 451msData table
| Bucket | Uptime | Probes | Response time |
|---|---|---|---|
| 8/14/2026, 4:00:00 AM | 0% | 1 | — |
| 8/15/2026, 4:00:00 AM | 0% | 1 | — |
| 8/16/2026, 4:00:00 AM | 0% | 1 | — |
| 8/17/2026, 4:00:00 AM | 0% | 1 | — |
| 8/18/2026, 5:00:00 AM | 0% | 1 | — |
| 8/19/2026, 5:00:00 AM | 100% | 1 | 363ms |
| 8/19/2026, 6:00:00 AM | 100% | 1 | 324ms |
| 8/19/2026, 7:00:00 AM | 100% | 1 | 469ms |
| 8/19/2026, 8:00:00 AM | 100% | 1 | 511ms |
| 8/19/2026, 9:00:00 AM | 100% | 1 | 394ms |
| 8/19/2026, 10:00:00 AM | 100% | 1 | 331ms |
| 8/19/2026, 12:00:00 PM | 100% | 1 | 357ms |
| 8/19/2026, 1:00:00 PM | 100% | 1 | 370ms |
| 8/19/2026, 2:00:00 PM | 100% | 1 | 382ms |
| 8/19/2026, 3:00:00 PM | 100% | 1 | 323ms |
| 8/19/2026, 4:00:00 PM | 100% | 1 | 368ms |
| 8/19/2026, 5:00:00 PM | 100% | 1 | 360ms |
| 8/19/2026, 6:00:00 PM | 100% | 1 | 369ms |
| 8/19/2026, 7:00:00 PM | 100% | 1 | 371ms |
| 8/19/2026, 8:00:00 PM | 100% | 1 | 371ms |
| 8/19/2026, 10:00:00 PM | 100% | 1 | 338ms |
| 8/19/2026, 11:00:00 PM | 100% | 1 | 360ms |
| 8/20/2026, 12:00:00 AM | 100% | 1 | 360ms |
| 8/20/2026, 1:00:00 AM | 100% | 1 | 390ms |
| 8/20/2026, 2:00:00 AM | 100% | 1 | 342ms |
| 8/20/2026, 3:00:00 AM | 100% | 1 | 380ms |
| 8/20/2026, 5:00:00 AM | 100% | 1 | 366ms |
| 8/20/2026, 6:00:00 AM | 100% | 1 | 433ms |
| 8/20/2026, 7:00:00 AM | 100% | 1 | 335ms |
| 8/20/2026, 8:00:00 AM | 100% | 1 | 352ms |
| 8/20/2026, 9:00:00 AM | 100% | 1 | 361ms |
| 8/20/2026, 10:00:00 AM | 100% | 1 | 355ms |
| 8/20/2026, 11:00:00 AM | 100% | 1 | 313ms |
| 8/20/2026, 1:00:00 PM | 100% | 1 | 323ms |
| 8/20/2026, 2:00:00 PM | 100% | 1 | 337ms |
- Availability
- 52
- Latency
- 98
- 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
- OVH sas
- Domain registered
- 2026-02-26
- Hosting network
- BLS-98-64-0-0-1003020950
- 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.