All servers · Markets & trading
Who Do I Call For? — Emergency Home-Service Router
io.github.woodydaniel/whodoicallfor · v1.1.0
Measured by MCP Station
| Last check | Reachable |
|---|---|
| Checked at | — |
| Check success 7 / 30 days | — |
| First-try success 30 days | — |
| Median response | — |
| Lookups 30 days | — |
| Authentication | No auth |
| MCP version | 2025-06-18 |
| Rank score | — |
| Declared risk | Read-only (all tools declare readOnlyHint) |
| Capabilities declared | tools |
| Tool definitions | 3 tools · with description 100% · input schema is an object 100% · read/destructive hints 100% |
Description written by the publisher, not verified
Routes home emergencies to the right trade: who to call in what order, first steps, sourced costs.
Connect
streamable-http · https://whodoicallfor.com/api/mcp/
claude mcp add --transport http whodoicallfor https://whodoicallfor.com/api/mcp/{
"mcpServers": {
"whodoicallfor": {
"url": "https://whodoicallfor.com/api/mcp/"
}
}
}Tools as reported by the server
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 pass a US state for regiget_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.
Website · JSON · Text for agents · Registry updated 2026-08-12