STEADYWRK Field Service Dispatch
REMOTE · STEADYWRK.APP · SCANNED SEP 25
Field service dispatch: instant quotes, tracked work orders, public evals. steadywrk.app
Available components
Recent critical change
Authorization (5 Sept 2026). See the changelog before you install this server.
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. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (dispatch.order). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability66
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 929 tokens (~154/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage76
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 18% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the STEADYWRK Field Service Dispatch MCP server?
STEADYWRK Field Service Dispatch is a hosted endpoint at https://steadywrk.app/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · steadywrk.app
claude mcp add --transport http app-steadywrk-mcp-dispatch 'https://steadywrk.app/api/mcp'
{
"mcpServers": {
"app-steadywrk-mcp-dispatch": {
"url": "https://steadywrk.app/api/mcp"
}
}
} {
"servers": {
"app-steadywrk-mcp-dispatch": {
"type": "http",
"url": "https://steadywrk.app/api/mcp"
}
}
} [mcp_servers.app-steadywrk-mcp-dispatch] url = "https://steadywrk.app/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"app-steadywrk-mcp-dispatch": {
"type": "remote",
"url": "https://steadywrk.app/api/mcp",
"enabled": true
}
}
} openclaw mcp add app-steadywrk-mcp-dispatch --url 'https://steadywrk.app/api/mcp' --transport streamable-http
mcp_servers:
app-steadywrk-mcp-dispatch:
url: "https://steadywrk.app/api/mcp" {
"McpServers": {
"app-steadywrk-mcp-dispatch": {
"Transport": "http",
"Url": "https://steadywrk.app/api/mcp"
}
}
} assistant mcp add app-steadywrk-mcp-dispatch -t streamable-http -u 'https://steadywrk.app/api/mcp'
{
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 16 Sept 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Tool “dispatch.quote” rewrote its description, which is the text the model reads security
- Schema quality: 179 → 154 ▲ functional
- 11 Sept 26 −1
- The server rewrote its instructions, which are the text every model session reads security
- Tool “dispatch.quote” rewrote its description, which is the text the model reads security
- 6 Sept 26 +2
- The server rewrote its instructions, which are the text every model session reads security
- Tool “dispatch.estimate” rewrote its description, which is the text the model reads security
- Tool “dispatch.evals” rewrote its description, which is the text the model reads security
- Tool “dispatch.order” rewrote its description, which is the text the model reads security
- Tool “dispatch.quote” rewrote its description, which is the text the model reads security
- Schema quality: 222 → 172 ▲ functional
- 5 Sept 26 0
- Authorization: unverified → fail ▼ critical
- Tool “dispatch.order” is now declared destructive security
- Tool “agentic.readiness_probe” now declares an output schema ▲ functional
- Tool “dispatch.estimate” now declares an output schema ▲ functional
- Tool “dispatch.evals” now declares an output schema ▲ functional
- Tool “dispatch.index” now declares an output schema ▲ functional
- Tool “dispatch.order” now declares an output schema ▲ functional
- Tool “dispatch.quote” now declares an output schema ▲ functional
- First check of Tool coverage: 100 functional
- Tool “agentic.readiness_probe” changed its title: Inspect storefront readiness cosmetic
- Tool “dispatch.estimate” changed its title: Estimate dispatch cost cosmetic
- Tool “dispatch.evals” changed its title: Read dispatch evaluations cosmetic
- Tool “dispatch.index” changed its title: Read the dispatch trade catalog cosmetic
- Tool “dispatch.order” changed its title: Create a dispatch work order cosmetic
- Tool “dispatch.quote” changed its title: Get a dispatch quote cosmetic
- 31 Aug 26 0
- Tool “dispatch.estimate” rewrote its description, which is the text the model reads security
- 27 Aug 26 75
- The server rewrote its instructions, which are the text every model session reads security
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 25 Sept 2026 · Probed https://steadywrk.app/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=steadywrk.app | CN=WE1,O=Google Trust Services,C=US | 20 Aug 2026 | 18 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 4687cb880741903a13fb1374c005d9be |
| SANs: steadywrk.app, *.steadywrk.app | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of steadywrk.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| steadywrk.app. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | accelerometer=(), autoplay=(), bluetooth=(), camera=(), display-capture=(), encrypted-media=(), fullscreen=(self), geolocation=(), gyroscope=(), hid=(), idle-detection=(), magnetometer=(), microphone=(self), midi=(), payment=(), picture-in-picture=(), publickey-credentials-get=(self), screen-wake-lock=(), serial=(), sync-xhr=(), usb=(), xr-spatial-tracking=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://steadywrk.app/api/mcp | Verified | 200 | |
| http (plaintext) | http://steadywrk.app/api/mcp | HTTPS enforced | 301 | https://steadywrk.app/api/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
agentic.readiness_probe Inspect storefront readiness ~68
Free multi-surface storefront readiness snapshot (UCP/ACP discovery, product schema, robots, answer-engine maps). Not an attested Store Guard grade. Response includes a Store Guard $149 CTA. No API key required.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Public storefront URL or domain |
Structured output declared, but exposes no named fields.
No examples provided.
dispatch.estimate Estimate dispatch cost ~109
Public modeled field-service price estimate using cited BLS wage data and disclosed model assumptions. Returns wage_basis and billed_estimate so callers can inspect the calculation and geographic basis. The response identifies estimates based on a national baseline and distinguishes model assumptions from observed prices. Use dispatch.quote with an accepted credential to request a quote. No API key required.
| Name | Type | Req | Description |
|---|---|---|---|
| location | object | yes | – |
| trade | string | yes | Trade code (plumbing, electrical, HVAC, etc.) |
| urgency | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
dispatch.evals Read dispatch evaluations ~64
Return the public evaluation document for a selected rolling window. Consult its per-field provenance and methodology to distinguish self-reported estimates, measurements, and unavailable fields. It is not an independent audit or a service-level guarantee. No API key required.
| Name | Type | Req | Description |
|---|---|---|---|
| period | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| estimated | boolean | yes | False only when goal-fulfillment rates are backed by fresh, sufficient production telemetry. |
| goal_fulfillment | object | yes | – |
| methodology | object | yes | Metric definitions, named-period window, source-class vocabulary. Never a sample size. |
| operational | object | yes | – |
| period | string | yes | – |
| provenance | object | yes | Per-field record of whether each published figure is measured or estimated. |
| schema_version | string | yes | – |
| trust_signals | object | yes | – |
No examples provided.
dispatch.index Read the dispatch trade catalog ~93
Return the catalog of 8 dispatch trade verticals. Per trade: the BLS OES hourly WAGE (medianRateDollars/p25/p75 — what a technician earns, NOT a price) alongside billedHourlyRateRoutineDollars, what a buyer pays hourly at routine urgency, derived by the same wage→billed transform dispatch.estimate uses. See the wage_vs_billed block. No API key required.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| model_assumptions | string | yes | – |
| note | string | yes | – |
| rate_model_version | string | yes | – |
| source_period | string | yes | – |
| trades | array | yes | – |
| updated_at | string | yes | – |
| wage_vs_billed | object | yes | – |
No examples provided.
dispatch.order Create a dispatch work order ~182
Create a field-service order and return its status URL. HTTP 201 returns a created order; HTTP 202 returns an order accepted_pending_fulfilment with fulfilled=false. Order creation requires a provisioned integration key through x-api-key. MCP also accepts that key through Authorization: Bearer; direct REST order creation requires x-api-key. A self-serve OAuth token authenticates but is not entitled to create orders: HTTP 402 payment_required (JSON-RPC -32002 over MCP). Anonymous callers receive HTTP 401 with WWW-Authenticate. Provisioning contact: hello@steadywrk.app.
| Name | Type | Req | Description |
|---|---|---|---|
| callback_url | string | – | – |
| description | string | yes | – |
| location | object | yes | – |
| nte_cents | integer | – | – |
| reference_id | string | – | – |
| trade | string | yes | – |
| urgency | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
dispatch.quote Get a dispatch quote ~153
Request a field-service quote by trade, location, and urgency. Returns availability and quote details when available. Accepts a provisioned integration key through x-api-key or, when OAuth is enabled, a scoped self-serve OAuth token through Authorization: Bearer. MCP also accepts the provisioned key through Authorization: Bearer. Request a key at hello@steadywrk.app. Anonymous callers receive HTTP 401 with WWW-Authenticate. Public modeled pricing is available through dispatch.estimate.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | – |
| location | object | yes | – |
| nte_cents | integer | – | – |
| trade | string | yes | Trade code (plumbing, electrical, HVAC, etc.) |
| urgency | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
What is the STEADYWRK Field Service Dispatch MCP server?
STEADYWRK Field Service Dispatch is an MCP server listed in the public MCP registry as app.steadywrk/mcp-dispatch. Field service dispatch: instant quotes, tracked work orders, public evals. steadywrk.app. This page covers its hosted endpoint (https://steadywrk.app/api/mcp).
Is the STEADYWRK Field Service Dispatch MCP server safe to use?
STEADYWRK Field Service Dispatch scores 77 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the STEADYWRK Field Service Dispatch MCP server expose?
STEADYWRK Field Service Dispatch exposes 6 tools: agentic.readiness_probe, dispatch.quote, dispatch.estimate, dispatch.order, dispatch.evals, dispatch.index. Their descriptions and schemas cost roughly 669 tokens of context every time the server is loaded.
Does the STEADYWRK Field Service Dispatch MCP server require authentication?
No. We connected to STEADYWRK Field Service Dispatch without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the STEADYWRK Field Service Dispatch MCP server still maintained?
STEADYWRK Field Service Dispatch is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.