Who Do I Call For? — Emergency Home-Service Router
Routes home emergencies to the right trade: who to call in what order, first steps, sourced costs.
Connect Remote server
claude mcp add --transport http whodoicallfor https://whodoicallfor.com/api/mcp/
{
"mcpServers": {
"whodoicallfor": {
"url": "https://whodoicallfor.com/api/mcp/"
}
}
}
{
"servers": {
"whodoicallfor": {
"type": "http",
"url": "https://whodoicallfor.com/api/mcp/"
}
}
}
Settings > Connectors > Add custom connector
URL: https://whodoicallfor.com/api/mcp/
Tools 3 found in our last check
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 pas…
get_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.
Details
| Endpoint | https://whodoicallfor.com/api/mcp/ (Streamable HTTP) |
| First published | 12 Aug 2026 |
| Last updated | 12 Aug 2026 |
| Registry name | io.github.woodydaniel/whodoicallfor |
More other servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.
