Skip to content

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

by woodydaniel · remote · no sign-in to list tools · v1.1.0 · published by GitHub user woodydaniel

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

Changes · 1
CompareRegistry entry

3 tools: 1 change things and 2 only read.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

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

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

3 tools

Changes things 1Claude Code: ask
  • route_emergencyGiven a home emergency described in plain words (e.g.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Route a home emergency
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
Only reads 2Claude Code: allow
  • get_scenarioFetch one situation in full: structured answer (who to call, costs, FAQ, sources) plus the complete step-by-step guide as markdown.No findings

    Why it is in this group

    • The name "get_scenario" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Get one situation in full
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • list_scenariosList every published situation with title, category, slug, and canonical URLs.No findings

    Why it is in this group

    • The name "list_scenarios" says "list": a word for reading.
    Description, as the server wrote it
    List every published situation with title, category, slug, and canonical URLs.

    Annotations the server declares

    • title: List all situations
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 1.1.0. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__whodoicallfor__get_scenario",
      "mcp__whodoicallfor__list_scenarios"
    ],
    "ask": [
      "mcp__whodoicallfor__route_emergency"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as whodoicallfor. Review it before you use it.