io.github.woodydaniel/whodoicallfor · v1.1.0 · ecommerce
Who Do I Call For? — Emergency Home-Service Router is healthy: it completed an MCP handshake in 752 ms and exposes 3 tools.
Routes home emergencies to the right trade: who to call in what order, first steps, sourced costs.
Endpoint: https://whodoicallfor.com/api/mcp/ (streamable-http)
No repository listed · Website · JSON · Add to my inventory
| Users (last 30 days) | 0 |
| Handshake | Healthy |
| Auth needed | None |
| Tool count | 3 |
| Latency | 752 ms |
| Last checked (UTC) | 2026-10-15T11:25:14.718Z |
| Checked (UTC) | Status | Latency | Error |
|---|---|---|---|
| 2026-10-15T11:25:14.718Z | Healthy | 752 |
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 a US state for regi |
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. |