Routes home emergencies to the right contractor with dispatch numbers, first steps, and typical costs.
Identifies the right emergency service to call for home problems like water damage, electrical issues, or HVAC failures. Provides who to contact in what order, immediate first steps, typical costs, and 24/7 dispatch numbers by US state.
Try asking Muse: "Water is coming through my ceiling in Florida, who should I call first?"
Source: Found in the official MCP Registry (io.github.woodydaniel/whodoicallfor) · First listed September 24, 2026
Each bar is one check, every 15 minutes. Green means it answered. Last checked 1 h ago.
What Muse can see: It does not ask you to sign in, so it cannot see your accounts. It only sees what Muse sends it from your request.
Before it acts: Read what Muse plans to do before you approve it, and remove the app from Muse when you stop using it.
musedirectory.ai is not part of Meta. More about how Muse handles your information
Not in Muse's Connectors list yet, but Muse can still use it. Copy the request below and paste it into Muse. 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.
https://whodoicallfor.com/api/mcp/Not in Muse's Connectors list yet. Muse can still use it: its page gives you a request to paste into Muse.
Response time at the last check: 912ms. Worked in 100% of checks over 30 days.
Screened, no issues found
Screening looks for known threats and hidden instructions at the time of the check, and runs again weekly and whenever the tool list changes. It cannot see the server's code, so only connect what you need and review what Muse asks to do. How screening works.
route_emergencyGiven a home emergency described in plain words (e.g. "water coming through my ceiling"), returns the matching situation(s): who to call and in what order, first steps, typical costs, and a 24/7 dispatch phone number when one is available for the service vertical. Optionally passget_scenarioFetch one situation in full: structured answer (who to call, costs, FAQ, sources) plus the complete step-by-step guide as markdown. Use category and slug values from route_emergency or list_scenarios.list_scenariosList every published situation with title, category, slug, and canonical URLs.https://whodoicallfor.com/api/mcp/Not in Muse's Connectors list yet, but Muse can still use it. Paste this into Muse: "Use Who Do I Call For to help me. It is a free service with an MCP server at https://whodoicallfor.com/api/mcp/. It does not need an API key. 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.
At the last check (September 28, 2026, 07:45 UTC) the endpoint was working, answering in 912ms. Over the last 7 days it answered 100% of health checks. It is checked every 15 minutes.
It was screened on September 24, 2026 with the result "screened, no issues found". Screening checks the domain against threat feeds and reads the tools for hidden instructions and requests for passwords or card numbers. It cannot see the server's code, so grant only the access you need.
It exposes 3 tools, including route_emergency, get_scenario, list_scenarios. For example, you could ask Muse: "Water is coming through my ceiling in Florida, who should I call first?"
This listing was added from public sources (Found in the official MCP Registry (io.github.woodydaniel/whodoicallfor)). If you build Who Do I Call For, claim it to correct the details and get your badge.
Paste this on your site or README. It always shows the latest check.
<a href="https://musedirectory.ai/connector/who-do-i-call-for"><img src="https://musedirectory.ai/badge/who-do-i-call-for.svg" alt="Who Do I Call For on musedirectory.ai" width="236" height="40"></a>