imd-mcp

Experimental, commissioned as a test of the IMD swarm. It may not work as described. Read the code, start with small amounts, no warranty.

A real paid job.open was opened through imd_pay on Ethereum mainnet on 2026-10-03 (order 03fab9a5-30a2-49e4-9f70-455211d87d8f, submit 202, admitted) at commit 865972d.

An MCP (Model Context Protocol) server over stdio that lets any MCP client — Claude Code, Claude Desktop, Cursor — hire the IMD swarm at https://api.imd.fun. Paid actions are settled with the x402 / Permit2 flow: the server quotes, you sign a Permit2 PermitWitnessTransferFrom plus a QuoteApproval EIP-712 payload, the IMD server pays the gas.

Payment is 0.5 IMD (0xd34a99bc0f67ae1bbd63c660e6d0b0dd03e263b7 on Ethereum mainnet) per action — per run for schedules. Your wallet needs a one-time approve of IMD to Permit2 (0x000000000022D473030F116dDEE9F6B43aC78BA3); the API server submits and pays gas for the onchain settlement.

Tools

Paid actions are read at runtime from GET /openapi.json x-imd-actions (an array keyed by .action: job.open, job.continue, launch.open, oracle.request, workflow.open, schedule.create, schedule.topup), so new actions appear without a release. The live API advertises no per-action input schema, so imd_quote passes input through: use imd_check (free) first, and the server's 422 invalid_input problems are returned as-is. Input shapes are documented at https://imd.fun/docs#paid.

Related MCP server: Agent Payment Node

Run it

Requires Node 20+.

Straight from GitHub:

npx -y github:identity-md-launches/launch-600-build-imd-mcp-model-context

The prepare script compiles the TypeScript on install and the imd-mcp bin starts the stdio server.

Or from a clone:

git clone https://github.com/identity-md-launches/launch-600-build-imd-mcp-model-context.git && cd launch-600-build-imd-mcp-model-context
npm ci            # prepare runs `npm run build` automatically
node dist/src/index.js        # or: npm start

imd-mcp --help prints the experimental notice and the env vars.

Client configuration

Read-only (no key — imd_pay will refuse):

{
  "mcpServers": {
    "imd": {
      "command": "npx",
      "args": ["-y", "github:identity-md-launches/launch-600-build-imd-mcp-model-context"]
    }
  }
}

With a wallet:

{
  "mcpServers": {
    "imd": {
      "command": "npx",
      "args": ["-y", "github:identity-md-launches/launch-600-build-imd-mcp-model-context"],
      "env": {
        "IMD_PRIVATE_KEY": "0x…",
        "IMD_MAX_PER_REQUEST": "1",
        "IMD_MAX_PER_DAY": "5",
        "IMD_DRY_RUN": "false"
      }
    }
  }
}

Claude Code

claude mcp add imd -- npx -y github:identity-md-launches/launch-600-build-imd-mcp-model-context
# or with env vars:
claude mcp add imd \
  -e IMD_PRIVATE_KEY=0x… -e IMD_DRY_RUN=false \
  -- npx -y github:identity-md-launches/launch-600-build-imd-mcp-model-context

Claude Desktop

Edit claude_desktop_config.json (macOS ~/Library/Application Support/Claude/, Windows %APPDATA%\Claude\):

{
  "mcpServers": {
    "imd": {
      "command": "npx",
      "args": ["-y", "github:identity-md-launches/launch-600-build-imd-mcp-model-context"],
      "env": { "IMD_DRY_RUN": "true" }
    }
  }
}

Cursor

Settings → MCP → "New MCP server" writes ~/.cursor/mcp.json:

{
  "mcpServers": {
    "imd": {
      "command": "npx",
      "args": ["-y", "github:identity-md-launches/launch-600-build-imd-mcp-model-context"],
      "env": { "IMD_DRY_RUN": "true" }
    }
  }
}

Any of these can also point at a local checkout with "command": "node", "args": ["/path/to/launch-600-build-imd-mcp-model-context/dist/src/index.js"].

Environment

Safety model

• The key is read only from IMD_PRIVATE_KEY. It is never logged, printed, written to disk, or sent anywhere except inside signatures.

• Dry run is the default. Real payment needs IMD_DRY_RUN=false and confirm: true on the imd_pay call.

• Per-request and per-day caps are enforced before any signature is made.

• Before signing, an amount is atomically reserved in a per-wallet local daily ledger. The reservation is retained if submit or polling loses a response: after a signature exists, the client conservatively assumes it may settle. This ledger is keyed by the public address and contains no private key.

• The 402 challenge is refused if accepts[0] or the quote disagree with the GET /requests/capabilities actions[] entry for the quoted action on asset, payTo or amount — this blocks look-alike address poisoning. The expected amount is that entry's payment.amount, or payment.amount × runs (runs from the quoted input) for actions pricedPer "run" (schedule.create, schedule.topup). We never pay more than the quoted amount, and the caps apply to that total: with the default IMD_MAX_PER_REQUEST=1, a schedule of more than 2 runs is refused.

Paid-request flow (what imd_pay does)

1. POST /requests/{id}/submit → 402 challenge (accepts[], quote, resource, resourceUrl, requesterScopeHash).

2. Verify accepts[0] and quote.payment against capabilities; check caps.

3. Sign EIP-712 PermitWitnessTransferFrom (Permit2 domain, spender 0x402085c248EeA27D92E8b30b2C58ed07f9E20001, deadline = expiresAt − 5 s, witness {to: payTo, validAfter: 0}).

4. Sign EIP-712 QuoteApproval (IdentityMD Paid Action v1) whose paymentHash is the sha256 of the key-sorted JSON payment object.

5. POST /requests/{id}/submit with PAYMENT-SIGNATURE: base64(payment) and body {quoteSignature} → 202 pending / 200 outcome.

6. Poll GET /requests/{id} until it leaves quoted/payment_pending/admission_pending.

Development

See Publishing for the repository owner’s npm and MCP directory publishing steps.

npm test   # builds, then runs the full quote → 402 → sign → submit → poll
           # path against a local mock server with throwaway keys

Tests never spend real IMD and never touch mainnet — they run against tests/mock-server.ts, which serves the bodies of GET /requests/capabilities, GET /openapi.json and two free POST /requests/check calls saved from the live API under fixtures/live/. tests/live.test.ts checks the client against those saved bodies.

Commissioned through paid IMD swarm requests.