Your AI assistant can now ask who's on the other side.

chainward-mcp-server is the read-side intelligence layer for the AI agent economy on Base. Install it once and any MCP-compatible assistant — Claude Desktop, Cursor, Claude Code, Codex — can look up labeled agent wallets, ACP economics, and our Decodes corpus before you sign a single transaction.

$ npx -y chainward-mcp-server

v0.1.0read-onlyno api key requirednpm: chainward-mcp-server

The gap

Base MCP shipped 7 day-one plugins. All of them answer "how do I act?"

Morpho, Bankr, Moonwell, Avantis, Aerodrome, Virtuals, Uniswap. Every one is a write-side tool — swap, lend, launch, send. None of them answer the question that comes a step earlier: who's the deployer of this token, what does their wallet history look like, and is this an agent ChainWard has investigated?

We shipped that one.

The tools

Eight tools. All read-only.

Your assistant picks the right tool from the description. No prompting required.

lookup_agent: Is 0x… a known AI agent? Returns label, framework, ACP profile, related Decodes. Cheap.
get_agent_profile: 24h/7d stats, hourly balance history, daily gas, 20 most recent transactions, matching Decodes.
get_agent_economics: ACP revenue, aGDP, jobs, success rate, gas efficiency, 30-day P&L.
get_observatory_overview: Ecosystem-wide stats: agents tracked, gas burned, portfolio value, recent volume.
get_top_agents: Leaderboard by activity. Who is doing what on Base, ranked.
get_activity_feed: Live feed of labeled-agent transactions across the ecosystem.
list_decodes: Every published ChainWard Decode, newest first. Each with its target addresses.
find_decodes_for_address: Has ChainWard written about 0x…? Returns matching Decode URLs.

Composition

Pair it with Base MCP. Read before you write.

ChainWard reads. Base MCP writes. Different namespaces, different concerns. Your assistant sees both and composes naturally — look up the deployer with ChainWard, then build the unsigned swap with Base MCP. The user signs in their own Base Account. ChainWard never sees the key.

// claude_desktop_config.json or .cursor/mcp.json
{
  "mcpServers": {
    "chainward": {
      "command": "npx",
      "args": ["-y", "chainward-mcp-server"]
    },
    "base": {
      "command": "npx",
      "args": ["-y", "@base/mcp"]
    }
  }
}

Install

Works in every MCP-capable surface today. No partnership required.

SurfaceTransportStatus

Claude Desktopstdiolive

Cursorstdiolive

Claude Codestdiolive

Codexstdiolive

Remote / your own clientstreamable HTTPlive

For HTTP transport: CHAINWARD_MCP_TRANSPORT=http PORT=3300 npx -y chainward-mcp-server. MCP endpoint at /mcp, health at /healthz.

The agent economy needs a read step before every write step.

ChainWard is the read step. Install it next to whatever signs.

npm: chainward-mcp-server →Read the decodes