Agentiam Mcp
Wire Claude Code or Cursor to AgentIAM on Base so agents can call 18 x402-paid safety and intelligence endpoints over stdio MCP.
Overview
AgentIAM MCP is a MCP server for the Build phase that exposes AgentIAM’s 18 Base x402 agent-safety and intelligence endpoints to coding agents over stdio.
What is this MCP server?
- Stdio MCP transport—no separate HTTP bridge in the agent config
- Wraps 18 x402 micropayment endpoints on Base for AgentIAM
- Agent safety and intelligence checks callable as MCP tools
- Published as io.github.achilliesbot/agentiam-mcp v0.1.0
- GitHub source: achilliesbot/agentiam-mcp
- 18 x402 endpoints documented in the server description
- Server version 0.1.0 per server.schema.json
- Transport: stdio MCP wrapper
What problem does it solve?
You want agent safety and intelligence on Base without writing and maintaining eighteen separate x402 HTTP integrations inside every agent project.
Who is it for?
Indie builders running Claude Code or Cursor with on-chain or x402-based agent services on Base who already understand micropayment flows.
Skip if: Teams that only need browser automation, generic LLM chat, or agents with no Base/x402 budget and no desire to operate paid external APIs.
What do I get? / Deliverables
After registering the stdio server, your agent can invoke AgentIAM capabilities as native MCP tools with x402 billing on the documented endpoints.
- MCP tool surface mapping to AgentIAM x402 APIs
- Stdio-connected agent runtime without custom HTTP glue for those endpoints
Recommended MCP Servers
Journey fit
Canonical shelf is Build because you register the MCP server while assembling agent runtime integrations, not during ideation or launch SEO. agent-tooling is the right subphase: stdio MCP exposes external agent safety APIs directly inside the coding agent’s tool surface.
How it compares
Paid on-chain agent-safety API via MCP, not a local browser automation or general web-scraping skill.
Common Questions / FAQ
Who is AgentIAM MCP for?
Solo and small-team builders shipping AI agents who want AgentIAM safety and intelligence on Base exposed as MCP tools instead of custom HTTP clients.
When should I use AgentIAM MCP?
Use it during Build while wiring agent-tooling when your stack already uses Base x402 and you need the documented 18 endpoints inside Claude Code, Cursor, or similar.
How do I add AgentIAM MCP to my agent?
Add the io.github.achilliesbot/agentiam-mcp stdio server entry from the GitHub repo to your agent’s MCP configuration, then fund or configure x402 access for AgentIAM on Base as their API requires.