mocop
Browse · Docs · Guide · Analyze

app.steadywrk/mcp-dispatch

MCP server by STEADYWRK · mcp

STEADYWRK Dispatch MCP over Streamable HTTP. Call tools/list to enumerate. Read the steadywrk://docs/quickstart resource for a working call per tool; prompts/list offers ready-made workflows. agentic.readiness_probe takes a public storefront URL or domain (argument: url), needs no key, and returns a dated snapshot, not an attested grade. Example call: 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. 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. For dispatch.quote: Over MCP, witho…

Endpoint: https://steadywrk.app/api/mcp

Verification: observed. Source: crawl.

Capabilities (13)

  • agentic.readiness_probe
  • dispatch.quote
  • dispatch.estimate
  • dispatch.order
  • dispatch.order_status
  • dispatch.evals
  • dispatch.index
  • acp.validate
  • ucp.validate
  • audit_storefront
  • price_a_job
About · Contact · Privacy