MCP

Connect to hosted read-only tools or run a local server with an explicit authority profile.

Hosted Read-Only MCP

Connect any Streamable HTTP MCP client to:

https://mcp.peer.xyz/mcp

The hosted server is stateless and read-only. It accepts no signing material and never broadcasts. Check service health at:

https://mcp.peer.xyz/health

Local MCP

Use stdio when you need local configuration, custody-separated Cash tools, or full operator authority:

peer mcp --profile read-only
peer mcp --profile cash
peer mcp --profile full

peer mcp uses stdio by default. To host your own read-only Streamable HTTP server:

peer mcp --transport http --profile read-only --host 0.0.0.0 --port 3000

HTTP rejects cash and full. Those profiles remain local stdio surfaces.

Registration Modes

Profile	Behavior
`read-only`	Generic protocol reads plus Peer Cash reads; never signs or broadcasts
`cash`	Complete `peer_cash_*` surface; prepares unsigned plans and never accepts private keys, signs, or broadcasts
`full`	Every generic CLI-backed tool plus Peer Cash; generic writes preview unless the server process starts with `--yes`

Start with read-only. Never start full with --yes unless every write tool in that process is intentionally allowed to broadcast without a second preview.

Tool Naming

Tool names are deterministic:

peer_<path>

Rules:

path segments are joined with _
dashes are converted to _

Examples:

peer quote → peer_quote
peer deposit ensure-allowance → peer_deposit_ensure_allowance
peer intent-hook pre set → peer_intent_hook_pre_set

Tool Input Shape

Generic tool schemas are derived from CLI command definitions. Peer Cash schemas are owned by the Cash registry because its custody boundary is intentionally separate.

That means:

generic CLI and MCP tools use the same parameter schema
generated tool catalog should match the live MCP surface
command metadata changes should trigger catalog regeneration

Tool Output Shape

MCP returns:

structuredContent: the normalized CLI envelope
content: a JSON text rendering of the same envelope
isError: mapped from CLI success/failure state

Agent Recommendations

Use hosted MCP when read-only tools are enough.
Use CLI subprocesses when you need shell-native orchestration or local file piping.
Keep write tools disabled by default in shared-agent environments.
Use the cash profile when the host wallet must retain all signing authority.
Use the full profile locally when an automation needs preview-first protocol writes, including deposits, intents, staking, guardian, vault, and checkout operations.