Skip to content

STEADYWRK Agentic Readiness Probe, Store Guard and Dispatch MCP server

app.steadywrk/mcp-dispatchsteadywrk.appstreamable-httpv0.3.0Scanned

Keyless storefront readiness probe linking a Store Guard audit, plus dispatch estimates and quotes.

9 tools: 1 can delete or cancel things, 3 change things and 5 only read.

Tools: 1 delete, 0 irreversible, 3 write, 5 read.
  • Reads private data · 1
  • Reads text others write · 5
  • Can send data out · 3
  • 2 findings

Tools listed without sign-in. Remote posture

Anlyon alternative

4 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

Its sign-in does not let Anlyon set up an OAuth client on its own, so there is no link to it here.

What the STEADYWRK Agentic Readiness Probe, Store Guard and Dispatch MCP server can do

The STEADYWRK Agentic Readiness Probe, Store Guard and Dispatch MCP server is published by steadywrk.app, a domain the MCP Registry verified. It has 9 tools. It can delete or cancel things (1 tool: dispatch.order) and create or change data (3 tools: agentic.readiness_probe, dispatch.quote and dispatch.estimate). 5 tools only read.

1 tool reads private data (dispatch.evals); 5 tools bring in text other people can write (agentic.readiness_probe, dispatch.quote, dispatch.order and 2 more); 3 tools can send data out of your system (agentic.readiness_probe, acp.validate and ucp.validate). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.

The fixed checks matched 2 findings (annotation-conflict and credentials-mention). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 12, 2026, version 0.3.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

9 tools

