Is calculate_rent_revision working right now?
com.adminlanding/french-rental-compliance · mcp-registry/com.adminlanding/french-rental-compliance/calculate_rent_revision
Recovery track record: 72 outages in 90 days, median time-to-recovery 10 min.
Recent contract changes
Schema/catalog changes Glimind observed on this server — a changed contract can silently break a previously working call.
added—calculate_home_employment_end_of_contract(2026-08-24)added—calculate_assistant_maternel_end_of_contract(2026-08-24)schema_changed—check_zone_tendue(2026-08-21)schema_changed—calculate_tenant_notice_period(2026-08-21)schema_changed—check_dpe_rental_restrictions(2026-08-21)
See all live alternatives to calculate_rent_revision →
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 calculate_rent_revision working right now?
As of the latest check, calculate_rent_revision (mcp-registry/com.adminlanding/french-rental-compliance/calculate_rent_revision) has a Glimind reliability score of 60/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 calculate_rent_revision?
calculate_rent_revision scores 60/100 (grade C) on the Glimind reliability standard. The score is neutral and unconflicted — Glimind sells no tools.
What should I do if calculate_rent_revision is down or failing?
Healthy — standard retry (1–2x) with jitter on transient errors. Use a timeout around 11922ms. Check Glimind for a live alternative before retrying.
What are the best alternatives to calculate_rent_revision?
Glimind surfaces live, capability-matched alternatives the moment calculate_rent_revision degrades — query https://glimind.com/v1/alternatives/mcp-registry%2Fcom.adminlanding%2Ffrench-rental-compliance%2Fcalculate_rent_revision.
How do I call calculate_rent_revision reliably?
Before calling, check calculate_rent_revision with Glimind (MCP: prepare_tool_call, or GET https://glimind.com/v1/prepare/mcp-registry%2Fcom.adminlanding%2Ffrench-rental-compliance%2Fcalculate_rent_revision) to get a known-good input shape, the expected output, a suggested timeout (~11922ms), 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.adminlanding%2Ffrench-rental-compliance%2Fcalculate_rent_revision?ref=badge)
<a href="https://glimind.com/tool/mcp-registry%2Fcom.adminlanding%2Ffrench-rental-compliance%2Fcalculate_rent_revision?ref=badge"><img src="https://glimind.com/v1/badge/mcp-registry%2Fcom.adminlanding%2Ffrench-rental-compliance%2Fcalculate_rent_revision.svg" alt="Glimind reliability"></a>
.. image:: https://glimind.com/v1/badge/mcp-registry%2Fcom.adminlanding%2Ffrench-rental-compliance%2Fcalculate_rent_revision.svg :target: https://glimind.com/tool/mcp-registry%2Fcom.adminlanding%2Ffrench-rental-compliance%2Fcalculate_rent_revision?ref=badge :alt: Glimind reliability
Operator of com.adminlanding/french-rental-compliance?
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.adminlanding%2Ffrench-rental-compliance%2Fcalculate_rent_revision. 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-09-02T02:47:35.221Z.
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.