Aegis Protocol
Wire trustless USDC escrow and ERC-8004 agent identity on Base into your agent workflow for agent-to-agent paid tasks.
Overview
Aegis Protocol MCP is a MCP server for the Build phase that connects AI assistants to trustless USDC escrow and agent identity on Base L2.
What is this MCP server?
- Trustless escrow for AI agent-to-agent transactions on Base L2 with USDC settlement
- ERC-8004 identity support for attributable agent parties
- Configurable chain (base-sepolia or base), RPC, REST relay via AEGIS_API_URL
- Optional AEGIS_PRIVATE_KEY for signing; read-only mode when key omitted
- npm @aegis-protocol/mcp-server v0.1.3 with Node runtime hint
- Package version 0.1.3
- Supports base-sepolia and base chains via AEGIS_CHAIN
Community signal: 2 GitHub stars.
What problem does it solve?
Agent builders lack a standard way to escrow USDC between agents without bespoke smart-contract scripts in every repo.
Who is it for?
Developers building agent marketplaces, paid tool invocation, or B2A commerce on Base who already use MCP in Claude Code or Cursor.
Skip if: Founders who only need fiat checkout (Stripe/Paddle) with no on-chain or USDC requirements.
What do I get? / Deliverables
After registration, your agent can drive Aegis escrow and chain configuration through MCP tools instead of one-off wallet scripts.
- MCP-accessible Aegis escrow and chain configuration on Base
- Repeatable agent-to-agent payment integration path without custom CLI each time
Recommended MCP Servers
Journey fit
How it compares
On-chain escrow MCP integration, not a traditional payment-gateway skill or smart-contract audit tool.
Common Questions / FAQ
Who is Aegis Protocol MCP for?
Solo builders and small teams shipping AI agents that pay or get paid in USDC on Base and want MCP-driven escrow setup.
When should I use Aegis Protocol MCP?
Use it during build when integrating agent-to-agent paid workflows, testing on base-sepolia, or wiring production Base escrow.
How do I add Aegis Protocol MCP to my agent?
Install @aegis-protocol/mcp-server via npm, set AEGIS_CHAIN, AEGIS_RPC_URL, and AEGIS_API_URL, optionally AEGIS_PRIVATE_KEY for signing, then add the stdio server to your MCP client config.