# Who Do I Call For? — Emergency Home-Service Router (remote · whodoicallfor.com)

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

- Trust score: 74/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-15

## Components

- remote · `whodoicallfor.com`: 74/100 (this document), [markdown](https://verifymcp.io/servers/woodydaniel-whodoicallfor/api-mcp.md), [page](https://verifymcp.io/servers/woodydaniel-whodoicallfor/api-mcp)

## Channel facts

- Endpoint: `https://whodoicallfor.com/api/mcp/`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-15.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 83/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 294 tokens (~98/item across 3 items; 3 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 13/100
  - Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### Claude

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

### Codex

```toml
[mcp_servers.woodydaniel-whodoicallfor]
url = "https://whodoicallfor.com/api/mcp/"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "woodydaniel-whodoicallfor": {
      "type": "remote",
      "url": "https://whodoicallfor.com/api/mcp/",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add woodydaniel-whodoicallfor --url https://whodoicallfor.com/api/mcp/ --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  woodydaniel-whodoicallfor:
    url: "https://whodoicallfor.com/api/mcp/"
```

### Other

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

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-15 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-13 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-12 (score 72, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-08-11 (score 72)

First indexed and scored.

## MCP tools (3)

### `route_emergency` (~114 tokens)

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.

Input parameters:

- `problem` (string, required): The user's problem in plain words
- `state` (string): Optional US state code or name, e.g. "FL" or "Florida"

Output parameters:

- `categories` (array)
- `matches` (array): Matching situations, best first; empty when no confident match
- `note` (string)
- `state` (string|null): US state code the numbers were matched against
- `triage_url` (string)

### `get_scenario` (~86 tokens)

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.

Input parameters:

- `category` (string, required): Category slug, e.g. "water"
- `slug` (string, required): Scenario slug, e.g. "ceiling-leaking"

Output parameters:

- `body_markdown` (string): The full step-by-step guide as markdown
- `category` (string)
- `costs` (array)
- `description` (string)
- `faq` (array)
- `json_url` (string)
- `recommended_call` (object|null)
- `sources` (array)
- `title` (string)
- `tldr` (string)
- `updated` (string)
- `url` (string)
- `vertical` (string|null)
- `who_to_call` (array)

### `list_scenarios` (~25 tokens)

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

Output parameters:

- `count` (number)
- `scenarios` (array)
- `site` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/woodydaniel-whodoicallfor/api-mcp#diagnostics

## Score history

- 2026-08-15: 74
- 2026-08-14: 73
- 2026-08-13: 73
- 2026-08-12: 72
- 2026-08-11: 72

## Links

- Remote endpoint: https://whodoicallfor.com/api/mcp/
- Website: https://whodoicallfor.com/for-agents/
- Changelog RSS feed: https://verifymcp.io/servers/woodydaniel-whodoicallfor/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/woodydaniel-whodoicallfor/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/woodydaniel-whodoicallfor/api-mcp