# AtlasAdapt Muse connector

From musedirectory.ai, the independent directory of Meta Muse connectors. Not affiliated with Meta.

## AtlasAdapt

Check a building's climate risk and see which resilience upgrades pay for themselves.

- Record: https://musedirectory.ai/connector/atlasadapt
- Category: Research & Data
- Developer: AtlasAdapt (https://mcp.atlasadapt.com/)
- Muse status: Extra setup. Not in Muse's Connectors list yet. Muse can still use it: its page gives you a request to paste into Muse.
- Health: Working, 339ms, checked 2026-11-11T19:21:16Z
- Endpoint: https://mcp.atlasadapt.com/mcp
- Auth: Needs an access key; Pricing: unknown
- Screening: Screened, no issues found (2026-11-11T19:21:16Z)
- Source: Found in the official MCP Registry (com.atlasadapt/climate-resilience) https://registry.modelcontextprotocol.io/v0/servers?search=com.atlasadapt%2Fclimate-resilience

Connects to AtlasAdapt's climate risk and incentive engine. Muse can geocode an address, pull flood, wind, wildfire, heat and outage ratings with their public sources, price recommended upgrades, find grants and rebates, and compare payback across plans for one building or a portfolio.

Example request: "Is my house in a flood zone, and which upgrades would pay for themselves after rebates?"

How to connect: Not in Muse's Connectors list yet, but Muse can still use it. Paste this into Muse: "Use AtlasAdapt to help me. It is a free service with an MCP server at https://mcp.atlasadapt.com/mcp. It needs an API key from AtlasAdapt; ask me to enter it through your secure credential prompt. Ask me before you share anything with it." Muse asks before it shares anything with the app's site. Meta does not review apps used this way, so only use ones you trust. We tested this in the Muse app on September 24, 2026: Muse used an app's link directly this way and returned a live answer.

Tools:
- resolve_address: Geocode an address: coordinates, state, county (and US county FIPS), city, postcode, FEMA flood zone in the US, and how precise the match is (rooftop vs postcode centroid).
- assess_risk: Per-address climate hazard profile (flood, hurricane/wind, wildfire, heat, earthquake, power outage …) for the US, UK, Germany, France and Switzerland. Each hazard carries its rating and the public source it came from. A hazard that is absent was never modelled for that country —
- list_upgrades: The hardening and efficiency measures (upgrade ids) we hold priced cost rules for, by country and segment. Use these ids in estimate_plan and find_incentives.
- estimate_plan: For one building: the upgrades we RECOMMEND (commercial, when `upgrades` is omitted) or the ones you name; each upgrade's cost; the yearly loss per hazard without and with the plan (the owner's share, after deductible and insurer); incentives counted; net upfront cost; annual ben
- find_incentives: Which grants, tax credits, rebates and loans apply to this building and these upgrades, and for how much: `available` (counted), `contingent` (real but not the owner's, or event-triggered — never counted), `non_cash` (financing, unpriced). Each carries its ref, funding state, sta
- get_incentive: Full record for one programme, by the reference a person reads off a screen (US12c, FR33, DE12) or its id: grantor, amount rule, funding state, conditions, sources. Eligibility formulas, research sources and budget detail appear only if this key was granted them. Never add an inc
- compare_plans: Price 2 to 5 options (sets of upgrades) for the SAME building on the same basis and return them side by side: cost, incentives counted, net upfront, annual benefit, yearly loss avoided, payback, net over the horizon. Commercial buildings also get our recommended plan as an extra 
- estimate_portfolio: Price many buildings in one job (up to 500 sites, or the key's batch limit). Returns a job id at once; poll get_portfolio_job until status is done. Each site is billed as one request. `defaults` applies to every site and any site may override a field; a site takes the same fields
- get_portfolio_job: The status of a portfolio job (queued, running, done, failed, expired) and, once done, the per-site results and summary. Polling is free. Results are deleted after the job's expires_at.
- supply_chain_exposure: For a sole-source manufacturing or warehouse site run by a commercial or nonprofit body: how long one hazard event stops it, how long that stops its customer, and what that is worth. ONE event, not a yearly average: quote it with scenario.probability_pct. The downstream figure is
- my_usage: What this AtlasAdapt key may call, which countries it covers, and how many requests are left this month. Each tool call costs the REST calls behind it (usually one).

Screening checks:
- MCP handshake: pass (Answered in 339ms)
- Domain against threat feeds (Cloudflare security DNS): pass (mcp.atlasadapt.com not flagged)
- Published packages against the OSV malicious-package database: n/a (No npm or PyPI package published)
- Hidden instructions or invisible characters in tool text: pass (11 tools read, nothing found)
- Inputs asking for passwords, card numbers or seed phrases: pass (None found)
- Domain and redirects: pass (Domain registered 161 days ago)
- AI review of purpose and tool behavior: pass (tool descriptions include calculation rules addressed to the model, but they constrain accuracy rather than hide data)