Who Do I Call For? — Emergency Home-Service Router is a remote MCP server that gives an AI agent 3 tools, among them get_scenario, list_scenarios, route_emergency. It answers at https://whodoicallfor.com/api/mcp/ over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 6 of 6 times since 11 September 2026; the last check, on 24 October 2026, succeeded.
Routes home emergencies to the right trade: who to call in what order, first steps, sourced costs.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
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. Inputs: category, slug |
list_scenarios | List every published situation with title, category, slug, and canonical URLs. |
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 f Inputs: problem, state |
Every block below points at https://whodoicallfor.com/api/mcp/. Pick your client and copy.
claude mcp add --transport http who-do-i-call-for-emergency-home https://whodoicallfor.com/api/mcp/
{
"mcpServers": {
"who-do-i-call-for-emergency-home": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://whodoicallfor.com/api/mcp/"]
}
}
}{
"mcpServers": {
"who-do-i-call-for-emergency-home": {
"url": "https://whodoicallfor.com/api/mcp/"
}
}
}{
"servers": {
"who-do-i-call-for-emergency-home": {
"type": "http",
"url": "https://whodoicallfor.com/api/mcp/"
}
}
}{
"context_servers": {
"who-do-i-call-for-emergency-home": {
"url": "https://whodoicallfor.com/api/mcp/"
}
}
}{
"mcpServers": {
"who-do-i-call-for-emergency-home": {
"serverUrl": "https://whodoicallfor.com/api/mcp/"
}
}
}{
"mcpServers": {
"who-do-i-call-for-emergency-home": {
"url": "https://whodoicallfor.com/api/mcp/"
}
}
}name: Who Do I Call For? — Emergency Home-Service Router
version: 0.0.1
schema: v1
mcpServers:
- name: Who Do I Call For? — Emergency Home-Service Router
type: streamable-http
url: https://whodoicallfor.com/api/mcp/{
"mcpServers": {
"who-do-i-call-for-emergency-home": {
"httpUrl": "https://whodoicallfor.com/api/mcp/"
}
}
}{
"mcpServers": {
"who-do-i-call-for-emergency-home": {
"type": "http",
"url": "https://whodoicallfor.com/api/mcp/"
}
}
}{
"mcpServers": {
"who-do-i-call-for-emergency-home": {
"url": "https://whodoicallfor.com/api/mcp/"
}
}
}goose://extension?url=https%3A%2F%2Fwhodoicallfor.com%2Fapi%2Fmcp%2F&type=streamable_http&id=who-do-i-call-for-emergency-home&name=Who%20Do%20I%20Call%20For%3F%20%E2%80%94%20Emergency%20Home-Service%20Router
It answered our last check on 24 October 2026 in 176 ms. Over 6 checks since 11 September 2026 it answered 6. Status here comes from Neuronto's own probes, not from the publisher.
3, as returned by the server's own tools/list on 22 September 2026: get_scenario, list_scenarios, route_emergency.
It answered our last check on 24 October 2026 in 176 ms. Over 6 checks since 11 September 2026 it answered 6.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://whodoicallfor.com/api/mcp/. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: io.github.woodydaniel. Endpoint host: whodoicallfor.com. ARD identifier: urn:air:io.github.woodydaniel:mcp:whodoicallfor.
First indexed 10 September 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.