# AegisAI (remote · aegis-api.kadopi.workers.dev)

Paid pre-execution risk verification for AI agents over MCP and x402.

- Trust score: 69/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

> **Recent critical change**: Authorization (2026-08-30). See the changelog below before you install this server.

## Components

- remote · `aegis-api.kadopi.workers.dev`: 69/100 (this document), [markdown](https://verifymcp.io/servers/kadopi-aegis-ai/aegis-api.md), [page](https://verifymcp.io/servers/kadopi-aegis-ai/aegis-api)

## Channel facts

- Endpoint: `https://aegis-api.kadopi.workers.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.6.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (stop_monitor_subscription).
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 66/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 855 tokens (~50/item across 17 items; 17 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 97/100
  - Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 69/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 6% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 17 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 17 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the AegisAI MCP server?

AegisAI is a hosted endpoint at https://aegis-api.kadopi.workers.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http kadopi-aegis-ai 'https://aegis-api.kadopi.workers.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "kadopi-aegis-ai": {
      "url": "https://aegis-api.kadopi.workers.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "kadopi-aegis-ai": {
      "type": "http",
      "url": "https://aegis-api.kadopi.workers.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.kadopi-aegis-ai]
url = "https://aegis-api.kadopi.workers.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "kadopi-aegis-ai": {
      "type": "remote",
      "url": "https://aegis-api.kadopi.workers.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add kadopi-aegis-ai --url 'https://aegis-api.kadopi.workers.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  kadopi-aegis-ai:
    url: "https://aegis-api.kadopi.workers.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "kadopi-aegis-ai": {
      "Transport": "http",
      "Url": "https://aegis-api.kadopi.workers.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add kadopi-aegis-ai -t streamable-http -u 'https://aegis-api.kadopi.workers.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "kadopi-aegis-ai": {
      "type": "http",
      "url": "https://aegis-api.kadopi.workers.dev/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-19 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-17 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-14 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-12 (score 66, +1)

No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-10 (score 65, +1)

No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-08 (score 64, +1)

No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-06 (score 63, +1)

No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-04 (score 62, +1)

No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (17)

### `get_aegis_capabilities` (~36 tokens)

Get AegisAI capabilities

Returns machine-readable discovery links and x402 testnet payment information. This tool is free and does not perform risk verification.

### `evaluate_agent_commerce_policy` (~80 tokens)

Evaluate Agent Commerce policy

Deterministically pre-evaluates a public-price sale without sending, paying, settling, or changing stored state. Signed Basic and Pro public terms may be allowed; verified-payer velocity is reserved atomically after facilitator verification and before settlement.

Input parameters:

- `offer` (object, required)
- `purchase` (object, required)
- `seller` (object, required)

### `list_monitor_alerts` (~61 tokens)

List on-chain monitor alerts

Lists structured alerts belonging only to the authenticated monitor account. This tool never sends notifications or performs wallet actions.

Input parameters:

- `caseStatus` (string)
- `limit` (integer)
- `severity` (string)
- `walletAddress` (string)

### `get_monitor_alert` (~31 tokens)

Get an on-chain monitor alert

Returns one structured alert and its bounded evidence for the authenticated monitor account.

Input parameters:

- `alertId` (string, required)

### `update_monitor_alert_status` (~63 tokens)

Update on-chain monitor alert status

Idempotently updates only the case status and note for an alert owned by the authenticated monitor account. It never changes notification state or performs wallet actions.

Input parameters:

- `alertId` (string, required)
- `caseStatus` (string, required)
- `note` (string)

### `list_monitor_subscriptions` (~26 tokens)

List monitor subscriptions

Lists account-scoped Base Sepolia monitor subscriptions without changing monitoring or payment state.

### `get_monitor_subscription` (~30 tokens)

Get a monitor subscription

Returns one account-owned subscription and its current policy and scan state.

Input parameters:

- `subscriptionId` (string, required)

### `register_monitor_subscription` (~62 tokens)

Register a stopped monitor subscription

Registers a Base Sepolia wallet and validated policy in stopped state. Payment and operator approval are still required before activation.

Input parameters:

- `chainId` (string, required)
- `label` (string)
- `policy` (object, required)
- `walletAddress` (string, required)

### `update_monitor_subscription` (~48 tokens)

Update monitor subscription policy

Idempotently updates label or policy. It never activates monitoring, pays, or changes networks.

Input parameters:

- `label`
- `policy` (object)
- `subscriptionId` (string, required)

### `stop_monitor_subscription` (~33 tokens)

Stop a monitor subscription

Idempotently disables monitoring for one account-owned subscription without deleting its audit history.

Input parameters:

- `subscriptionId` (string, required)

### `register_monitor_a2a_endpoint` (~74 tokens)

Register an A2A alert endpoint

Registers an account-scoped endpoint in pending-verification state. Registration never contacts the endpoint and delivery remains disabled.

Input parameters:

- `endpointUrl` (string, required)
- `maxPerHour` (integer)
- `minSeverity` (string)
- `protocolVersion` (string, required)
- `transport` (string, required)

### `list_monitor_a2a_endpoints` (~28 tokens)

List A2A alert endpoints

Lists the authenticated account's A2A notification endpoints and delivery-disabled state.

### `create_monitor_a2a_endpoint_challenge` (~48 tokens)

Create an A2A endpoint ownership challenge

Creates a one-time 15-minute challenge for a pending endpoint. It does not contact or verify the endpoint and never enables delivery.

Input parameters:

- `endpointId` (string, required)

### `create_monitor_a2a_dns_txt_challenge` (~43 tokens)

Create an A2A endpoint DNS TXT challenge

Creates a one-time DNS TXT ownership challenge without contacting the customer endpoint. Verification and delivery remain disabled.

Input parameters:

- `endpointId` (string, required)

### `verify_monitor_a2a_dns_txt_challenge` (~56 tokens)

Verify an A2A endpoint DNS TXT challenge

Checks only Cloudflare's fixed DNS resolver when DNS verification is enabled. It never contacts the customer endpoint and never enables delivery.

Input parameters:

- `challengeId` (string, required)
- `endpointId` (string, required)

### `stop_monitor_a2a_endpoint` (~37 tokens)

Stop an A2A alert endpoint

Idempotently stops an account-owned endpoint and cancels only its unsent deliveries.

Input parameters:

- `endpointId` (string, required)

### `verify_risk` (~99 tokens)

Verify risk with AegisAI

Runs paid AegisAI risk verification and never runs verification for free. An x402-aware MCP client can pay and retry this tool automatically; unpaid calls return the canonical payment challenge.

Input parameters:

- `content` (string, required): Text to assess before an external action.
- `context` (object)
- `plan` (string): Product plan. Evidence is advertised but not yet available.
- `requestedChecks` (array)
- `sources` (array)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/kadopi-aegis-ai/aegis-api#diagnostics

## Score history

- 2026-09-20: 69
- 2026-09-19: 69
- 2026-09-18: 68
- 2026-09-17: 68
- 2026-09-16: 67
- 2026-09-15: 67
- 2026-09-14: 67
- 2026-09-13: 66
- 2026-09-12: 66
- 2026-09-11: 65
- 2026-09-10: 65
- 2026-09-09: 64
- 2026-09-08: 64
- 2026-09-07: 63
- 2026-09-06: 63
- 2026-09-05: 62
- 2026-09-04: 62
- 2026-09-03: 61
- 2026-09-02: 61
- 2026-09-01: 61
- 2026-08-31: 60
- 2026-08-30: 60
- 2026-08-29: 66
- 2026-08-28: 66
- 2026-08-27: 66
- 2026-08-26: 65
- 2026-08-25: 63
- 2026-08-24: 63
- 2026-08-23: 62
- 2026-08-22: 62

## Common questions

### What is the AegisAI MCP server?

AegisAI is an MCP server listed in the public MCP registry as io.github.kadopi/aegis-ai. Paid pre-execution risk verification for AI agents over MCP and x402. This page covers its hosted endpoint (https://aegis-api.kadopi.workers.dev/mcp).

### Is the AegisAI MCP server safe to use?

AegisAI scores 69 out of 100 on VerifyMCP. 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 AegisAI MCP server expose?

AegisAI exposes 17 tools: get_aegis_capabilities, evaluate_agent_commerce_policy, list_monitor_alerts, get_monitor_alert, update_monitor_alert_status, and 12 more. Their descriptions and schemas cost roughly 855 tokens of context every time the server is loaded.

### Does the AegisAI MCP server require authentication?

No. We connected to AegisAI without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the AegisAI MCP server still maintained?

AegisAI 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.

## Links

- Remote endpoint: https://aegis-api.kadopi.workers.dev/mcp
- Changelog RSS feed: https://verifymcp.io/servers/kadopi-aegis-ai/aegis-api.xml
- Changelog JSON feed: https://verifymcp.io/servers/kadopi-aegis-ai/aegis-api.json
- HTML version of this page: https://verifymcp.io/servers/kadopi-aegis-ai/aegis-api