Is on_call_rotation working right now?

ai.llpro/campus · mcp-registry/ai.llpro/campus/on_call_rotation

One MCP connection for every live tool. Your agent finds the right tool and calls it through Glimind, and skips servers that are down. Free, no signup.Add to CursorVS CodeAdd to Claude Code copies a terminal command claude mcp add --transport http glimind https://glimind.com/mcp?ref=install-tool. Other clients
healthy
Recommendation: proceed
uptime (30d probes)
97.4%
checks observed
1,165
p50 latency
1.2s
data basis
probe-history (1165 checks, 97.4% up)

Recovery track record: 7 outages in 90 days, median time-to-recovery 16 min.

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 on_call_rotation →

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?ref=install-tool

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp?ref=install-tool"
    }
  }
}

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

FAQ

Is on_call_rotation working right now?

As of the latest check, on_call_rotation (mcp-registry/ai.llpro/campus/on_call_rotation) has a Glimind reliability score of 73/100 (grade C) 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 on_call_rotation?

on_call_rotation scores 73/100 (grade C) on the Glimind reliability standard. The score is neutral and unconflicted — Glimind sells no tools.

What should I do if on_call_rotation is down or failing?

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

What are the best alternatives to on_call_rotation?

Glimind surfaces live, capability-matched alternatives the moment on_call_rotation degrades — query https://glimind.com/v1/alternatives/mcp-registry%2Fai.llpro%2Fcampus%2Fon_call_rotation.

How do I call on_call_rotation reliably?

Before calling, check on_call_rotation with Glimind (MCP: prepare_tool_call, or GET https://glimind.com/v1/prepare/mcp-registry%2Fai.llpro%2Fcampus%2Fon_call_rotation) to get a known-good input shape, the expected output, a suggested timeout (~3486ms), 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/ai.llpro/campus/on_call_rotation

Markdown
[![Glimind reliability](https://glimind.com/v1/badge/mcp-registry%2Fai.llpro%2Fcampus%2Fon_call_rotation.svg)](https://glimind.com/tool/mcp-registry%2Fai.llpro%2Fcampus%2Fon_call_rotation?ref=badge)
HTML
<a href="https://glimind.com/tool/mcp-registry%2Fai.llpro%2Fcampus%2Fon_call_rotation?ref=badge"><img src="https://glimind.com/v1/badge/mcp-registry%2Fai.llpro%2Fcampus%2Fon_call_rotation.svg" alt="Glimind reliability"></a>
reStructuredText
.. image:: https://glimind.com/v1/badge/mcp-registry%2Fai.llpro%2Fcampus%2Fon_call_rotation.svg
   :target: https://glimind.com/tool/mcp-registry%2Fai.llpro%2Fcampus%2Fon_call_rotation?ref=badge
   :alt: Glimind reliability

Operator of ai.llpro/campus?

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%2Fai.llpro%2Fcampus%2Fon_call_rotation. 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-11-22T16:32:06.040Z.

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.

Feedback
Help us improve