Is thread.agree_delivery_extension working right now?
com.setix/clearinghouse · mcp-registry/com.setix/clearinghouse/thread.agree_delivery_extension
Recovery track record: 195 outages in 90 days, median time-to-recovery 2 min.
Recent contract changes
Schema/catalog changes Glimind observed on this server — a changed contract can silently break a previously working call.
schema_changed—thread.file_dispute(2026-08-01)added—thread.poke_auto_release(2026-07-25)removed—thread.poke_auto_release(2026-07-25)added—thread.poke_auto_release(2026-07-25)schema_changed—thread.post_principal_delegation(2026-07-23)
See all live alternatives to thread.agree_delivery_extension →
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:
# MCP client — add one endpoint: https://glimind.com/mcp # or wrap your calls with the SDK: npm i glimind # pip install glimind
FAQ
Is thread.agree_delivery_extension working right now?
As of the latest check, thread.agree_delivery_extension (mcp-registry/com.setix/clearinghouse/thread.agree_delivery_extension) has a Glimind reliability score of 63/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 thread.agree_delivery_extension?
thread.agree_delivery_extension scores 63/100 (grade C) on the Glimind reliability standard. The score is neutral and unconflicted — Glimind sells no tools.
What should I do if thread.agree_delivery_extension is down or failing?
Healthy — standard retry (1–2x) with jitter on transient errors. Use a timeout around 5400ms. Check Glimind for a live alternative before retrying.
What are the best alternatives to thread.agree_delivery_extension?
Glimind surfaces live, capability-matched alternatives the moment thread.agree_delivery_extension degrades — query https://glimind.com/v1/alternatives/mcp-registry%2Fcom.setix%2Fclearinghouse%2Fthread.agree_delivery_extension.
How do I call thread.agree_delivery_extension reliably?
Before calling, check thread.agree_delivery_extension with Glimind (MCP: prepare_tool_call, or GET https://glimind.com/v1/prepare/mcp-registry%2Fcom.setix%2Fclearinghouse%2Fthread.agree_delivery_extension) to get a known-good input shape, the expected output, a suggested timeout (~5400ms), 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.setix%2Fclearinghouse%2Fthread.agree_delivery_extension?ref=badge)
<a href="https://glimind.com/tool/mcp-registry%2Fcom.setix%2Fclearinghouse%2Fthread.agree_delivery_extension?ref=badge"><img src="https://glimind.com/v1/badge/mcp-registry%2Fcom.setix%2Fclearinghouse%2Fthread.agree_delivery_extension.svg" alt="Glimind reliability"></a>
.. image:: https://glimind.com/v1/badge/mcp-registry%2Fcom.setix%2Fclearinghouse%2Fthread.agree_delivery_extension.svg :target: https://glimind.com/tool/mcp-registry%2Fcom.setix%2Fclearinghouse%2Fthread.agree_delivery_extension?ref=badge :alt: Glimind reliability
Operator of com.setix/clearinghouse?
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.setix%2Fclearinghouse%2Fthread.agree_delivery_extension. 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-08-21T13:24:29.554Z.
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.