# Woodydaniel Whodoicallfor MCP server

Source: https://glimind.com/server/mcp-registry%2Fio.github.woodydaniel%2Fwhodoicallfor
Registry id: `mcp-registry/io.github.woodydaniel/whodoicallfor`
Status: live (checked 2026-10-27T01:45:08.476Z)

## Verdict

Woodydaniel Whodoicallfor MCP server answered 99.97% of Glimind's liveness checks over 30 days, better than 42% of MCP servers, with 418 ms median handshake and 1 outage in 90 days. Its agent-readiness grade is A (100/100) across 3 tools, costing an agent about 352 tokens to load. Checked every few minutes; no tool is ever called.

## Measurements (30 days)

| Metric | Value | Better than |
|---|---|---|
| Uptime, 30 days | 99.97% | 42% of MCP servers |
| Median handshake latency | 418 ms | 54% of MCP servers |
| p95 handshake latency | 2469 ms | — |
| Checks in 30 days | 4,973 | — |
| Outages, 90 days | 1 | — |
| Median recovery | 7 min | — |
| Agent-readiness score | 100/100 (A) | 94% of MCP servers |
| Tools | 3 | — |
| Tool-list size for an agent | ~352 tokens | 93% of MCP servers |
| Days observed | 29 | — |

## Install

```json
{
  "mcpServers": {
    "woodydaniel-whodoicallfor-mcp-server": {
      "type": "http",
      "url": "https://whodoicallfor.com/api/mcp/"
    }
  }
}
```

Claude Code:

```sh
claude mcp add --transport http woodydaniel-whodoicallfor-mcp-server https://whodoicallfor.com/api/mcp/
```

## Tools (3)

- `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
- `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, firs

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.