Is thruact_compare working right now?
com.thruact/thruact · mcp-registry/com.thruact/thruact/thruact_compare
Recovery track record: 5 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—thruact_discover(2026-08-25)added—thruact_act(2026-08-25)added—thruact_compare(2026-08-25)added—thruact_call(2026-08-25)added—thruact_wallet(2026-08-25)
See all live alternatives to thruact_compare →
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 thruact_compare working right now?
As of the latest check, thruact_compare (mcp-registry/com.thruact/thruact/thruact_compare) has a Glimind reliability score of 87/100 (grade B) 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 thruact_compare?
thruact_compare scores 87/100 (grade B) on the Glimind reliability standard. The score is neutral and unconflicted — Glimind sells no tools.
What should I do if thruact_compare is down or failing?
Healthy — standard retry (1–2x) with jitter on transient errors. Use a timeout around 5052ms. Check Glimind for a live alternative before retrying.
What are the best alternatives to thruact_compare?
Glimind surfaces live, capability-matched alternatives the moment thruact_compare degrades — query https://glimind.com/v1/alternatives/mcp-registry%2Fcom.thruact%2Fthruact%2Fthruact_compare.
How do I call thruact_compare reliably?
Before calling, check thruact_compare with Glimind (MCP: prepare_tool_call, or GET https://glimind.com/v1/prepare/mcp-registry%2Fcom.thruact%2Fthruact%2Fthruact_compare) to get a known-good input shape, the expected output, a suggested timeout (~5052ms), 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%2Fcom.thruact%2Fthruact%2Fthruact_compare?ref=badge)
<a href="https://glimind.com/tool/mcp-registry%2Fcom.thruact%2Fthruact%2Fthruact_compare?ref=badge"><img src="https://glimind.com/v1/badge/mcp-registry%2Fcom.thruact%2Fthruact%2Fthruact_compare.svg" alt="Glimind reliability"></a>
.. image:: https://glimind.com/v1/badge/mcp-registry%2Fcom.thruact%2Fthruact%2Fthruact_compare.svg :target: https://glimind.com/tool/mcp-registry%2Fcom.thruact%2Fthruact%2Fthruact_compare?ref=badge :alt: Glimind reliability
Operator of com.thruact/thruact?
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%2Fcom.thruact%2Fthruact%2Fthruact_compare. 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-16T19:48:02.207Z.
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.