Deletes or cancels 1Claude Code: deny
  • dispatch.orderCreate a field-service order and return its status URL.Reads text others writeNo findings

    Why it is in this group

    • The description's first verb is "create": a word for a change.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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. To be provisioned, POST JSON to https://steadywrk.app/api/integration-key-request or use https://steadywrk.app/developers/keys and a person reviews each request. Email fallback: hello@steadywrk.app.

    Annotations the server declares

    • title: Create a dispatch work order
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: true
Changes things 3Claude Code: ask
  • agentic.readiness_probeRun a one-time readiness check on a public storefront and return a score, a grade and per-check results (UCP and ACP discovery files, product schema, robots rules, answer-engine ma…Reads text others writeCan send data out1 finding

    Why it is in this group

    • The description's first verb is "run": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.

    Findings

    • Warn

      The server marks "agentic.readiness_probe" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The description's first verb is "run": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Run a one-time readiness check on a public storefront and return a score, a grade and per-check results (UCP and ACP discovery files, product schema, robots rules, answer-engine maps). The result is a dated snapshot of public files, not an attested Store Guard grade. Input: url, a public storefront URL or domain (up to 255 characters; local, private and numeric hosts are refused). Each run may store a public snapshot record, at most one per host per UTC day, linked in the response. The response also lists Store Guard and sample-report links under `next`. Rate-limited per caller. No API key required.

    Annotations the server declares

    • title: Inspect storefront readiness
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • dispatch.estimatePublic modeled field-service price estimate with cited BLS wage benchmarks.1 finding

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Info

      The description mentions "credential".

      Matched text

      description: "...es. Use dispatch.quote with an accepted credential to request a quote. No API key required..."

      What this check looks for
    Description, as the server wrote it
    Public modeled field-service price estimate with cited BLS wage benchmarks. Returns customer hourly rates, line items, ranges and a total alongside geographic scope and source provenance. Model estimates are not observed transaction prices or binding quotes. Use dispatch.quote with an accepted credential to request a quote. No API key required.

    Annotations the server declares

    • title: Estimate dispatch cost
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • dispatch.quoteRequest a field-service quote by trade, location, and urgency.Reads text others writeNo findings

    Why it is in this group

    • The description's first verb is "request": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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 an integration key: POST JSON to https://steadywrk.app/api/integration-key-request (GET it for the fields), or use https://steadywrk.app/developers/keys and a person reviews each request. Email fallback: hello@steadywrk.app. Over MCP, without a key, add contact_email (and optionally contact_name and company) and the request is filed for a person to answer by email. Other anonymous callers receive HTTP 401 with WWW-Authenticate. Public modeled pricing is available through dispatch.estimate.

    Annotations the server declares

    • title: Get a dispatch quote
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
Only reads 5Show 5 read-only tools
  • acp.validateFree validator for a store's Agentic Commerce Protocol (ACP) discovery file at /.well-known/acp.json.Reads text others writeCan send data outNo findings

    Why it is in this group

    • The name "acp.validate" says "validate": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.

    Claude Code: ask, because it is tagged outbound.

    Description, as the server wrote it
    Free validator for a store's Agentic Commerce Protocol (ACP) discovery file at /.well-known/acp.json. Pass url to fetch a public store's file, or document to check pasted JSON. Returns a verdict, every rule result, and a fix list: each failed rule with the change that fixes it. Reads one public file, stores nothing, calls no checkout endpoint. No API key required.

    Annotations the server declares

    • title: Validate a store's ACP discovery file
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • dispatch.evalsReturn the public evaluation document for a selected rolling window.Reads private dataNo findings

    Why it is in this group

    • The description's first verb is "return": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "return" and "document": it reads documents.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Read dispatch evaluations
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • dispatch.indexReturn the catalog of 8 dispatch trade verticals.No findings

    Why it is in this group

    • The description's first verb is "return": a word for reading.
    Description, as the server wrote it
    Return the catalog of 8 dispatch trade verticals. Per trade: the BLS OES hourly WAGE benchmark (medianRateDollars/p25/p75 — what a technician earns, NOT a price) alongside billedHourlyRateRoutineDollars, a modeled customer hourly estimate at routine urgency. Estimates are not observed transaction prices or binding quotes. No API key required.

    Annotations the server declares

    • title: Read the dispatch trade catalog
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • dispatch.order_statusReturn the current state of a work order created by dispatch.order: status, assignment, quote and timestamps.No findings

    Why it is in this group

    • The name "dispatch.order_status" says "status": a word for reading.
    Description, as the server wrote it
    Return the current state of a work order created by dispatch.order: status, assignment, quote and timestamps. Same key as dispatch.order (the order's status_url, served over MCP). A self-serve OAuth token cannot have created an order, so it receives HTTP 402 payment_required (JSON-RPC -32002). Anonymous callers receive HTTP 401 with WWW-Authenticate. To be provisioned, POST JSON to https://steadywrk.app/api/integration-key-request or use https://steadywrk.app/developers/keys and a person reviews each request. Email fallback: hello@steadywrk.app.

    Annotations the server declares

    • title: Read a dispatch work order
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • ucp.validateFree validator for a store's Universal Commerce Protocol (UCP) discovery file at /.well-known/ucp.Reads text others writeCan send data outNo findings

    Why it is in this group

    • The name "ucp.validate" says "validate": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.

    Claude Code: ask, because it is tagged outbound.

    Description, as the server wrote it
    Free validator for a store's Universal Commerce Protocol (UCP) discovery file at /.well-known/ucp. Pass url to fetch a public store's file, or document to check pasted JSON. Returns a verdict, every rule result, and a fix list: each failed rule with the change that fixes it. Reads one public file, stores nothing, calls no checkout endpoint. No API key required.

    Annotations the server declares

    • title: Validate a store's UCP discovery file
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

15 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 1 private-data tool breaks every one.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write5
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out3
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
deny to break every path
{
  "permissions": {
    "deny": [
      "mcp__dispatch__dispatch_evals"
    ]
  }
}

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:30 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
4
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://steadywrk.app/.well-known/oauth-protected-resource
Authorization servers
https://clerk.steadywrk.app
Legacy HTTP+SSE transport
no
Dynamic client registration
no
Client ID metadata documents
no
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 4 tools that change things (1 destructive, 3 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://steadywrk.app/api/mcp: tools/list returned 9 tools to an anonymous client, including dispatch.order (destructive), agentic.readiness_probe (write), dispatch.quote (write), dispatch.estimate (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

1 warn1 info
  • The server marks "agentic.readiness_probe" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The description's first verb is "run": a word for a change.

    What this check looks for
  • The description mentions "credential".

    Matched text

    description: "...es. Use dispatch.quote with an accepted credential to request a quote. No API key required..."

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools1 changed.~1 changedView diff

Install

Pinned to version 0.3.0. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__dispatch__dispatch_order_status",
      "mcp__dispatch__dispatch_evals",
      "mcp__dispatch__dispatch_index"
    ],
    "ask": [
      "mcp__dispatch__agentic_readiness_probe",
      "mcp__dispatch__dispatch_quote",
      "mcp__dispatch__dispatch_estimate",
      "mcp__dispatch__acp_validate",
      "mcp__dispatch__ucp_validate"
    ],
    "deny": [
      "mcp__dispatch__dispatch_order"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as dispatch. Review it before you use it.

Capability tags behind 6 rules
  • mcp__dispatch__agentic_readiness_probe untrusted-input, outbound
  • mcp__dispatch__dispatch_quote untrusted-input
  • mcp__dispatch__dispatch_order untrusted-input
  • mcp__dispatch__dispatch_evals private-data
  • mcp__dispatch__acp_validate untrusted-input, outbound
  • mcp__dispatch__ucp_validate untrusted-input, outbound

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/app.steadywrk/mcp-dispatch/verify?hash=48a7bd5f228485a6c8a6835c65f1f16179330f7c7ac0e29b8362a82f9346cca8" | jq -e '.changed == false'

Pinned hash 48a7bd5f2284, from Nov 12, 2026, 03:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/app.steadywrk/mcp-dispatch/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for app.steadywrk/mcp-dispatch
[![Anlyon Radar](https://radar.anlyon.com/badge/app.steadywrk/mcp-dispatch.svg)](https://radar.anlyon.com/servers/app.steadywrk/mcp-dispatch)

Source: MCP Registry. Synced Oct 21, 2026, 17:45 UTC.

STEADYWRK Agentic Readiness Probe, Store Guard and Dispatch MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the STEADYWRK Agentic Readiness Probe, Store Guard and Dispatch MCP server safe?

No scan can promise that. What its definitions show: 9 tools, 4 of which can change, send or delete something, and 2 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the STEADYWRK Agentic Readiness Probe, Store Guard and Dispatch MCP server delete data?

Yes. 1 tool can delete, cancel or revoke something: dispatch.order.

Can the STEADYWRK Agentic Readiness Probe, Store Guard and Dispatch MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the STEADYWRK Agentic Readiness Probe, Store Guard and Dispatch MCP server have?

9 tools: 1 destructive, 3 write, 5 read. dispatch.order, agentic.readiness_probe, dispatch.quote, dispatch.estimate, dispatch.order_status, dispatch.evals, dispatch.index, acp.validate and 1 more.

Does the STEADYWRK Agentic Readiness Probe, Store Guard and Dispatch MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the STEADYWRK Agentic Readiness Probe, Store Guard and Dispatch MCP server send data to outside services?

3 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): agentic.readiness_probe, acp.validate and ucp.validate.

Has the STEADYWRK Agentic Readiness Probe, Store Guard and Dispatch MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Oct 30, 2026. Every change is on this page and in its Atom feed.