Epovest/epovest-mcp / status

Epovest/epovest-mcp status

Operational · last checked 13:13 UTC · 151 ms · checked every about 5 minutes

Uptime

24 hours
100.000%
7 days
100.000%
30 days
100.000%
90 days
100.000%

90 days agotoday

Handshake latency p50 1011 ms · p95 2948 ms · mean time to recover 4 min

Incidents (90 days)

Outage · 2026-09-10 06:46 UTC · 4 min · http_5xx
Outage · 2026-09-01 11:20 UTC · 4 min · http_5xx
Outage · 2026-09-01 02:14 UTC · 9 min · http_5xx
Outage · 2026-08-06 05:47 UTC · 5 min · http_5xx
Outage · 2026-07-31 13:19 UTC · 1 min · timeout
Outage · 2026-07-31 06:11 UTC · 1 min · http_5xx

How this is measured

Checked by Glimind's probe (initialize + tools/list, never a tool call) from one region. Uptime counts a server as up when it completes the handshake, including when it asks for credentials. An outage starts at the first failed check, so short blips between checks are not seen. Every server is measured the same way; an owner's plan never changes these numbers. Owner updates are the owner's own words and sit next to the measurements, not in place of them.

JSON: /v1/status/glama/epovest/epovest-mcp · signed proof: /v1/proof/glama/epovest/epovest-mcp · Own this server?

Feedback
Help us improve