Is check_address_risks working right now?

com.faireplace/public-tools · mcp-registry/com.faireplace/public-tools/check_address_risks

Recovery track record: 3288 outages in 90 days, median time-to-recovery 4 min.

Working alternatives

• real_estate_fr_risks io.github.helpmyagent/helpmyagent
• consulter_risques_naturels io.github.OneNicolas/mcp-service-public
• company_fr_risk io.github.helpmyagent/helpmyagent
• list_risks com.ascent-partners/coso-mcp

See all live alternatives to check_address_risks →

claude mcp add --transport http glimind https://glimind.com/mcp

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is check_address_risks working right now?

As of the latest check, check_address_risks (mcp-registry/com.faireplace/public-tools/check_address_risks) has a Glimind reliability score of 42/100 (grade D) and its current verdict is "degraded" — recommendation: proceed with caution. Glimind tracks this live from safe liveness probes plus privacy-clean real-usage outcomes.

How reliable is check_address_risks?

check_address_risks scores 42/100 (grade D) on the Glimind reliability standard. The score is neutral and unconflicted — Glimind sells no tools.

What should I do if check_address_risks is down or failing?

Degraded — retry at most once with backoff and a longer timeout; line up an alternative. Use a timeout around 37371ms. Live alternatives that do a similar job: real_estate_fr_risks, consulter_risques_naturels, company_fr_risk, list_risks.

What are the best alternatives to check_address_risks?

Working alternatives ranked by capability similarity and live health: real_estate_fr_risks, consulter_risques_naturels, company_fr_risk, list_risks. See each one's live status on Glimind.

How do I call check_address_risks reliably?

Before calling, check check_address_risks with Glimind (MCP: prepare_tool_call, or GET https://glimind.com/v1/prepare/mcp-registry%2Fcom.faireplace%2Fpublic-tools%2Fcheck_address_risks) to get a known-good input shape, the expected output, a suggested timeout (~37371ms), 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:

[![Glimind reliability](https://glimind.com/v1/badge/mcp-registry%2Fcom.faireplace%2Fpublic-tools%2Fcheck_address_risks.svg)](https://glimind.com/tool/mcp-registry%2Fcom.faireplace%2Fpublic-tools%2Fcheck_address_risks?ref=badge)

<a href="https://glimind.com/tool/mcp-registry%2Fcom.faireplace%2Fpublic-tools%2Fcheck_address_risks?ref=badge"><img src="https://glimind.com/v1/badge/mcp-registry%2Fcom.faireplace%2Fpublic-tools%2Fcheck_address_risks.svg" alt="Glimind reliability"></a>

.. image:: https://glimind.com/v1/badge/mcp-registry%2Fcom.faireplace%2Fpublic-tools%2Fcheck_address_risks.svg
   :target: https://glimind.com/tool/mcp-registry%2Fcom.faireplace%2Fpublic-tools%2Fcheck_address_risks?ref=badge
   :alt: Glimind reliability

Operator of com.faireplace/public-tools?

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.faireplace%2Fpublic-tools%2Fcheck_address_risks. 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-17T17:47:53.796Z.

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.