mcpbeat

STEADYWRK Field Service Dispatch MCP Server

app.steadywrk/mcp-dispatch
answering

STEADYWRK Field Service Dispatch is answering right now. Last checked 12 min ago. It exposes 4 tools.

Field service dispatch: instant quotes, tracked work orders, public evals. steadywrk.app

The linked repository no longer exists on GitHub — it was deleted or made private.

Uptime history 40 hours of history
40 hours agonow
100.0%
Uptime 24h
91 of 91 checks
4
Tools
read from the server
428 ms
Response time
average over 24h
open, no key
Access
streamable-http

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 12 min ago.

run in your terminal
claude mcp add mcp-dispatch --transport http https://steadywrk.app/api/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "mcp-dispatch": {
      "url": "https://steadywrk.app/api/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.mcp-dispatch]
url = "https://steadywrk.app/api/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "mcp-dispatch": {
      "url": "https://steadywrk.app/api/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "mcp-dispatch": {
      "url": "https://steadywrk.app/api/mcp"
    }
  }
}

Available tools 4

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

dispatch
dispatch.evals
Return the public evals dashboard: completion rate, NTE variance, dispatch latency, human-override rate, and operational counts for the selected rolling window. No API key required.
dispatch.index
Return the catalog of 8 dispatch trade verticals with baseline model rates (routine urgency, 1.0× multiplier). Rates are STEADYWRK model rates informed by BLS OES data — not BLS verbatim. No API key required.
dispatch.order
Create a dispatch work order. Auto-matches a contractor from the active pool and returns a tracked order with masked contractor reference and status URL.
dispatch.quote
Return an instant dispatch quote for a field-service job. Accepts trade + location + urgency and returns matched contractor, estimated cost in cents, ETA tier, and valid_for_minutes.

Endpoints

URLTransportStateLatencyChecked
https://steadywrk.app/api/mcp streamable-http answering 461 ms 12 min ago

STEADYWRK Field Service Dispatch — questions

Answers built from our own checks of this server.

What can STEADYWRK Field Service Dispatch do?
It exposes 4 tools, read directly from the server on our last check. Among them: dispatch.evals, dispatch.index, dispatch.order, dispatch.quote. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is STEADYWRK Field Service Dispatch working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 428 ms. The bar chart above shows every period we have measured.
Is STEADYWRK Field Service Dispatch still maintained?
The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.
How do I connect STEADYWRK Field Service Dispatch?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does STEADYWRK Field Service Dispatch need an API key?
No. STEADYWRK Field Service Dispatch completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 4 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is STEADYWRK Field Service Dispatch?
It answers our handshake in 428 ms on average, which is faster than 30% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.