Is mcp-registry/com.enuygun/weg-mcp/car_cancel_commit working right now?
Recent contract changes
Schema/catalog changes Glimind observed on this server — a changed contract can silently break a previously working call.
added—flight_ticket_reissue(2026-07-10)added—flight_cancel_viewonly(2026-07-10)added—flight_get_reservation_detail(2026-07-10)added—flight_checkin(2026-07-10)added—mcp_enuygun_ping(2026-07-10)
See all live alternatives to mcp-registry/com.enuygun/weg-mcp/car_cancel_commit →
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 mcp-registry/com.enuygun/weg-mcp/car_cancel_commit working right now?
As of the latest check, mcp-registry/com.enuygun/weg-mcp/car_cancel_commit has a Glimind reliability score of 79/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 mcp-registry/com.enuygun/weg-mcp/car_cancel_commit?
mcp-registry/com.enuygun/weg-mcp/car_cancel_commit scores 79/100 (grade B) on the Glimind reliability standard. The score is neutral and unconflicted — Glimind sells no tools.
What should I do if mcp-registry/com.enuygun/weg-mcp/car_cancel_commit is down or failing?
Healthy — standard retry (1–2x) with jitter on transient errors. Use a timeout around 2373ms. Check Glimind for a live alternative before retrying.
What are the best alternatives to mcp-registry/com.enuygun/weg-mcp/car_cancel_commit?
Glimind surfaces live, capability-matched alternatives the moment mcp-registry/com.enuygun/weg-mcp/car_cancel_commit degrades — query https://glimind.com/v1/alternatives/mcp-registry%2Fcom.enuygun%2Fweg-mcp%2Fcar_cancel_commit.
How do I call mcp-registry/com.enuygun/weg-mcp/car_cancel_commit reliably?
Before calling, check mcp-registry/com.enuygun/weg-mcp/car_cancel_commit with Glimind (MCP: prepare_tool_call, or GET https://glimind.com/v1/prepare/mcp-registry%2Fcom.enuygun%2Fweg-mcp%2Fcar_cancel_commit) to get a known-good input shape, the expected output, a suggested timeout (~2373ms), 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.enuygun%2Fweg-mcp%2Fcar_cancel_commit?ref=badge)
<a href="https://glimind.com/tool/mcp-registry%2Fcom.enuygun%2Fweg-mcp%2Fcar_cancel_commit?ref=badge"><img src="https://glimind.com/v1/badge/mcp-registry%2Fcom.enuygun%2Fweg-mcp%2Fcar_cancel_commit.svg" alt="Glimind reliability"></a>
.. image:: https://glimind.com/v1/badge/mcp-registry%2Fcom.enuygun%2Fweg-mcp%2Fcar_cancel_commit.svg :target: https://glimind.com/tool/mcp-registry%2Fcom.enuygun%2Fweg-mcp%2Fcar_cancel_commit?ref=badge :alt: Glimind reliability
Operator of mcp-registry/com.enuygun/weg-mcp/car_cancel_commit?
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.enuygun%2Fweg-mcp%2Fcar_cancel_commit. 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-07-10T20:43:40.915Z.
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.