eCommerce

steadywrk.dev

MCP server that provides storefront agent-readiness checks and field-service quote, estimate, and order tools.

1 endpoint6 known toolsFirst detected September 10, 2026Last detected September 10, 2026

ENDPOINT 1

https://steadywrk.dev/api/mcp

No auth detected

MCP server metadata

Name: app.steadywrk/mcp-dispatch
Version: 0.1.1

Capabilities

toolslogging

Server instructions

STEADYWRK Dispatch MCP over Streamable HTTP. Call tools/list to enumerate. Lead with agentic.readiness_probe — keyless storefront snapshot that finishes, with a Store Guard $149 CTA. Required argument: url (public storefront URL or domain). Example: POST https://steadywrk.app/api/mcp {"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"agentic.readiness_probe","arguments":{"url":"https://example.com"}}}. dispatch.quote and dispatch.order require the CLIENT to send its own integration key as x-api-key (or Authorization: Bearer); without one they return HTTP 401 with WWW-Authenticate and JSON-RPC error -32001. Self-serve: POST /api/mcp/oauth/register then POST /api/mcp/oauth/token. Self-serve machine credential, no human in the loop: POST https://steadywrk.app/api/mcp/oauth/register (RFC 7591 dynamic client registration), then POST https://steadywrk.app/api/mcp/oauth/token with grant_type=client_credentials to mint a Bearer token. Discovery: https://steadywrk.app/.well-known/oauth-protected-resource/api/mcp. hello@steadywrk.app still works for humans. A self-serve token is accepted by dispatch.quote but is NOT entitled to dispatch.order, which is the billable tool: it answers HTTP 402 payment_required (JSON-RPC -32002) until you are provisioned an integration key via hello@steadywrk.app. Keyless callers can use dispatch.estimate (public rate card). dispatch.evals is public, no-auth. Read its per-field provenance and methodology; it is self-reported, not an independent audit.

Known tools 6

agentic.readiness_probe

Free multi-surface storefront readiness snapshot (UCP/ACP discovery, product schema, robots, answer-engine maps).

Inferred read-only

dispatch.quote

Request a field-service quote by trade, location, and urgency.

Potential side effects

dispatch.estimate

Public modeled field-service price estimate using cited BLS wage data and disclosed model assumptions.

Inferred read-only

dispatch.order

Create a field-service order and return its status URL.

Potential side effects

dispatch.evals

Return the public evaluation document for a selected rolling window.

Inferred read-only

dispatch.index

Return the catalog of 8 dispatch trade verticals.

Potential side effects

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.app-steadywrk-mcp-dispatch]
url = "https://steadywrk.dev/api/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "app-steadywrk-mcp-dispatch": {
      "type": "http",
      "url": "https://steadywrk.dev/api/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: app-steadywrk-mcp-dispatch
Remote MCP URL: https://steadywrk.dev/api/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "app-steadywrk-mcp-dispatch": {
      "url": "https://steadywrk.dev/api/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "app-steadywrk-mcp-dispatch": {
      "type": "http",
      "url": "https://steadywrk.dev/api/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "app-steadywrk-mcp-dispatch",
  "transport": "streamable-http",
  "url": "https://steadywrk.dev/api/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.