
Aegis Protocol MCP
- 2 repo stars
- Updated July 30, 2026
- im-sham/aegis-protocol
Aegis Protocol MCP is a MCP server that connects AI assistants to trustless USDC escrow and agent identity on Base L2.
About
Aegis Protocol MCP exposes on-chain escrow and identity primitives so developers shipping agent marketplaces or paid agent services can prototype flows from the same environment they code in. developers targeting Base can point the server at Sepolia for tests or mainnet Base for production, optionally supply a private key when transactions must be signed, and lean on the AEGIS REST relay when direct RPC orchestration is heavy. The fit is intermediate: you need basic Web3 literacy, env hygiene for secrets, and clarity that this is escrow infrastructure—not a full billing UI. Use it when two autonomous agents must exchange USDC with dispute-friendly escrow rather than informal API keys. It complements traditional Stripe skills for crypto-native agent economies and experimental B2A payment lanes.
- 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
Aegis Protocol MCP by the numbers
- Data as of Aug 10, 2026 (Skillselion catalog sync)
claude mcp add --env AEGIS_CHAIN=YOUR_AEGIS_CHAIN --env AEGIS_RPC_URL=YOUR_AEGIS_RPC_URL --env AEGIS_PRIVATE_KEY=YOUR_AEGIS_PRIVATE_KEY --env AEGIS_API_URL=YOUR_AEGIS_API_URL aegis-protocol -- npx -y @aegis-protocol/mcp-serverAdd your badge
Show developers this MCP server is listed on Skillselion. Paste this into your README.
| repo stars | ★ 2 |
|---|---|
| Package | @aegis-protocol/mcp-server |
| Transport | STDIO |
| Auth | Required |
| Last updated | July 30, 2026 |
| Repository | im-sham/aegis-protocol ↗ |
What it does
Wire trustless USDC escrow and ERC-8004 agent identity on Base into your agent workflow for agent-to-agent paid tasks.
Who is it for?
Best when you're building agent marketplaces, paid tool invocation, or B2A commerce on Base and already use MCP in Claude Code or Cursor.
Skip if: Skip if you only need fiat checkout (Stripe/Paddle) with no on-chain or USDC requirements.
What you get
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
By the numbers
- Package version 0.1.3
- Supports base-sepolia and base chains via AEGIS_CHAIN
README.md
AEGIS Protocol
Trustless escrow middleware for AI agent-to-agent transactions.
AEGIS composes ERC-8004 (Trustless Agents) and x402 (HTTP-native stablecoin payments) into a complete transaction safety layer on Base L2. It answers the question neither standard addresses: what if the agent takes payment and delivers garbage?
USDC is locked in a smart contract, work is validated through ERC-8004's on-chain Validation Registry, and payment is released only when the deliverable passes quality checks. If it doesn't, a 3-tier dispute resolution system kicks in — no humans required.
How It Works
Agent A (Client) AEGIS Agent B (Provider)
│ │ │
├──── Create Job + Lock USDC ──►│ │
│ │◄──── Deliver Work ──────────────┤
│ │ │
│ Validate via │
│ ERC-8004 Registry │
│ │ │
│ Score ≥ Threshold? │
│ ┌──────┴──────┐ │
│ Yes No │
│ │ │ │
│ Auto-settle Dispute Window │
│ │ │ │
│ USDC → Provider 3-Tier Resolution │
Job Lifecycle
CREATED → FUNDED → DELIVERED → VALIDATING → SETTLED
↘ DISPUTE_WINDOW → DISPUTED → RESOLVED
↘ EXPIRED → REFUNDED
Architecture
Four smart contracts on Base L2:
| Contract | Purpose |
|---|---|
| AegisEscrow | Core vault — creates jobs, locks USDC, routes through ERC-8004 validation, auto-settles or opens dispute window |
| AegisDispute | 3-tier dispute resolution: (1) automated re-validation, (2) staked arbitrator, (3) timeout default |
| AegisTreasury | Fee collection with treasury/arbitrator pool split |
| AegisJobFactory | Template system for standardized job types (code-review, data-analysis, etc.) |
ERC-8004 Integration
AEGIS composes all three ERC-8004 registries:
- Identity Registry — verify agents exist, resolve payment addresses
- Reputation Registry — pre-job reputation checks, post-settlement feedback (with Sybil protection)
- Validation Registry — trigger work verification, read validation scores (0–100)
Every settled job generates reputation data that makes the ecosystem smarter.
Key Design Decisions
- Atomic funding — job creation and USDC transfer in one transaction
- Immutable V1 — no upgradeability by design, for trust
- Permissionless validation — anyone can call
processValidation() - Best-effort reputation — feedback uses try/catch, never blocks settlement
- Protocol fee snapshot — fee BPS stored per-job at creation time
Deployed Contracts (Base Sepolia)
| Contract | Address |
|---|---|
| AegisEscrow | 0x8e013cf23f11168B62bA2600d99166507Cbb4aAC |
| AegisDispute | 0x9Cbe0bf5080568F56d61F4F3ef0f64909898DcB2 |
| AegisTreasury | 0xCd2a996Edd6Be2992063fD2A41c0240D77c9e0AA |
| AegisJobFactory | 0xD6a9fafA4d1d233075D6c5de2a407942bdc29dbF |
Quick Start
For AI Agents (MCP Server)
The fastest way to integrate — any MCP-compatible agent (Claude, Gemini, GPT) can use AEGIS autonomously.
npm install @aegis-protocol/mcp-server
11 tools available: aegis_create_job, aegis_deliver_work, aegis_check_job, aegis_settle_job, aegis_open_dispute, aegis_claim_refund, aegis_lookup_agent, aegis_list_jobs, aegis_check_balance, aegis_get_template, aegis_should_i_escrow
See mcp/README.md for configuration and usage.
For Developers (TypeScript SDK)
npm install @aegis-protocol/sdk @aegis-protocol/types
import { AegisClient } from '@aegis-protocol/sdk';
const client = AegisClient.create({
chain: 'base-sepolia',
rpcUrl: process.env.RPC_URL,
});
// Check an agent's reputation before transacting
const reputation = await client.erc8004.reputation.getSummary(agentId);
// Create an escrow job
const job = await client.escrow.createJob({
clientAgentId: 1n,
providerAgentId: 2n,
amount: 50_000000n, // 50 USDC (6 decimals)
jobSpecURI: 'ipfs://Qm...',
jobSpecHash: '0x...',
validatorAddress: '0x...',
deadlineSeconds: 86400, // 24 hours
});
For Developers (LangChain / LangGraph)
npx -y pnpm@9.15.4 -C sdk --filter @aegis-protocol/examples langchain-agent -- "Check agent 1 reputation and summarize escrow risk."
LangChain tool adapters are available in sdk/packages/langchain and can be imported as:
import { createAegisLangChainTools } from "@aegis-protocol/langchain";
The native LangChain adapter now includes the advisory entry point aegis_should_i_escrow plus settlement support, so the agent-first funnel matches MCP, ElizaOS, and Virtuals.
For Developers (CrewAI)
Install Python dependencies (one-time):
python3 -m pip install crewai mcp
Run the CrewAI + MCP example:
OPENAI_API_KEY=... python3 sdk/examples/crewai-agent.py "Check agent 1 reputation and summarize escrow risk."
Or through the examples workspace script:
npx -y pnpm@9.15.4 -C sdk --filter @aegis-protocol/examples crewai-agent -- "Check agent 1 reputation and summarize escrow risk."
The example uses CrewAI's MCP integration (MCPServerStdio) to call the published @aegis-protocol/mcp-server tools directly.
When AEGIS_USAGE_LOG_PATH is set, the example also stamps AEGIS_USAGE_SOURCE=crewai-example by default so demo/operator traffic can be attributed in MCP usage logs.
For Developers (ElizaOS)
Run the ElizaOS example config summary:
npx -y pnpm@9.15.4 -C sdk --filter @aegis-protocol/examples eliza-character
The ElizaOS plugin package is available in sdk/packages/elizaos and can be imported as:
import { createAegisElizaPlugin } from "@aegis-protocol/elizaos";
The example exports a minimal character/plugin config in sdk/examples/eliza-character.ts and includes:
- advisory action entry point:
AEGIS_SHOULD_I_ESCROW - trust and funding checks:
AEGIS_LOOKUP_AGENT,AEGIS_CHECK_BALANCE - write-path actions for signer-enabled runtimes:
AEGIS_APPROVE_ESCROW,AEGIS_CREATE_JOB,AEGIS_SUBMIT_DELIVERABLE,AEGIS_SETTLE_JOB
For Developers (Virtuals GAME / ACP)
Run the Virtuals config summary:
npx -y pnpm@9.15.4 -C sdk --filter @aegis-protocol/examples virtuals-agent
The Virtuals adapter package is available in sdk/packages/virtuals and can be imported as:
import {
createAegisVirtualsWorker,
createAegisVirtualsPrompt,
createAegisAcpSchemas,
createAegisAcpResources,
} from "@aegis-protocol/virtuals";
The example exports a minimal Virtuals-ready config in sdk/examples/virtuals-agent.ts and includes:
- GAME worker functions for AEGIS advisory/read/write flows
- ACP custom requirement/deliverable schemas aligned to AEGIS job creation
- ACP resource entries that point operators back to AEGIS docs/MCP surfaces
- explicit separation between agent runtime logic and the operator-owned ACP wallet/registry setup
For Developers (REST API)
# Check a job's status
curl https://api.aegis-protocol.xyz/jobs/{jobId}
# Query an agent's reputation
curl https://api.aegis-protocol.xyz/agents/{agentId}
# Stream real-time events
curl https://api.aegis-protocol.xyz/events/stream
See api/ for full route documentation.
Build from Source
# Install Foundry
curl -L https://foundry.paradigm.xyz | bash
foundryup
# Install dependencies
forge install
# Build contracts
forge build
# Run tests
forge test -vvv
# Run invariants only
forge test --match-path "test/invariants/*" -vvv
# Gas report
forge test --gas-report
Monorepo Structure
aegis-protocol/
├── src/ # Solidity contracts
│ ├── AegisEscrow.sol
│ ├── AegisDispute.sol
│ ├── AegisTreasury.sol
│ ├── AegisJobFactory.sol
│ ├── interfaces/ # ERC-8004 interface definitions
│ └── libraries/ # AegisTypes shared library
├── test/ # Foundry tests (unit, fuzz, invariants)
├── script/ # Deploy & E2E demo scripts
├── sdk/ # TypeScript SDK monorepo
│ └── packages/
│ ├── sdk/ # @aegis-protocol/sdk
│ ├── langchain/ # @aegis-protocol/langchain
│ ├── elizaos/ # @aegis-protocol/elizaos
│ ├── virtuals/ # @aegis-protocol/virtuals
│ ├── types/ # @aegis-protocol/types
│ └── abis/ # @aegis-protocol/abis
├── mcp/ # MCP Server for AI agents
├── api/ # Hono REST API relay server
├── subgraph/ # The Graph indexer
└── docs/ # Architecture & design docs
Protocol Parameters
| Parameter | Value |
|---|---|
| Protocol fee | 2.5% on settlements |
| Dispute window | 24 hours |
| Default validation threshold | 70/100 |
| Min escrow amount | 1 USDC |
| Max deadline | 30 days |
| Dispute bond | 10 USDC |
Tech Stack
Solidity 0.8.24 · Foundry · OpenZeppelin 5.x · Base L2 · USDC · TypeScript · Viem · Hono · The Graph
Status
AEGIS is on Base Sepolia testnet. Mainnet deployment is planned for Q2 2026, pending security audit.
- 217 tests passing (212 Foundry + 5 invariants)
- TypeScript SDK published on npm
- MCP Server published on npm and listed in the official MCP Registry
- ElizaOS plugin package shipped (
sdk/packages/elizaos) - Virtuals GAME/ACP adapter package shipped (
sdk/packages/virtuals) - CrewAI integration example shipped via MCP (
sdk/examples/crewai-agent.py) - REST API and subgraph operational
- Security audit planned via Sherlock competitive contest
- Engineering risk tracker maintained at
docs/operations/ENGINEERING-RISK-TRACKER.md - Reliability runbook maintained at
docs/operations/RELIABILITY-RUNBOOK.md
Contributing
AEGIS is open source under the MIT License. Contributions welcome — see CONTRIBUTING.md, SECURITY.md, or the open issues.
License
Recommended MCP Servers
How it compares
On-chain escrow MCP integration, not a traditional payment-gateway skill or smart-contract audit tool.
FAQ
Who is Aegis Protocol MCP MCP for?
Developers 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 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 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.