ARPI ECG Analysis MCP · ARPI

Outage
Unclaimed — claim this pageother Auth expectations unknown
https://mcp.arpi.ai/mcp
Badge
OutageHTTP 404 on Streamable HTTP; SSE probe returned HTTP 404 (application/json; charset=utf-8).
Since Aug 18, 2026 — 7:10 AM (31 d ago)
16.7%
Availability · 30 days · 18 checks
654 ms
Latency (last observation)
Contract
Schema stable
0
Incidents · 30 days
Observed since

Availability — last 30 days

No failures Some failures Mostly failing Auth required No observations

Last observed 4 d ago by MCP Tools Edge Scanner · scheduled every 120 min

Outage Aug 18, 2026 — 9:15 AM
HTTP 404 on Streamable HTTP; SSE probe returned HTTP 404 (application/json; charset=utf-8).
VerifiedTwo consecutive observations failed (latest: http_error, HTTP 404).
InterpretationClients depending on this endpoint may currently be unable to connect.
Raw event details
{
  "result": "http_error",
  "error": "HTTP 404 on Streamable HTTP; SSE probe returned HTTP 404 (application/json; charset=utf-8)."
}
Observed by MCP Tools Edge Scanner
Baseline captured — authentication required Informational Aug 6, 2026 — 5:25 AM
Endpoint is reachable; initialization requires authentication. Passive observation records availability, latency, and protocol behavior only.
Verifiedinitialize returned HTTP 401.
InterpretationAuthenticated contract monitoring can be added later (OAuth support planned).
Raw event details
{
  "httpStatus": 401,
  "wwwAuthenticate": "Bearer error=\"invalid_token\", error_description=\"Authentication failed. The provided bearer token is invalid, expired, or no longer recognized by the server. To resolve: clear authentication tokens in your MCP client and reconnect. Your client should automatically re-register and obtain new tokens.\", resource_metadata=\"https://mcp.arpi.ai/.well-known/oauth-protected-resource/mcp\"",
  "discovery": null
}
Observed by MCP Tools Edge Scanner