# Who Do I Call For Muse connector

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

## Who Do I Call For

Routes home emergencies to the right contractor with dispatch numbers, first steps, and typical costs.

- Record: https://musedirectory.ai/connector/who-do-i-call-for
- Category: Lifestyle
- Developer: Woody Daniel (https://whodoicallfor.com/for-agents/)
- 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, 912ms, checked 2026-09-28T07:45:53Z
- Endpoint: https://whodoicallfor.com/api/mcp/
- Auth: No account needed; Pricing: unknown
- Screening: Screened, no issues found (2026-09-24T04:50:49Z)
- Source: Found in the official MCP Registry (io.github.woodydaniel/whodoicallfor) https://registry.modelcontextprotocol.io/v0/servers?search=io.github.woodydaniel%2Fwhodoicallfor

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.

Example request: "Water is coming through my ceiling in Florida, who should I call first?"

How to connect: 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.

Tools:
- route_emergency: Given 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 pass
- get_scenario: Fetch 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_scenarios: List every published situation with title, category, slug, and canonical URLs.

Screening checks:
- MCP handshake: pass (Answered in 446ms)
- Domain against threat feeds (Cloudflare security DNS): pass (whodoicallfor.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 (3 tools read, nothing found)
- Inputs asking for passwords, card numbers or seed phrases: pass (None found)
- Domain and redirects: pass (Domain registered 44 days ago)
- AI review of purpose and tool behavior: pass (No concerns)