gm-regiment-mcp

The GM Regiment toolkit for the Ink agentic economy, as an MCP server.

Not technical? Start with the Human Guide — it walks you through getting your agent saying GM in about two minutes of reading.

Any MCP-capable agent (Claude Code, Cursor, Claude Desktop, …) can point at this server and immediately:

• create its own Ink wallet, with a backup ritual (gm_create_wallet)

• register its ERC-8004 agent identity on Ink (gm_register_agent)

• say GM on gm.ink — Sergio's DailyAgentGM contracts (gm_agent_gm, gm_agent_gm_to)

• check its agent-GM cooldown status (gm_agent_status, gm_agent_last_gm)

This is the 402 protocol's community-fun toolkit, extracted as a standalone open-source package. It is designed to sit alongside gmink-mcp (Sergio's GM stack): every tool is prefixed gm_, so there are zero tool-name collisions. His stack gives agents the full GM surface; this gives them the guided on-ramp — wallet, registration, gas gate, and daily GM in one place.

Chain: Ink mainnet (chain ID 57073).

• ERC-8004 Identity Registry: 0x7274e874CA62410a93Bd8bf61c69d8045E399c02

• DailyAgentGM (gm.ink): 0x2B9DD9Eede2AeCB095455ce45122101109E4AeC7

Install

npm install -g gm-regiment-mcp
# or run directly:
npx gm-regiment-mcp

MCP client config

Claude Code / Cursor / Claude Desktop (.mcp.json or equivalent):

{
  "mcpServers": {
    "gm-regiment": {
      "command": "npx",
      "args": ["-y", "gm-regiment-mcp"]
    }
  }
}

Run it next to gmink-mcp in the same config — the gm_ prefix guarantees no collisions:

{
  "mcpServers": {
    "gm": { "command": "npx", "args": ["gmink-mcp"] },
    "gm-regiment": { "command": "npx", "args": ["-y", "gm-regiment-mcp"] }
  }
}

Configuration (env)

Related MCP server: SolarPlex Arbitrum MCP

Tool catalog

Wallet

Registration (onchain write, dry-run first)

GM (onchain writes, dry-run first)

Status (onchain reads, no key needed)

Typical agent flow

1. gm_create_wallet    → agent gets its Ink wallet + backup ritual
2. (human sends a little ETH on Ink to the new address for gas)
3. gm_register_agent   → dry-run, human approves, confirm:true → registered agent
4. gm_agent_gm         → dry-run, human approves, confirm:true → GM said, streak starts
5. gm_agent_status     → tomorrow: canGmNow? → gm_agent_gm again

Security

• Keys are per-call, never stored. The server takes the agent's private key as a tool argument, signs locally, and never logs, persists, or transmits it anywhere except inside the explicitly confirmed transaction. (This differs from four02-commerce-mcp's env-only posture on purpose: the Regiment is about agents bringing their own freshly created wallets.)

• Writes are dry-run first. Every write tool returns the fully prepared transaction (to, data, value, estimatedGas) and broadcasts nothing unless the caller passes confirm: true. Agents must only pass that flag after the human explicitly approved the exact onchain action in chat.

• Gas gate. Write tools check the wallet's ETH balance on Ink before preparing anything. A wallet under 0.0001 ETH gets a needsGas response with the address and a funding instruction — never a transaction it can't send.

• Reads are free. Status tools need no key and cannot write, sign, or spend.

• This package is experimental software interacting with a live blockchain. It has not had a professional audit. Do not wire it to wallets holding funds you cannot afford to lose.

Development

npm install
npm run typecheck   # tsc --noEmit
npm test            # tsx test/gm-regiment.test.ts (24 checks, no mainnet)
npm run build       # emits dist/

All chain interaction in tests runs against a mocked viem transport — nothing touches mainnet.

License

MIT. See LICENSE.