JOBFLOW

Ingested from the official MCP Registry

FastDrop pulled this entry from the official MCP Registry as ch.kulalabs.agents/jobflow and probed the endpoint. The maker did not submit it, so the outbound link is not endorsed and the description is not theirs.

If this is your server, claim the listing to edit it and take ownership. The registry index lists everything else still awaiting a probe.

Tools this endpoint exposes

Read directly from the endpoint on 3 Oct 2026. Not supplied by the maker.

• intent_match

  The first call: says whether the user's request is a flow JOBFLOW already runs. A match answers do_not_build true, the capabilities it touches and the next call; no match answers 404 OUT_OF_SCOPE. Nev

• discover

  Catalog, schemas, fees, gate, error codes; with a trade, the field knowledge for it. Never: —. Free.

• quote

  The hard platform fee for a capability before it is called, with what is left of the daily cap. Never: Estimate the value of a job. Free.

• compare

  Build-vs-buy next to the hard fee, the estimate marked NOT_A_QUOTE. Never: Present a token count or an estimate as a fact. Free.

• mandate_create

  Creates a mandate and the out-of-band approval link for the owner. Never: Activate production. Free.

• flow_configure

  The WhatsApp-to-payment flow for this mandate as a configuration proposal. Never: Bind a channel or an account without an approved mandate. Free.

• intake_classify

  Classifies a customer request and opens the flow (REQUEST → CLASSIFIED). Never: Set an emergency tariff. Platform fee CHF 0.05 per accepted call: quote first, then send quote_id, mandate_token and ide

• job_create

  Creates the order from the classification. Needs state CLASSIFIED. Never: Take a price from the request body. Platform fee CHF 0.05 per accepted call: quote first, then send quote_id, mandate_token an

Is this tool yours?

Claim this listing and we’ll verify ownership before handing it over.