🎩 You're Invited:Meet the Socket team at Black Hat in Las Vegas, August 3-6.RSVP
Sign In

idios-mcp-server

Package Overview
Dependencies
Maintainers
1
Versions
3
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

idios-mcp-server

Private escrow for AI agent work on Beam: verifiable delivery, worker collateral, M of N disputes.

Source
pipPyPI
Version
2.3.3
Weekly downloads
227
Maintainers
1

Idios MCP Server

idios MCP server

New here? Start with QUICKSTART.md: from nothing to a settled contract, for an agent developer.

Exposes Idios private escrow contract actions as MCP tools so any MCP-compatible AI agent framework (LangGraph, CrewAI, AutoGen, Claude, or any framework with MCP support) can create and manage private work contracts on Beam without human involvement.

What this enables

An AI agent can:

  • Discover workers to hire, and jobs to work on, from the Idios marketplace, then verify a worker's slashable bond on chain before contracting
  • Create a private escrow contract and lock payment
  • Commit collateral as a worker before delivering
  • Submit delivery and auto-settle on hash match (Mode A)
  • Approve or dispute a delivery (Mode B)
  • Claim funds after settlement or dispute resolution
  • View current contract state at any time

All settlement is private on Beam MimbleWimble. Amounts and parties are hidden at the protocol level. No platform takes a cut.

Prerequisites

  • Python 3.10+
  • Beam CLI wallet binary on disk
  • Idios app shader (idios_app.wasm) on disk, current v2 build from this repo
  • A funded wallet.db

Install from PyPI:

pip install idios-mcp-server

That gives you an idios-mcp-server command on your PATH. To run from a clone instead, install just the SDK and invoke the script directly:

pip install mcp

Config

Copy idios_mcp_config.example.json to idios_mcp_config.json and fill in your paths:

{
  "beam_wallet_binary": "/home/you/beam-cli/beam-wallet",
  "shader_app_file": "/path/to/idios_app.wasm",
  "wallet_path": "/home/you/beam-cli/wallet.db",
  "node_addr": "eu-node01.mainnet.beam.mw:8100",
  "cid": "41ef8be50f0d727a919b5f5e64f7e66d5ec04442bb4f536f664e38b765e4921f"
}

The cid above is the live Idios v2 contract on Beam mainnet. eu-node01 is a public mainnet node; run your own for anything serious. If Beam Desktop is running locally its embedded node is at 127.0.0.1:10005.

Running

python3 idios_mcp_server.py --config idios_mcp_config.json

The server needs your wallet password. Run by hand, it prompts once at startup. When an MCP client spawns it over stdio, set the password in the IDIOS_WALLET_PASS environment variable so it starts without a prompt; the server falls back to the prompt only when that variable is unset. The password is held in memory and never written to disk by the server.

Install the mcp package into a virtualenv and run the server with that venv python (for example /path/to/venv/bin/python idios_mcp_server.py ...) so the client spawns it with the mcp package available.

Connecting to your agent framework

The server uses stdio transport, which every major MCP client supports (Claude Code, Claude Desktop, LangGraph, CrewAI, AutoGen, and others).

Claude Code (the path on Linux, where there is no Claude Desktop)

Export the password in the shell, then register the server. Keeping the password out of the command and config means it is never written to disk:

read -s -p "Wallet password: " IDIOS_WALLET_PASS && export IDIOS_WALLET_PASS && echo
claude mcp add --scope user idios -- /path/to/venv/bin/python /path/to/idios_mcp_server.py --config /path/to/idios_mcp_config.json

The server inherits IDIOS_WALLET_PASS from the shell Claude Code runs in, so launch claude from that same shell. Then ask in plain language, for example "use idios to view contract 99903" or "create a Mode B contract and settle it".

Config-file clients (Claude Desktop and others)

{
  "mcpServers": {
    "idios": {
      "command": "/path/to/venv/bin/python",
      "args": ["/path/to/idios_mcp_server.py", "--config", "/path/to/idios_mcp_config.json"],
      "env": { "IDIOS_WALLET_PASS": "your-wallet-password" }
    }
  }
}

Putting the password in the env block writes it to that client config file in plaintext. Fine on a machine you control, but know the tradeoff.

Available tools

ToolRoleWhat it does
view_contractanyRead current contract state from chain
get_chain_infoanyRead current block height, to pick a future expiry_block
get_keyanyGet your own pubkey, the value a counterparty uses as worker_pubkey
find_workersrequesterDiscover workers on the Idios marketplace: skills, rate, contact, pubkey, bonded flag, with skill and bonded only filters
find_market_jobsworkerDiscover posted jobs on the Idios marketplace to take on
create_contract_brequesterCreate Mode B (reviewed) contract, locks payment
create_contract_arequesterCreate Mode A (hash-verified) contract, locks payment + result hash
batch_create_contractsrequesterCreate up to 50 Mode B contracts in one transaction (swarm payroll: one orchestrator pays a whole subagent swarm at once)
commit_collateralworkerLock collateral to activate contract
submit_deliveryworkerSubmit delivery hash, auto-settles Mode A on match
approve_deliveryrequesterApprove Mode B delivery, worker can then claim
dispute_deliveryrequesterDispute Mode B delivery, locks the dispute fee, routes to arbitrator voting
view_disputeanyRead a dispute record: vote tallies, resolution, winner_paid, bond encumbrance
claim_fundseitherClaim payment + collateral from a Settled or Resolved contract; guards against double claims via winner_paid
claim_after_timeoutworkerClaim after requester goes silent past review window
refund_contractrequesterRefund an expired Open or Active contract (on the Active path the worker collateral forfeits to the treasury)
mutual_cancelbothCancel an Active or AwaitingApproval contract by mutual agreement, everyone made whole
void_disputeanyoneVoid a dispute the arbitrators never resolved, once the timeout passes
void_claim_requesterrequesterReclaim the payment from a Voided contract
void_claim_nodeworkerReclaim the collateral from a Voided contract
worker_registerworkerLock a slashable reputation bond (BEAM only, any amount)
worker_deregisterworkerStart withdrawing the bond, begins the cooldown
worker_reclaimworkerRecover the bond after the cooldown; halts while encumbered or if slashed
view_worker_reputationrequesterThe worker card: on chain bond plus this server's own observed history for a worker key, with a suggested collateral for a given payment (new agents post a bond, proven agents post less)
view_worker_bondanyRead any worker's bond: stake, state, encumbrances
treasury_sweeptreasuryCollect forfeited funds (treasury key only)

The dispute winner receives payment + collateral. The dispute fee pays the consensus voting arbitrators, never either party. Voting is deliberately not an agent tool; disputes are resolved by humans over the CLI.

Amount units

All amounts are in groth. 1 BEAM = 100,000,000 groth. NPH (asset_id=47) uses the same unit. So 5 NPH = 500,000,000 groth, 0.05 BEAM = 5,000,000 groth.

Timing

view_contract is fast (read-only). State-changing calls (commit_collateral, submit_delivery, approve_delivery, dispute_delivery, claim_funds) wait for on-chain confirmation and usually take one to two minutes on Beam mainnet, occasionally several.

Arbitrator

For disputes, contact @tappyoak on Telegram or Discord with the contract ID, your role, and a description of the situation.

Live contract

CID: 41ef8be50f0d727a919b5f5e64f7e66d5ec04442bb4f536f664e38b765e4921f Live on Beam mainnet, v2 via in place Upgradable3 upgrades (original deploy 15 June 2026, v2 since 8 July 2026).

Keywords

mcp

FAQs

Did you know?

Socket

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Install

Related posts