# STEADYWRK Field Service Dispatch (remote · steadywrk.app)

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

- Trust score: 61/100 (medium)
- Change this week: +7
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `steadywrk.app`: 61/100 (this document), [markdown](https://verifymcp.io/servers/app-steadywrk-mcp-dispatch/api-mcp.md), [page](https://verifymcp.io/servers/app-steadywrk-mcp-dispatch/api-mcp)

## Channel facts

- Endpoint: `https://steadywrk.app/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.1`

## 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-03.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - 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**: 49/100
  - AI-judged instruction clarity (fair).
  - Tool/resource definitions use about 352 tokens (~88/item across 4 items; 4 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 69/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 8% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http app-steadywrk-mcp-dispatch https://steadywrk.app/api/mcp
```

### Codex

```toml
[mcp_servers.app-steadywrk-mcp-dispatch]
url = "https://steadywrk.app/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "app-steadywrk-mcp-dispatch": {
      "type": "remote",
      "url": "https://steadywrk.app/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add app-steadywrk-mcp-dispatch --url https://steadywrk.app/api/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  app-steadywrk-mcp-dispatch:
    url: "https://steadywrk.app/api/mcp"
```

### Other

```json
{
  "mcpServers": {
    "app-steadywrk-mcp-dispatch": {
      "type": "http",
      "url": "https://steadywrk.app/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-03 (score 61, +1)

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

### 2026-08-01 (score 60, +1)

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

### 2026-07-31 (score 59, +3)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 56, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-28 (score 55, +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-07-27 (score 54, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 53)

First indexed and scored.

## MCP tools (4)

### `dispatch.quote` (~93 tokens)

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.

Input parameters:

- `description` (string)
- `location` (object, required)
- `nte_cents` (integer)
- `trade` (string, required): Trade code (plumbing, electrical, HVAC, etc.)
- `urgency` (string)

### `dispatch.order` (~90 tokens)

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.

Input parameters:

- `callback_url` (string)
- `description` (string, required)
- `location` (object, required)
- `nte_cents` (integer)
- `reference_id` (string)
- `trade` (string, required)
- `urgency` (string)

### `dispatch.evals` (~52 tokens)

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.

Input parameters:

- `period` (string)

### `dispatch.index` (~61 tokens)

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.

## Diagnostics

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

## Score history

- 2026-08-03: 61
- 2026-08-02: 60
- 2026-08-01: 60
- 2026-07-31: 59
- 2026-07-30: 56
- 2026-07-29: 55
- 2026-07-28: 55
- 2026-07-27: 54
- 2026-07-26: 53

## Links

- Remote endpoint: https://steadywrk.app/api/mcp
- Website: https://steadywrk.app/developers/mcp
- Changelog RSS feed: https://verifymcp.io/servers/app-steadywrk-mcp-dispatch/api-mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/app-steadywrk-mcp-dispatch/api-mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/app-steadywrk-mcp-dispatch/api-mcp