Is availability-sla-calculator working right now?

io.github.helphub369/utility-matrix · mcp-registry/io.github.helphub369/utility-matrix/availability-sla-calculator

healthy
Recommendation: proceed
uptime (30d probes)
100%
checks observed
2,391
p50 latency
1.5s
data basis
probe-history (2391 checks, 100% up)

Recovery track record: 2 outages in 90 days, median time-to-recovery 337 h.

Recent contract changes

Schema/catalog changes Glimind observed on this server — a changed contract can silently break a previously working call.

See all live alternatives to availability-sla-calculator →

Never call a dead tool again

Agents that check Glimind first make fewer failed calls, waste fewer tokens, and auto-route around outages like this one. Add it in ~10 seconds — free, no signup:

One click:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

Or wrap your calls with the SDK: npm i glimind · pip install glimind. See how it works

FAQ

Is availability-sla-calculator working right now?

As of the latest check, availability-sla-calculator (mcp-registry/io.github.helphub369/utility-matrix/availability-sla-calculator) has a Glimind reliability score of 90/100 (grade A) and its current verdict is "healthy" — recommendation: proceed. Glimind tracks this live from safe liveness probes plus privacy-clean real-usage outcomes.

How reliable is availability-sla-calculator?

availability-sla-calculator scores 90/100 (grade A) on the Glimind reliability standard. The score is neutral and unconflicted — Glimind sells no tools.

What should I do if availability-sla-calculator is down or failing?

Healthy — standard retry (1–2x) with jitter on transient errors. Use a timeout around 4515ms. Check Glimind for a live alternative before retrying.

What are the best alternatives to availability-sla-calculator?

Glimind surfaces live, capability-matched alternatives the moment availability-sla-calculator degrades — query https://glimind.com/v1/alternatives/mcp-registry%2Fio.github.helphub369%2Futility-matrix%2Favailability-sla-calculator.

How do I call availability-sla-calculator reliably?

Before calling, check availability-sla-calculator with Glimind (MCP: prepare_tool_call, or GET https://glimind.com/v1/prepare/mcp-registry%2Fio.github.helphub369%2Futility-matrix%2Favailability-sla-calculator) to get a known-good input shape, the expected output, a suggested timeout (~4515ms), and a live fallback.

Embed this live badge

Show live reliability in your README or status page. It auto-updates and links back here — copy one:

Glimind reliability badge for mcp-registry/io.github.helphub369/utility-matrix/availability-sla-calculator

Markdown
[![Glimind reliability](https://glimind.com/v1/badge/mcp-registry%2Fio.github.helphub369%2Futility-matrix%2Favailability-sla-calculator.svg)](https://glimind.com/tool/mcp-registry%2Fio.github.helphub369%2Futility-matrix%2Favailability-sla-calculator?ref=badge)
HTML
<a href="https://glimind.com/tool/mcp-registry%2Fio.github.helphub369%2Futility-matrix%2Favailability-sla-calculator?ref=badge"><img src="https://glimind.com/v1/badge/mcp-registry%2Fio.github.helphub369%2Futility-matrix%2Favailability-sla-calculator.svg" alt="Glimind reliability"></a>
reStructuredText
.. image:: https://glimind.com/v1/badge/mcp-registry%2Fio.github.helphub369%2Futility-matrix%2Favailability-sla-calculator.svg
   :target: https://glimind.com/tool/mcp-registry%2Fio.github.helphub369%2Futility-matrix%2Favailability-sla-calculator?ref=badge
   :alt: Glimind reliability

Operator of io.github.helphub369/utility-matrix?

Claim this listing → Prove you control this server (GitHub repo, live endpoint, or DNS — automated, ~1 min) to unlock the Verified operator marker, a remediation checklist (exactly why your score is what it is + how to raise it), and owner analytics. Or just embed the badge above and improve your score by having users report real outcomes (privacy-clean) via the free SDK. Glimind is neutral and sells no tools — the score is never for sale, so the fastest path to a better score is real uptime plus real usage.

Get the data (agents)

Query https://glimind.com/mcp (MCP) or GET https://glimind.com/v1/health/mcp-registry%2Fio.github.helphub369%2Futility-matrix%2Favailability-sla-calculator. The signed reliability feed for gateways/routers: GET https://glimind.com/v1/reliability/feed.

Rating methodology is transparent and neutral — Glimind sells no tools and runs no integrations; it only measures. Updated 2026-10-16T22:57:34.635Z.

This score is an automated estimate derived from safe liveness probes and privacy-clean outcomes reported by users; it may be incomplete, delayed, or inaccurate, and reflects reachability from Glimind's vantage point — not a statement of fact about the service. Glimind is not affiliated with, endorsed by, or acting for this tool or its operator; all names belong to their owners. Operator? Request a correction, or remove your server from measurement, via https://glimind.com/opt-out or [email protected] — we act promptly.