AegisAI
REMOTE · AEGIS-API.KADOPI.WORKERS.DEV · SCANNED SEP 20
Paid pre-execution risk verification for AI agents over MCP and x402.
Available components
Recent critical change
Authorization (30 Aug 2026). See the changelog before you install this server.
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. How we score → Why this is hard to score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (stop_monitor_subscription). See how to fix → View diagnostics → Fail
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability66
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 855 tokens (~50/item across 17 items; 17 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
- Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage69
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 6% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 17 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 17 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
remote · aegis-api.kadopi.workers.dev
claude mcp add --transport http kadopi-aegis-ai 'https://aegis-api.kadopi.workers.dev/mcp'
{
"mcpServers": {
"kadopi-aegis-ai": {
"url": "https://aegis-api.kadopi.workers.dev/mcp"
}
}
} {
"servers": {
"kadopi-aegis-ai": {
"type": "http",
"url": "https://aegis-api.kadopi.workers.dev/mcp"
}
}
} [mcp_servers.kadopi-aegis-ai] url = "https://aegis-api.kadopi.workers.dev/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"kadopi-aegis-ai": {
"type": "remote",
"url": "https://aegis-api.kadopi.workers.dev/mcp",
"enabled": true
}
}
} openclaw mcp add kadopi-aegis-ai --url 'https://aegis-api.kadopi.workers.dev/mcp' --transport streamable-http
mcp_servers:
kadopi-aegis-ai:
url: "https://aegis-api.kadopi.workers.dev/mcp" {
"McpServers": {
"kadopi-aegis-ai": {
"Transport": "http",
"Url": "https://aegis-api.kadopi.workers.dev/mcp"
}
}
} assistant mcp add kadopi-aegis-ai -t streamable-http -u 'https://aegis-api.kadopi.workers.dev/mcp'
{
"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.
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 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.
- 17 Sept 26 +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.
- 14 Sept 26 +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.
- 12 Sept 26 +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.
- 10 Sept 26 +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.
- 8 Sept 26 +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.
- 6 Sept 26 +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.
- 4 Sept 26 +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.
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 · Probed https://aegis-api.kadopi.workers.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=kadopi.workers.dev | CN=WE1,O=Google Trust Services,C=US | 13 Aug 2026 | 11 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 7378f7e851e7d509138dab0d6217f927 |
| SANs: kadopi.workers.dev, *.kadopi.workers.dev | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of aegis-api.kadopi.workers.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| workers.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://aegis-api.kadopi.workers.dev/mcp | Verified | 200 | |
| http (plaintext) | http://aegis-api.kadopi.workers.dev/mcp | Inconclusive | 405 |
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 →
create_monitor_a2a_dns_txt_challenge Create an A2A endpoint DNS TXT challenge ~43
Creates a one-time DNS TXT ownership challenge without contacting the customer endpoint. Verification and delivery remain disabled.
| Name | Type | Req | Description |
|---|---|---|---|
| endpointId | string | yes | – |
No output schema declared.
No examples provided.
create_monitor_a2a_endpoint_challenge Create an A2A endpoint ownership challenge ~48
Creates a one-time 15-minute challenge for a pending endpoint. It does not contact or verify the endpoint and never enables delivery.
| Name | Type | Req | Description |
|---|---|---|---|
| endpointId | string | yes | – |
No output schema declared.
No examples provided.
evaluate_agent_commerce_policy Evaluate Agent Commerce policy ~80
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.
| Name | Type | Req | Description |
|---|---|---|---|
| offer | object | yes | – |
| purchase | object | yes | – |
| seller | object | yes | – |
No output schema declared.
No examples provided.
get_aegis_capabilities Get AegisAI capabilities ~36
Returns machine-readable discovery links and x402 testnet payment information. This tool is free and does not perform risk verification.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_monitor_alert Get an on-chain monitor alert ~31
Returns one structured alert and its bounded evidence for the authenticated monitor account.
| Name | Type | Req | Description |
|---|---|---|---|
| alertId | string | yes | – |
No output schema declared.
No examples provided.
get_monitor_subscription Get a monitor subscription ~30
Returns one account-owned subscription and its current policy and scan state.
| Name | Type | Req | Description |
|---|---|---|---|
| subscriptionId | string | yes | – |
No output schema declared.
No examples provided.
list_monitor_a2a_endpoints List A2A alert endpoints ~28
Lists the authenticated account's A2A notification endpoints and delivery-disabled state.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_monitor_alerts List on-chain monitor alerts ~61
Lists structured alerts belonging only to the authenticated monitor account. This tool never sends notifications or performs wallet actions.
| Name | Type | Req | Description |
|---|---|---|---|
| caseStatus | string | – | – |
| limit | integer | – | – |
| severity | string | – | – |
| walletAddress | string | – | – |
No output schema declared.
No examples provided.
list_monitor_subscriptions List monitor subscriptions ~26
Lists account-scoped Base Sepolia monitor subscriptions without changing monitoring or payment state.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
register_monitor_a2a_endpoint Register an A2A alert endpoint ~74
Registers an account-scoped endpoint in pending-verification state. Registration never contacts the endpoint and delivery remains disabled.
| Name | Type | Req | Description |
|---|---|---|---|
| endpointUrl | string | yes | – |
| maxPerHour | integer | – | – |
| minSeverity | string | – | – |
| protocolVersion | string | yes | – |
| transport | string | yes | – |
No output schema declared.
No examples provided.
register_monitor_subscription Register a stopped monitor subscription ~62
Registers a Base Sepolia wallet and validated policy in stopped state. Payment and operator approval are still required before activation.
| Name | Type | Req | Description |
|---|---|---|---|
| chainId | string | yes | – |
| label | string | – | – |
| policy | object | yes | – |
| walletAddress | string | yes | – |
No output schema declared.
No examples provided.
stop_monitor_a2a_endpoint Stop an A2A alert endpoint ~37
Idempotently stops an account-owned endpoint and cancels only its unsent deliveries.
| Name | Type | Req | Description |
|---|---|---|---|
| endpointId | string | yes | – |
No output schema declared.
No examples provided.
stop_monitor_subscription Stop a monitor subscription ~33
Idempotently disables monitoring for one account-owned subscription without deleting its audit history.
| Name | Type | Req | Description |
|---|---|---|---|
| subscriptionId | string | yes | – |
No output schema declared.
No examples provided.
update_monitor_alert_status Update on-chain monitor alert status ~63
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.
| Name | Type | Req | Description |
|---|---|---|---|
| alertId | string | yes | – |
| caseStatus | string | yes | – |
| note | string | – | – |
No output schema declared.
No examples provided.
update_monitor_subscription Update monitor subscription policy ~48
Idempotently updates label or policy. It never activates monitoring, pays, or changes networks.
| Name | Type | Req | Description |
|---|---|---|---|
| label | – | – | – |
| policy | object | – | – |
| subscriptionId | string | yes | – |
No output schema declared.
No examples provided.
verify_monitor_a2a_dns_txt_challenge Verify an A2A endpoint DNS TXT challenge ~56
Checks only Cloudflare's fixed DNS resolver when DNS verification is enabled. It never contacts the customer endpoint and never enables delivery.
| Name | Type | Req | Description |
|---|---|---|---|
| challengeId | string | yes | – |
| endpointId | string | yes | – |
No output schema declared.
No examples provided.
verify_risk Verify risk with AegisAI ~99
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.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | Text to assess before an external action. |
| context | object | – | – |
| plan | string | – | Product plan. Evidence is advertised but not yet available. |
| requestedChecks | array | – | – |
| sources | array | – | – |
No output schema declared.
No examples provided.
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.