Is io.github.im-sham/aegis-protocol safe to use?

io.github.im-sham/aegis-protocol has no known CVEs as of the latest MCPpedia security scan. It does not require authentication, so any local process can connect — keep this in mind in shared environments.

How do I install io.github.im-sham/aegis-protocol?

io.github.im-sham/aegis-protocol supports copy-paste install configs on its MCPpedia page for Claude Desktop, Cursor, and Claude Code. Scroll to the Quick Install section and select your client.

What can io.github.im-sham/aegis-protocol do?

io.github.im-sham/aegis-protocol provides 11 tools: aegis_create_job, aegis_deliver_work, aegis_check_job, aegis_settle_job, aegis_open_dispute and 6 more. See the full tools list on the server page for descriptions and parameters.

What AI clients work with io.github.im-sham/aegis-protocol?

io.github.im-sham/aegis-protocol is compatible with claude-desktop, cursor, claude-code. It uses stdio and sse and http transport.

Is io.github.im-sham/aegis-protocol actively maintained?

io.github.im-sham/aegis-protocol is actively maintained — last commit was 6 days ago. It has 2 GitHub stars.

io.github.im-sham/aegis-protocol

pnpm

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

2 114.0M/wk 11 tools GitHub npm PyPI

No known CVEs

No license

Actively maintained

Last commit 6d ago

Works with most clients

Transport: stdio, sse, http

11 tools · ~591 tok

Grade B · 0.3% of 200K ctx

Edit this pageView history

AI / ML Finance

Step 1

Install in your client

Config is the same across clients — only the file and path differ.

Supported in Claude Desktopstdio, sse, http · Node 18+

Paste into ~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "io-github-im-sham-aegis-protocol": {
      "args": [
        "-y",
        "pnpm"
      ],
      "command": "npx"
    }
  }
}

Are you the author?

Add this badge to your README to show your security score and help users find safe servers.

Embed in your READMEAbout badges →

