Other · Remote MCP server

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

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

Visit Who Do I Call For? - Emergency Home-Service Router's website

What the MCP Registry states

The entry as published to the official MCP Registry (read 2026-10-04), latest version.

Registry name
io.github.woodydaniel/whodoicallfor
Version
1.1.0
Status
Active
Category
other
Transport
Streamable HTTP
Published
2026-08-12
Updated
2026-08-12
Publisher
woodydaniel (GitHub) · 2 servers with pages here
Namespace
Namespace verified by the MCP Registry via GitHub (github.com/woodydaniel) · how
Website
whodoicallfor.com/for-agents/
Source
Registry API entry

Remote endpoints

TransportURLHeaders declared
Streamable HTTPhttps://whodoicallfor.com/api/mcp/None

Live check

This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.

Reachable
Yes (HTTP 200)
Handshake
whodoicallfor 1.1.0 · protocol 2025-06-18
Tools discovered
Not listed - timeout: no answer within 15 s
Checked on
2026-10-05

How the live check works

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

Who Do I Call For? - Emergency Home-Service Router is a remote MCP server: there is nothing to install. Its endpoint is https://whodoicallfor.com/api/mcp/, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.

No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.

Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect

Site checks

The website's own root, whodoicallfor.com, was checked for the files that tell AI systems about a site.

FileResult
/llms.txtNo real file found
/.well-known/mcp.jsonReal file, HTTP 200 · 2026-10-04
/.well-known/ai-plugin.jsonNo real file found
/agents.jsonNo real file found

More from woodydaniel (GitHub)

All 2 →
ServerRunsEndpoint or package
FedTally - US Federal Contract IntelligenceUS federal contract recompetes with the incumbent named, awards by company, agency spend.Remote · HTTPLive check: ✓ handshakefedtally.com

More other servers

All 8,395 →
ServerRunsEndpoint or package
WhiteIntel - Ownership IntelligenceUBO, sanctions & ownership graph. 23 tools, 130.7M entities, 31 registries.Remote & Local · HTTP, stdioLive check: ✗ no handshakewhiteintel.dev
WhiteMagic - governed local memory for agent continuityGoverned local-first memory and continuity for AI agents - signed receipts, optional hosted lane.Remote & Local · HTTP, stdioLive check: ✓ handshakemcp.whitemagic.dev
WhitePactAI governance MCP server: trust scoring, guardrails, bias/hallucination detection, compliance.Remote & Local · HTTP, SSE, stdioLive check: sign-in requiredwhitepact-mcp-http.onrender.com
WHMCS MCP ServerConnect Claude, ChatGPT, and Cursor to live WHMCS over MCP.Local · HTTPOCI image (Docker): docker.io/daddariotech/whmcs-mcp:latest
Who GhoWHO GHO MCP - World Health Organization Global Health Observatory (free, no auth)Remote · HTTPLive check: ✓ handshakegateway.pipeworx.io
Who Gho MCP ServerWHO Global Health Observatory - 3,059 indicators across 194 member states.Remote & Local · HTTP, stdioLive check: ✓ handshakewho-gho.caseyjhand.com
Who MCPGlobal health indicators from the WHO Global Health Observatory. No key required.Local · stdionpm: who-mcp
Who Represents This AddressAI-operated: US address to districts, legislators, governor and mayor; Google Civic-compatible.Remote · HTTPLive check: ✗ no handshakewhorepresents.rjhsignaltech.workers.dev