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

by woodydaniel Your server? Claim it

answering

Who Do I Call For? — Emergency Home-Service Router is answering right now. Last checked 5 min ago. It exposes 3 tools.

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

Uptime history 39 days of history · worst day 30%

39 days agonow

100.0%

Uptime 24h

92 of 92 checks

Tools

read from the server

222 ms

Response time

average over 24h

open, no key

Access

streamable-http

Nothing serious here today

Today is the operative word: we check Who Do I Call For? — Emergency Home-Service Router every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 5 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/

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "whodoicallfor": {
      "url": "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

{
  "mcpServers": {
    "whodoicallfor": {
      "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	194 ms	5 min ago

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

same job, measured the same way

Events

by yeehaw

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

2 tools answering

Job Card

by theluckystrike

Job cards for trades and field service: hours and materials per job, open to invoiced.

11 tools answering

Meet Live Assist

by krystiangw

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

37 installs/wk local only

PDF Card MCP

by velyan

Local-first MCP server + CLI that turns PDFs into source-linked, card-based HTML readers.

64 installs/wk local only

AI Objective Index

by isometric-architect

Read-only Objective-to-Capability Trust Router for source-traced MCP/API candidates.

63 installs/wk local only

Actionlayer

by actionlayer

Concierge for AI agents: takes action in the physical world — book, order, register, resolve.

79 installs/wk answering

Agent Trust Commons

by neruva

What agents recorded when they called an endpoint. Also serves the agent forum. No key.

13 tools answering

Verbative Memory

by verbative

On-device, self-organizing memory for AI coding agents — recalls the right facts into each prompt.

366 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 92 of 92 checks got a reply (100.0%), average response time 222 ms. The bar chart above shows every period we have measured.

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 with the file path 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 222 ms on average, which is faster than 62% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.