Who Do I Call For? — Emergency Home-Service Router MCP Server

by woodydaniel Your server? Claim it

not responding

Who Do I Call For? — Emergency Home-Service Router is listed as active in the registry but did not answer our last check. It exposes 3 tools.

Routes home emergencies to the right trade: who to call in what order, first steps, sourced costs.

Uptime history 89 days of history · worst day 30%

89 days agonow

59.3%

Uptime 24h

54 of 91 checks

Tools

read from the server

249 ms

Response time

average over 24h

open, no key

Access

streamable-http

Who Do I Call For? — Emergency Home-Service Router does not always answer

Over the last week it answered 80.9% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 7 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add whodoicallfor --transport http https://whodoicallfor.com/api/mcp/

Settings → Connectors → Add custom connector, then paste this address

https://whodoicallfor.com/api/mcp/

~/.codex/config.toml

[mcp_servers.whodoicallfor]
url = "https://whodoicallfor.com/api/mcp/"

.cursor/mcp.json

{
  "mcpServers": {
    "whodoicallfor": {
      "url": "https://whodoicallfor.com/api/mcp/"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "whodoicallfor": {
      "type": "http",
      "url": "https://whodoicallfor.com/api/mcp/"
    }
  }
}

Available tools 3

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

route

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 region-aware dispatch numbers.

scenario

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.

scenarios

list_scenarios

List every published situation with title, category, slug, and canonical URLs.

Endpoints

URL	Transport	State	Latency	Checked
https://whodoicallfor.com/api/mcp/	streamable-http	answering	86 ms	7 min ago

Alternatives to Who Do I Call For? — Emergency Home-Service Router

same job, measured the same way

forai.tools — let your agent find the right tool

by forai

Lets your agent find the right MCP server, tool or service for a task, in one call. Ads labelled.

1 tools answering

Events

by yeehaw

Agent-first Austin events concierge — fresh, sourced answers to what's happening in Austin.

2 tools answering

Rural Home Pros

by ruralhomepros

US well drillers and septic contractors: services, emergency service, estimates, with sources.

5 tools answering

Still Roach token check

by stillroach

Send the roach in first: Solana token holder checks for agents. Pay per call, no key.

7 tools answering

MSG91

by msg91-mcp

Find and call the right MSG91 API for SMS, OTP, WhatsApp, Email and Voice.

3 tools answering

AI Home Services Booking

by aihomeservices

Agent-first booking of home-service contractors in Canada and the US: quotes, availability, booking.

3 tools answering

PHION Task Router

by phion

Find the best eligible service for an agent task through one task-first MCP tool.

135 tools answering

Meet Live Assist

by krystiangw

Your own agent inside a live Google Meet or Zoom call. Local-first, no hosted service.

52 installs/wk local only

Who Do I Call For? — Emergency Home-Service Router — questions

Answers built from our own checks of this server.

What can Who Do I Call For? — Emergency Home-Service Router do?

It exposes 3 tools, read directly from the server on our last check. Among them: get_scenario, list_scenarios, route_emergency. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Who Do I Call For? — Emergency Home-Service Router working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 54 of 91 checks got a reply (59.3%), average response time 249 ms. The bar chart above shows every period we have measured.

The registry lists Who Do I Call For? — Emergency Home-Service Router as active — why does it not respond?

The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.

How do I connect Who Do I Call For? — Emergency Home-Service Router?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Who Do I Call For? — Emergency Home-Service Router need an API key?

No. Who Do I Call For? — Emergency Home-Service Router completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 3 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Who Do I Call For? — Emergency Home-Service Router?

It answers our handshake in 249 ms on average, which is faster than 55% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.