[![MCPpedia Score](https://mcppedia.org/api/badge/io-github-im-sham-aegis-protocol)](https://mcppedia.org/s/io-github-im-sham-aegis-protocol)

Read me

What io.github.im-sham/aegis-protocol does

Trustless escrow middleware for AI agent-to-agent transactions.

Test This Server

Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.

npx -y 'pnpm' 2>&1 | head -1 && echo "✓ Server started successfully"

After testing, let us know if it worked:

Loading README…

Scored, not listed

Why this score

Five weighted categories — click any category to see the underlying evidence.

Score breakdown

88/100across 5 weighted dimensions

How we score →

0255075100

−12

Security

Maintenance

Efficiency

Documentation

Compatibility

Categoriesclick a row to see evidence

Security

OSV.dev

28 fixed

GHSA-qrv3-253h-g69chigh · fixedCVSS 8.2

pnpm: Path traversal in configDependencies env lockfile allows symlink creation outside node_modules/.pnpm-config

## Summary `pnpm` accepts package names from the env lockfile `configDependencies` section and uses those names directly when creating config dependency symlinks under `node_modules/.pnpm-config`. A malicious repository can commit a crafted `pnpm-lock.yaml` whose env-lockfile document contains a traversal-shaped config dependency name such as `../../PWNED_CFGDEP`. During `pnpm install`, pnpm installs the config dependency and creates a symlink at a path derived from that name. In local testin

Affected: >= 0Fixed in 10.34.4source →

GHSA-72r4-9c5j-mj57high · fixedCVSS 7.1

pnpm: `patch-remove` could delete project-selected files outside the patches directory

## Summary The `patch-remove` deletion-scope issue tracked as GHSA-72r4-9c5j-mj57 / CAND-PNPM-030 has been addressed in pnpm. A crafted patch entry could resolve outside the configured patches directory and cause `pnpm patch-remove` to delete an arbitrary reachable file. This patch validates the configured directory and every resolved target before unlinking anything, then deletes the final directory entry without following it. ## Security boundary - Traversal and absolute paths that resolve

Affected: >= 0Fixed in 10.34.4source →

GHSA-fr4h-3cph-29xvhigh · fixedCVSS 7.1

pnpm: Hoisted install imports lockfile alias outside node_modules

## Summary The hoisted dependency alias issue tracked as GHSA-fr4h-3cph-29xv / CAND-PNPM-059 has been addressed in both pnpm and pacquet. A crafted lockfile alias could be joined directly under a hoisted `node_modules` directory. Traversal aliases could escape that directory, while reserved aliases such as `.bin` or `.pnpm` could overwrite pnpm-owned layout. This patch validates package-name semantics and path containment before graph insertion or filesystem work. ## Security boundary - The

Affected: >= 0Fixed in 10.34.4source →

CVE-2026-55700high · fixedCVSS 7.1

pnpm: `stage download` writes outside its destination directory via manifest name/version traversal

## Summary The staged-tarball filename traversal reported as GHSA-v23m-ccfg-pq9h / CAND-PNPM-038 is fixed on `main` by [pnpm/pnpm#12303](https://github.com/pnpm/pnpm/pull/12303), merged as `65443f4bdf1f0db9c8c7dc58fee25252607e9234`. Before the fix, `pnpm stage download` derived a local filename from registry-controlled package name and version fields. A crafted manifest could escape the selected download directory and overwrite another reachable file. The merged fix validates both fields, deri

Affected: >= 11.3.0Fixed in 11.5.3source →

CVE-2026-55699medium · fixedCVSS 6.5

pnpm: Reserved bin name deletes PNPM_HOME during global remove

<details> <summary>Maintainer Action Plan</summary> ## Maintainer Action Plan This report is ready to review with the shared patch branch. Start with the PR and the expected fixed behavior, then use the detailed exploit narrative below only if you want to replay the original path. - Advisory: `CAND-PNPM-085` / `GHSA-4gxm-v5v7-fqc4` - Advisory URL: https://github.com/pnpm/pnpm/security/advisories/GHSA-4gxm-v5v7-fqc4 - Shared patch PR: https://github.com/pnpm/pnpm-ghsa-j2hc-m6cf-6jm8/pull/1 - S

Affected: >= 0Fixed in 10.34.2source →

Inventory

Tools (11)

Click any tool to inspect its schema.

~591 tokens total

Community

Reviews

Be the first to review

Have you used this server?

Share your experience — it helps other developers decide.

How easy was setup?Did it work reliably?How was the documentation?

Frequently Asked Questions

Is io.github.im-sham/aegis-protocol safe to use?: io.github.im-sham/aegis-protocol has no known CVEs as of the latest MCPpedia security scan. It does not require authentication, so any local process can connect — keep this in mind in shared environments.
How do I install io.github.im-sham/aegis-protocol?: io.github.im-sham/aegis-protocol supports copy-paste install configs on its MCPpedia page for Claude Desktop, Cursor, and Claude Code. Scroll to the Quick Install section and select your client.
What can io.github.im-sham/aegis-protocol do?: io.github.im-sham/aegis-protocol provides 11 tools: aegis_create_job, aegis_deliver_work, aegis_check_job, aegis_settle_job, aegis_open_dispute and 6 more. See the full tools list on the server page for descriptions and parameters.
What AI clients work with io.github.im-sham/aegis-protocol?: io.github.im-sham/aegis-protocol is compatible with claude-desktop, cursor, claude-code. It uses stdio and sse and http transport.
Is io.github.im-sham/aegis-protocol actively maintained?: io.github.im-sham/aegis-protocol is actively maintained — last commit was 6 days ago. It has 2 GitHub stars.

Similar servers

Others in ai-ml / finance

View all →

Sequential Thinking MCP Server98

Dynamic problem-solving through sequential thought chains

87.9k 1

Memory MCP Server98

Persistent memory using a knowledge graph

87.9k 5

Gpt Researcher95

An autonomous agent that conducts deep research on any data using any LLM providers

28.0k 5

Ruflo95

🌊 The leading agent orchestration platform for Claude. Deploy intelligent multi-agent swarms, coordinate autonomous workflows, and build conversational AI systems. Features enterprise-grade architecture, distributed swarm intelligence, RAG integration, and native Claude Code / Codex Integration

62.3k 4

MCP Security Weekly

Get CVE alerts and security updates for io.github.im-sham/aegis-protocol and similar servers.

Community

Discussion

Start a conversation

Ask a question, share a tip, or report an issue.

Has anyone used this with Cursor?How do you handle auth?Any alternatives?

Edit this pageView history

AI / ML Finance

Step 1

Install in your client

Config is the same across clients — only the file and path differ.

Supported in Claude Desktopstdio, sse, http · Node 18+

Paste into ~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "io-github-im-sham-aegis-protocol": {
      "args": [
        "-y",
        "pnpm"
      ],
      "command": "npx"
    }
  }
}

