MCP server

vordium-mcp connects any AI that speaks the Model Context Protocol to Vordium. It runs on your machine and talks to your MCP client over stdio; no account and no API key.

• Testnet first. It reads the testnet unless you name the main network.
• Your keys stay with you. No tool takes a private key; to trade you point the server at a file holding an agent key, and it signs on your machine.
• The chain enforces the limits. The agent trades under the policy its account set on the chain (Agents).
• Nothing is remembered. Every value is read from the network when a tool is called.

Release on PyPI: 0.3.0 · Python >=3.9.

Install and connect

uvx vordium-mcp --version

Claude Desktop — add to claude_desktop_config.json, then restart:

{ "mcpServers": { "vordium": { "command": "uvx", "args": ["vordium-mcp"] } } }

Claude Code

claude mcp add vordium -- uvx vordium-mcp

Cursor — add the same mcpServers entry to ~/.cursor/mcp.json.

Then ask, for example, "What does the ETH order book on Vordium look like?"

Tools

Trading as an agent

1. Register the agent and open its session from the account's own wallet (your first agent).
2. Save the agent's private key in a file only you can read.
3. Start the server with trading allowed:

{
  "mcpServers": {
    "vordium": {
      "command": "uvx",
      "args": ["--from", "vordium-mcp[trade]", "vordium-mcp", "--allow-trading",
               "--owner", "0xYOUR_ACCOUNT", "--agent-key-file", "~/.vordium/agent.key"]
    }
  }
}

Before signing, the server checks that the network reports agent trading on, that the key is a live agent of that account with a confirmed session, and that the market is trading. The chain then applies the agent's policy on every validator, and the server returns the chain's answer as it is.

The main network is used only when you name it: "args": ["vordium-mcp", "--network", "mainnet"].