list_rails
Returns PacketOps and DiligenceOps contracts, required fields, sample package links, and return package targets.
MCP Server Wrapper v1
Agents use Wever Labs as an MCP tool surface.
The wrapper exposes the active rail path through JSON-RPC tool calls: list rails, quote a run, create a payment challenge, start a rail run, check status, fetch the return package, record the receipt, and validate a production write.
initializetools/listtools/callstatusreturnreceiptwrite gate
Tool surface
The rails no longer need a human browser.
Agents can discover the available tools with tools/list, then call the same operating sequence used by Agent Use Pack, Production Write Gate, and Customer Production Runs.
quote_run
Returns rail key, package level, amount, currency, accepted payment methods, and expiration.
create_payment_challenge
Returns a payment-required object with run ID, accepted methods, status URL, and receipt requirement.
start_rail_run
Starts a sandbox or payment-bound run with idempotency key, payment reference, status URL, and return package ID.
get_run_status
Returns run state, payment state, receipt state, next action, and return package URL.
fetch_return_package
Returns output fields, proof fields, attestation path, and callback payload.
record_receipt
Binds run ID, payment reference, return package ID, fee event, receipt hash, and signature state.
validate_production_write
Checks idempotency, rail, target surface, scope, HTTPS callback, and returns accepted or rejected write state.
execute_first_paid_production_run
Completes one paid PacketOps or DiligenceOps proof run with payment reference, return package, receipt, proof hash, and completion signature.
MCP call sequence
Use the rail without guessing the site.
Initialize, list tools, call the tool, read the structured result. The response carries the next action so the calling agent can continue through quote, challenge, run, return package, and receipt.
Production boundary
Direct tool use does not remove the gate.
Production calls still require the same sober shape: scoped key when persistence is enabled, idempotency key, allowed rail, HTTPS callback when present, and audit record.
Use the MCP surface
Agents can now call the Wever Labs rails directly.
Start with tools/list. Then call quote_run, create_payment_challenge, and start_rail_run. The work still returns as a proof-backed package with a receipt trail.