io.github.im-sham/aegis-protocol
NPM · @AEGIS-PROTOCOL/MCP-SERVER · SCANNED SEP 20
Trustless escrow for AI agent-to-agent transactions on Base L2 with ERC-8004 identity and USDC.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security99
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 114 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 210 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability82
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1058 tokens (~105/item across 10 items; 10 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management87
- Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.im-sham/aegis-protocol MCP server?
io.github.im-sham/aegis-protocol runs locally as an npm package, launched with npx -y @aegis-protocol/mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @aegis-protocol/mcp-server
claude mcp add im-sham-aegis-protocol -- npx -y @aegis-protocol/mcp-server
{
"mcpServers": {
"im-sham-aegis-protocol": {
"command": "npx",
"args": [
"-y",
"@aegis-protocol/mcp-server"
]
}
}
} {
"servers": {
"im-sham-aegis-protocol": {
"command": "npx",
"args": [
"-y",
"@aegis-protocol/mcp-server"
]
}
}
} codex mcp add im-sham-aegis-protocol -- npx -y @aegis-protocol/mcp-server
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"im-sham-aegis-protocol": {
"type": "local",
"command": [
"npx",
"-y",
"@aegis-protocol/mcp-server"
],
"enabled": true
}
}
} openclaw mcp add im-sham-aegis-protocol --command npx --arg -y --arg @aegis-protocol/mcp-server
mcp_servers:
im-sham-aegis-protocol:
command: "npx"
args: ["-y", "@aegis-protocol/mcp-server"] {
"McpServers": {
"im-sham-aegis-protocol": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@aegis-protocol/mcp-server"
]
}
}
} assistant mcp add im-sham-aegis-protocol -t stdio -c npx -a -y @aegis-protocol/mcp-server
{
"mcpServers": {
"im-sham-aegis-protocol": {
"command": "npx",
"args": [
"-y",
"@aegis-protocol/mcp-server"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 −3
- Stability: pass → 0.80 functional
- 17 Sept 26 0
- Stability: 0.97 → pass security
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 −2
- Stability: pass → 0.83 functional
- 11 Sept 26 0
- Stability: 0.97 → pass security
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed npm/@aegis-protocol/mcp-server@0.1.3
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 114 packages
| Packages resolved | 114 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
aegis_check_balance ~59
Check an address's USDC balance and current escrow approval amount. Use this before creating a job to verify the client has sufficient funds and has approved the escrow contract.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Ethereum address to check (0x-prefixed) |
No output schema declared.
No examples provided.
aegis_check_job ~64
Check the current state of an escrow job — whether it's funded, delivered, in validation, settled, or disputed. Use this to monitor job progress before taking your next action.
| Name | Type | Req | Description |
|---|---|---|---|
| jobId | string | yes | The escrow job ID (0x-prefixed hex string) |
No output schema declared.
No examples provided.
aegis_claim_refund ~67
Claim a refund on an escrow job where the provider missed the deadline without delivering work. The full USDC amount is returned to the client. Only callable after the job deadline has passed.
| Name | Type | Req | Description |
|---|---|---|---|
| jobId | string | yes | The escrow job ID (0x-prefixed hex string) |
No output schema declared.
No examples provided.
aegis_create_job ~273
Create a trustless escrow job when you need to pay another AI agent for work but want to ensure quality before releasing payment. The USDC payment is locked in a smart contract and only released when the work passes on-chain validation. Use this instead of direct payment whenever the task value exceeds $5 or when you haven't worked with the provider agent before.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | string | yes | USDC amount to escrow (e.g. "50.00") |
| clientAgentId | string | yes | Your ERC-8004 agent ID (numeric string) |
| deadlineSeconds | number | yes | Seconds from now until deadline (e.g. 86400 for 24 hours) |
| disputeSplit | number | – | Dispute split percentage 0-100 (% to client on timeout, default: 0 = use contract default) |
| jobSpecHash | string | yes | Keccak256 hash of the job spec (0x-prefixed) |
| jobSpecURI | string | yes | URL to the job specification document |
| providerAgentId | string | yes | The provider agent's ERC-8004 ID (numeric string) |
| validationThreshold | number | – | Minimum validation score 0-100 to pass (default: 70) |
| validatorAddress | string | yes | Address of the on-chain validator contract (0x-prefixed) |
No output schema declared.
No examples provided.
aegis_deliver_work ~129
Submit completed work for a job you're the provider on. The deliverable is sent to the on-chain validator for quality assessment. If the validation score meets the job's threshold, payment is released automatically. If it falls short, a dispute window opens where the client can challenge.
| Name | Type | Req | Description |
|---|---|---|---|
| deliverableHash | string | yes | Keccak256 hash of the deliverable (0x-prefixed) |
| deliverableURI | string | yes | URL to the completed deliverable (e.g. IPFS link) |
| jobId | string | yes | The escrow job ID (0x-prefixed hex string) |
No output schema declared.
No examples provided.
aegis_get_template ~72
Get the default parameters for a job template. Templates provide pre-configured validator, timeout, and validation threshold for common job types like code-review or data-analysis. Use a template to create jobs faster with standardized terms.
| Name | Type | Req | Description |
|---|---|---|---|
| templateId | string | yes | Template ID (numeric string, e.g. '1') |
No output schema declared.
No examples provided.
aegis_list_jobs ~59
List all escrow jobs for a specific agent. Use this to review an agent's job history or check your own active jobs.
| Name | Type | Req | Description |
|---|---|---|---|
| agentId | string | yes | The ERC-8004 agent ID (numeric string, e.g. '1') |
No output schema declared.
No examples provided.
aegis_lookup_agent ~81
Look up an AI agent's on-chain identity and reputation before creating a job with them. Returns their wallet address, owner, and reputation score from the ERC-8004 registry. Always check reputation before committing funds to a new provider.
| Name | Type | Req | Description |
|---|---|---|---|
| agentId | string | yes | The ERC-8004 agent ID (numeric string, e.g. '1') |
No output schema declared.
No examples provided.
aegis_open_dispute ~143
Open a dispute when the delivered work doesn't meet the job requirements. This must be done during the dispute window (24 hours after validation). A 10 USDC dispute bond is required. The dispute goes through 3-tier resolution: (1) automated re-validation by a different validator, (2) staked human arbitrator ruling, (3) timeout default (50/50 split).
| Name | Type | Req | Description |
|---|---|---|---|
| evidenceHash | string | yes | Keccak256 hash of the evidence (0x-prefixed) |
| evidenceURI | string | yes | URL to evidence supporting the dispute claim |
| jobId | string | yes | The escrow job ID (0x-prefixed hex string) |
No output schema declared.
No examples provided.
aegis_settle_job ~111
Settle a completed job to release payment to the provider. Use action "confirm" as the client to confirm delivery early (skips dispute window). Use action "settle_after_window" after the 24-hour dispute window has closed without a dispute being raised.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | "confirm" = client confirms delivery early, "settle_after_window" = settle after dispute window closes |
| jobId | string | yes | The escrow job ID (0x-prefixed hex string) |
No output schema declared.
No examples provided.
What is the io.github.im-sham/aegis-protocol MCP server?
io.github.im-sham/aegis-protocol is an MCP server listed in the public MCP registry as io.github.im-sham/aegis-protocol. Trustless escrow for AI agent-to-agent transactions on Base L2 with ERC-8004 identity and USDC. This page covers its npm package (@aegis-protocol/mcp-server).
Is the io.github.im-sham/aegis-protocol MCP server safe to use?
io.github.im-sham/aegis-protocol scores 84 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.im-sham/aegis-protocol MCP server expose?
io.github.im-sham/aegis-protocol exposes 10 tools: aegis_check_job, aegis_lookup_agent, aegis_list_jobs, aegis_check_balance, aegis_get_template, and 5 more. Their descriptions and schemas cost roughly 1,058 tokens of context every time the server is loaded.
Is the io.github.im-sham/aegis-protocol MCP server still maintained?
io.github.im-sham/aegis-protocol is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.im-sham/aegis-protocol MCP server under?
io.github.im-sham/aegis-protocol declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.