One MCP. Separate agent and owner authority.

Start with a connection check

1. Get the Mainnet agent credential privately

Use the credential supplied by the owner or in private judge instructions. Bearer tokens are authentication credentials, not wallet private keys. The spending and owner roles use separate tokens. Keep owner tokens, wallet keys and provider keys out of the agent's environment.

2. Configure your MCP client

Streamable HTTP with bearer authentication. Use your client's supported configuration format; the Codex recipe below was checked against the hosted endpoint. In this completed proof deployment, the agent receives read-only query capabilities.

{ "mcpServers": { "sisih": { "type": "http", "url": "https://sisih-azure.vercel.app/api/mcp",
  "headers": { "Authorization": "Bearer ${SISIH_AGENT_TOKEN}" } } } }

New-Item -ItemType Directory -Force sisih-agent | Out-Null
Set-Location sisih-agent
Remove-Item Env:SISIH_OWNER_TOKEN, Env:SISIH_OWNER_MCP_TOKEN, Env:DEMO_TOKEN, Env:OWNER_PRIVATE_KEY, Env:AGENT_PRIVATE_KEY -ErrorAction SilentlyContinue
# Secure prompt: keeps bearer credential out of PSReadLine console history
$env:SISIH_AGENT_TOKEN = [System.Net.NetworkCredential]::new("", (Read-Host "Enter SISIH_AGENT_TOKEN" -AsSecureString)).Password

3. Read the Mainnet state

Use the sisih MCP server to show the current Mainnet vault balance, protected commitments and permission state. List available services. Do not buy anything or change configuration.

$options = @('exec', '--ignore-user-config', '--ignore-rules', '--skip-git-repo-check', '--ephemeral', '--sandbox', 'read-only', '--disable', 'shell_tool', '--disable', 'unified_exec', '--disable', 'apps', '--disable', 'plugins', '--disable', 'hooks', '--disable', 'browser_use', '--disable', 'computer_use', '--disable', 'view_image', '-c', 'approval_policy=never', '-c', 'web_search=disabled', '-c', 'mcp_servers.sisih.url=https://sisih-azure.vercel.app/api/mcp', '-c', 'mcp_servers.sisih.bearer_token_env_var=SISIH_AGENT_TOKEN', '-c', 'mcp_servers.sisih.default_tools_approval_mode=auto')
codex @options "Use the sisih MCP server to show the current Mainnet vault balance, protected commitments and permission state. List available services. Do not buy anything or change configuration."

Other Streamable HTTP clients can use the connection contract above. Antigravity and a model owner-assistant session have not been verified.

The connected Mainnet vault

Mainnet MCP URL

https://sisih-azure.vercel.app/api/mcp

Vault

Inspect the Mainnet vault

Authentication

Bearer credential. A role never comes from a client name or a tool argument.

Ask your agent to inspect the actual result

This prompt retrieves the completed second purchase and the later refusal. Status reads never create or repeat a payment.

Use Sisih get_request_status for req-7dd90263-75e. Explain the delivered live report, the recalled rule source and both Mainnet transaction receipts. Then inspect req-f37bacb5-c6a and explain the reserve refusal. These are recorded requests: do not create a purchase.

Follow the full Mainnet proof →

Owner authority stays separate

The owner signed approval, session transition and final revocation locally. The original wallet key never reached the server. The published connection exposes evidence and status; configuration changes, new approvals and signed actions are closed.

{ "mcpServers": { "sisih": { "type": "http", "url": "https://sisih-azure.vercel.app/api/mcp",
  "headers": { "Authorization": "Bearer ${SISIH_OWNER_TOKEN}" } } } }