Is construction_barometer working right now?
pt.flatin/property-taxes · mcp-registry/pt.flatin/property-taxes/construction_barometer
Recovery track record: 10 outages in 90 days, median time-to-recovery 4 min.
Recent contract changes
Schema/catalog changes Glimind observed on this server — a changed contract can silently break a previously working call.
added—required_income(2026-10-26)added—municipality_housing_pipeline(2026-10-26)schema_changed—request_consultation(2026-10-23)schema_changed—imt_calculate(2026-10-19)schema_changed—imi_rate(2026-10-19)
See all live alternatives to construction_barometer →
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 construction_barometer working right now?
As of the latest check, construction_barometer (mcp-registry/pt.flatin/property-taxes/construction_barometer) has a Glimind reliability score of 82/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 construction_barometer?
construction_barometer scores 82/100 (grade B) on the Glimind reliability standard. The score is neutral and unconflicted — Glimind sells no tools.
What should I do if construction_barometer is down or failing?
Healthy — standard retry (1–2x) with jitter on transient errors. Use a timeout around 1923ms. Check Glimind for a live alternative before retrying.
What are the best alternatives to construction_barometer?
Glimind surfaces live, capability-matched alternatives the moment construction_barometer degrades — query https://glimind.com/v1/alternatives/mcp-registry%2Fpt.flatin%2Fproperty-taxes%2Fconstruction_barometer.
How do I call construction_barometer reliably?
Before calling, check construction_barometer with Glimind (MCP: prepare_tool_call, or GET https://glimind.com/v1/prepare/mcp-registry%2Fpt.flatin%2Fproperty-taxes%2Fconstruction_barometer) to get a known-good input shape, the expected output, a suggested timeout (~1923ms), 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%2Fpt.flatin%2Fproperty-taxes%2Fconstruction_barometer?ref=badge)
<a href="https://glimind.com/tool/mcp-registry%2Fpt.flatin%2Fproperty-taxes%2Fconstruction_barometer?ref=badge"><img src="https://glimind.com/v1/badge/mcp-registry%2Fpt.flatin%2Fproperty-taxes%2Fconstruction_barometer.svg" alt="Glimind reliability"></a>
.. image:: https://glimind.com/v1/badge/mcp-registry%2Fpt.flatin%2Fproperty-taxes%2Fconstruction_barometer.svg :target: https://glimind.com/tool/mcp-registry%2Fpt.flatin%2Fproperty-taxes%2Fconstruction_barometer?ref=badge :alt: Glimind reliability
Operator of pt.flatin/property-taxes?
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%2Fpt.flatin%2Fproperty-taxes%2Fconstruction_barometer. 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-26T20:29:16.812Z.
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.