Is run_credit_diagnostic working right now?
work.autonet/agent-health · mcp-registry/work.autonet/agent-health/run_credit_diagnostic
Recovery track record: 2 outages in 90 days, median time-to-recovery 7 min.
Recent contract changes
Schema/catalog changes Glimind observed on this server — a changed contract can silently break a previously working call.
added—export_incident_evidence(2026-10-20)added—configure_agent_reengagement(2026-10-16)added—read_agent_reengagement(2026-10-16)added—run_signed_diagnostic(2026-10-16)added—create_diagnostic_watch(2026-10-16)
See all live alternatives to run_credit_diagnostic →
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:
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 run_credit_diagnostic working right now?
As of the latest check, run_credit_diagnostic (mcp-registry/work.autonet/agent-health/run_credit_diagnostic) has a Glimind reliability score of 91/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 run_credit_diagnostic?
run_credit_diagnostic scores 91/100 (grade A) on the Glimind reliability standard. The score is neutral and unconflicted — Glimind sells no tools.
What should I do if run_credit_diagnostic is down or failing?
Healthy — standard retry (1–2x) with jitter on transient errors. Use a timeout around 1000ms. Check Glimind for a live alternative before retrying.
What are the best alternatives to run_credit_diagnostic?
Glimind surfaces live, capability-matched alternatives the moment run_credit_diagnostic degrades — query https://glimind.com/v1/alternatives/mcp-registry%2Fwork.autonet%2Fagent-health%2Frun_credit_diagnostic.
How do I call run_credit_diagnostic reliably?
Before calling, check run_credit_diagnostic with Glimind (MCP: prepare_tool_call, or GET https://glimind.com/v1/prepare/mcp-registry%2Fwork.autonet%2Fagent-health%2Frun_credit_diagnostic) to get a known-good input shape, the expected output, a suggested timeout (~1000ms), 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:
[](https://glimind.com/tool/mcp-registry%2Fwork.autonet%2Fagent-health%2Frun_credit_diagnostic?ref=badge)
<a href="https://glimind.com/tool/mcp-registry%2Fwork.autonet%2Fagent-health%2Frun_credit_diagnostic?ref=badge"><img src="https://glimind.com/v1/badge/mcp-registry%2Fwork.autonet%2Fagent-health%2Frun_credit_diagnostic.svg" alt="Glimind reliability"></a>
.. image:: https://glimind.com/v1/badge/mcp-registry%2Fwork.autonet%2Fagent-health%2Frun_credit_diagnostic.svg :target: https://glimind.com/tool/mcp-registry%2Fwork.autonet%2Fagent-health%2Frun_credit_diagnostic?ref=badge :alt: Glimind reliability
Operator of work.autonet/agent-health?
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%2Fwork.autonet%2Fagent-health%2Frun_credit_diagnostic. 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-20T20:19:29.283Z.
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.