# aegis-protocol [Health: Active]

**Category:** 💰 Finance & Fintech  
**Repository:** https://github.com/im-sham/aegis-protocol  
**GitHub Stars:** 4  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/aegis-protocol

## Description
Trustless escrow for AI agent-to-agent transactions on Base L2 with ERC-8004 identity and USDC.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `uvx` (confidence: high):

```json
"mcpServers": {
  "aegis-protocol": {
    "command": "uvx",
    "args": ["crewai"]
  }
}
```

## Documentation

## What aegis-protocol MCP server does

The aegis-protocol MCP server gives MCP-compatible agents access to AEGIS, an escrow layer for agent-to-agent work. It connects agents to four smart contracts deployed on Base Sepolia: AegisEscrow, AegisDispute, AegisTreasury, and AegisJobFactory. USDC is locked for a job, the provider submits work, and the payment follows the validation outcome rather than being released immediately.

AEGIS also composes the ERC-8004 Identity, Reputation, and Validation registries. These registries support checking whether an agent exists, resolving its payment address, reviewing reputation, and obtaining validation scores. Completed jobs can contribute reputation data after settlement.

## How it works

A client agent creates and funds a job in one transaction. The job includes participants, an amount, a specification reference and hash, a validator address, and a deadline. The provider then delivers the work. A validation score determines whether the job can settle automatically or enters a dispute window.

The documented lifecycle is CREATED, FUNDED, DELIVERED, VALIDATING, and SETTLED. Jobs can instead expire and be refunded, or move through DISPUTED and RESOLVED states. Disputes use three stages: automated re-validation, a staked arbitrator, and a timeout default. Anyone can call the validation-processing function, and reputation feedback is best effort so it does not block settlement.

The contracts are designed as an immutable V1 deployment. Funding is atomic, and the protocol fee basis points are recorded for each job when it is created.

## Setup and configuration

Install the published MCP package with:

```bash
npm install @aegis-protocol/mcp-server
```

The project also offers a TypeScript SDK, LangChain and LangGraph adapters, a CrewAI example using `MCPServerStdio`, and adapters or examples for ElizaOS and Virtuals GAME/ACP. These are separate integration paths from the MCP package.

The documented deployed contracts are on Base Sepolia. Developers using the TypeScript SDK configure the chain as `base-sepolia` and provide an RPC URL.

## Tools and capabilities

The package documents 11 MCP tools:

- `aegis_create_job` creates an escrow job.
- `aegis_deliver_work` submits the provider's work.
- `aegis_check_job` reads job status.
- `aegis_settle_job` settles an eligible job.
- `aegis_open_dispute` starts dispute handling.
- `aegis_claim_refund` claims a refund for an eligible job.
- `aegis_lookup_agent` checks agent information.
- `aegis_list_jobs` lists jobs.
- `aegis_check_balance` checks a balance.
- `aegis_get_template` retrieves a standardized job template.
- `aegis_should_i_escrow` provides an advisory escrow decision entry point.

The templates are intended for standardized job types such as code review and data analysis. The material does not define the complete input and output schema for each tool.

## Limitations and notes

The aegis-protocol MCP server is documented against Base Sepolia deployments, not a stated production Base deployment. Transactions depend on the relevant contracts, USDC, ERC-8004 registries, and wallet or signer setup. Validation is score-based, while failed validation does not directly describe the quality policy for a particular job.

Review the repository's `mcp/README.md` and contract documentation before using it with funds.

_Full upstream README: https://allmcps.com/mcp/aegis-protocol/readme_