A remote MCP server that routes home emergencies to the right trade, with call order, first steps, typical costs and dispatch numbers.
What you can do
Route a home emergency described in plain words to matching situations, with who to call and in what order, first steps, typical costs and a 24/7 dispatch phone number where available, optionally narrowed by US state. Fetch one situation in full, including a structured answer with costs, FAQ and sources plus a step-by-step guide in markdown. List every published situation with title, category, slug and canonical URLs.
When to use it
Useful when someone describes a home problem and needs to know which trade to call, in what order, what to do first, and roughly what it should cost.
Requirements
A remote streamable HTTP endpoint; no package, account, API key or header is declared.
Before you install
It returns referral and cost information, including phone numbers, which may vary by state and should be verified; it does not perform repairs or bookings itself.
Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.woodydaniel%2Fwhodoicallfor/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.
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.
Parametersstateproblemrequired
get_scenario
Get one situation in full
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.
Parametersslugrequiredcategoryrequired
list_scenarios
List all situations
List every published situation with title, category, slug, and canonical URLs.
Takes no parameters.
Version history
1
v1.1.0LatestSep 16, 2026
Score
83%
83% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
Reached in the last 30 daysRequired25 pts
Auth declaredRequired10 pts
Tools listedRequired15 pts
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.