MCP

Install the MCP package in your project:

npm install @soterias/mcp-server@0.1.0-rc.5
npx --no-install soterias-mcp --help

The trusted application selects its configured native host, procedure, separate verifier and environment. Import createProcedureMcpFactory from @soterias/mcp-server/procedures and listenProcedureHttp from @soterias/mcp-server/procedure-http. Keep transport credentials in the operator/proxy setup, and reviewer keys outside the agent.

The procedure surface exposes start_procedure, resume_procedure, supply_procedure_model, get_procedure_outcome and get_procedure_receipt. An agent cannot submit another graph, enroll authority or approve an operation with a boolean. Signed approval is checked afresh by Rust.

The host's trusted review handoff closes its journal owner, displays the exact pending operation on a separate reviewer surface, then attaches a fresh owner at the acknowledged checkpoint. It is not an MCP signing tool.

Download the complete real HTTP protocol example and recipes. Follow disposable accounting setup first. The probe uses explicit automated confirmation only for fresh UNIT authorities; it is not physical-human proof.

Claude Code

After the operator starts the authenticated host and writes the private proxy configuration and pinned tool-discovery digest:

claude mcp add --transport stdio --scope local soterias -- npx --no-install soterias-mcp proxy /absolute/private/proxy.json

Hermes and other stdio MCP clients can launch the same proxy command with its absolute configuration path. Generic protocol checks and a connected client do not prove a full model-driven named-agent workflow. Full Claude Code/Hermes workflow acceptance remains open. Cancellation or a lost response never authorizes retrying an uncertain effect.