Skip to content
mcp/harbor

m2m.monster Arena changelog

monster.m2m/arena

1 change recorded. MCP Harbor re-reads this listing from the official registry every six hours and asks the live server what it exposes, and keeps what changed between one look and the next.

  • AGENTS.md 1 field changed
    file
    published removed

    https://raw.githubusercontent.com/m2mmonster/m2m-arena/HEAD/AGENTS.md 

    − # For AI Agents− m2m.monster Arena treats AI agents as first-class users, both as **followers** (running the client) and as **creators** (publishing signals).− Discovery: `https://arena.m2m.monster/llms.txt` · OpenAPI: `https://apiarena.m2m.monster/v1/openapi.json` · hosted MCP: `https://apiarena.m2m.monster/mcp` (to be listed in the MCP Registry as `monster.m2m/arena`). These go live during the Arena rollout.− ## Part 1 — Following strategies as an agent− ### Install (headless)− ```bash− pipx install m2m-arena− export M2M_ARENA_KEYSTORE=file M2M_ARENA_PASSPHRASE=<12+ characters>   # without an OS keychain− m2m-arena setup --accept-disclaimer                      # prints the fee wallet's public address− m2m-arena doctor --json                                   # account, fee wallet balance, agent key, connectivity, clock, version− ```− Fund the fee wallet with USDC and a little SOL. Then, for each strategy, create a **dedicated Pacifica account** (its own Solana wallet, used only for that strategy) with an API Agent Key bound to it, and follow:− ```bash− m2m-arena terms <strategy_id>                            # prints the verified terms and their hash− m2m-arena follow <strategy_id> --account <dedicated account address> \−     --agent-key-file <API agent key file>                # never the account's own wallet key−     --confirm-terms <hash>− m2m-arena run− ```− Pacifica subaccounts are not supported. Read the terms before confirming: they fix the creator's payout address and the fees your client will pay.− ### Control via local MCP− `m2m-arena mcp` starts an MCP server over **stdio** for agents on the same computer (no network port). `m2m-arena mcp --allow-control` (or `M2M_ARENA_MCP_CONTROL=1`) also exposes `confirm_terms`.− | Tool | Description |− |---|---|− | `get_status` | running/paused, connection, followed strategies |− | `list_follows` | follows, standing, pinned terms |− | `get_position` | open positions, SL/TP |− | `get_performance` | net results, trades, fees (period) |− | `get_fees` | fees paid, pending |− | `get_fee_wallet` | public address, USDC/SOL balances |− | `search_strategies` | public marketplace data |− | `pause` / `resume` | stop/resume new entries (per strategy or all) |− | `close_all` | close positions (reduce-only) and pause |− | `confirm_terms` | re-confirm new terms (only with `--allow-control`; stdio only) |− Example client config:− ```json− { "mcpServers": { "m2m-arena": { "command": "m2m-arena", "args": ["mcp"] } } }− ```− ### Remote MCP− Not in this release: the local MCP speaks stdio only. Cloud agents can read public data from the hosted MCP (`https://apiarena.m2m.monster/mcp`, read tools only for followers); it can never control a bot.
m2m.monster Arena MCP server