Are you the author?

Add this badge to your README to show your security score and help users find safe servers.

Embed in your READMEAbout badges →

[![MCPpedia Score](https://mcppedia.org/api/badge/io-github-im-sham-aegis-protocol)](https://mcppedia.org/s/io-github-im-sham-aegis-protocol)

Read me

What io.github.im-sham/aegis-protocol does

Trustless escrow middleware for AI agent-to-agent transactions.

Test This Server

Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.

npx -y 'pnpm' 2>&1 | head -1 && echo "✓ Server started successfully"

After testing, let us know if it worked:

README

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`

... View full README on GitHub

Loading README…

Scored, not listed

Why this score

Five weighted categories — click any category to see the underlying evidence.

Score breakdown

88/100across 5 weighted dimensions

How we score →

0255075100

−12

Security

Maintenance

Efficiency

Documentation

Compatibility

Categoriesclick a row to see evidence

Security

OSV.dev

28 fixed

GHSA-qrv3-253h-g69chigh · fixedCVSS 8.2

pnpm: Path traversal in configDependencies env lockfile allows symlink creation outside node_modules/.pnpm-config

Affected: >= 0Fixed in 10.34.4source →

GHSA-72r4-9c5j-mj57high · fixedCVSS 7.1

pnpm: `patch-remove` could delete project-selected files outside the patches directory

Affected: >= 0Fixed in 10.34.4source →

GHSA-fr4h-3cph-29xvhigh · fixedCVSS 7.1

pnpm: Hoisted install imports lockfile alias outside node_modules

Affected: >= 0Fixed in 10.34.4source →

CVE-2026-55700high · fixedCVSS 7.1

pnpm: `stage download` writes outside its destination directory via manifest name/version traversal

Affected: >= 11.3.0Fixed in 11.5.3source →

CVE-2026-55699medium · fixedCVSS 6.5

pnpm: Reserved bin name deletes PNPM_HOME during global remove

Affected: >= 0Fixed in 10.34.2source →

Inventory

Tools (11)

Click any tool to inspect its schema.

~591 tokens total

Community

Reviews

Be the first to review

Have you used this server?

Share your experience — it helps other developers decide.

How easy was setup?Did it work reliably?How was the documentation?

Frequently Asked Questions

Is io.github.im-sham/aegis-protocol safe to use?: io.github.im-sham/aegis-protocol has no known CVEs as of the latest MCPpedia security scan. It does not require authentication, so any local process can connect — keep this in mind in shared environments.
How do I install io.github.im-sham/aegis-protocol?: io.github.im-sham/aegis-protocol supports copy-paste install configs on its MCPpedia page for Claude Desktop, Cursor, and Claude Code. Scroll to the Quick Install section and select your client.
What can io.github.im-sham/aegis-protocol do?: io.github.im-sham/aegis-protocol provides 11 tools: aegis_create_job, aegis_deliver_work, aegis_check_job, aegis_settle_job, aegis_open_dispute and 6 more. See the full tools list on the server page for descriptions and parameters.
What AI clients work with io.github.im-sham/aegis-protocol?: io.github.im-sham/aegis-protocol is compatible with claude-desktop, cursor, claude-code. It uses stdio and sse and http transport.
Is io.github.im-sham/aegis-protocol actively maintained?: io.github.im-sham/aegis-protocol is actively maintained — last commit was 6 days ago. It has 2 GitHub stars.