# io.github.Bajuzjefe/aikido-mcp (npm · aikido-mcp)

Security analysis for Aiken smart contracts on Cardano. 75 vulnerability detectors.

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

## Components

- npm · `aikido-mcp`: 69/100 (this document), [markdown](https://verifymcp.io/servers/bajuzjefe-aikido-mcp/aikido-mcp.md), [page](https://verifymcp.io/servers/bajuzjefe-aikido-mcp/aikido-mcp)

## Channel facts

- Registry: `npm`
- Package: `aikido-mcp`
- Version: `0.1.1`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-04.

- **Supply Chain Security**: 83/100
  - No malware found by supply-chain analysis.
  - CVE check failed: a known medium-severity CVE affects hono 4.12.33, reached via @modelcontextprotocol/sdk > hono. A fixed version is available.
  - No install/post-install scripts declared.
  - Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 158 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 77/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 355 tokens (~88/item across 4 items; 4 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 30/100
  - Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add bajuzjefe-aikido-mcp -- npx -y aikido-mcp
```

### Codex

```bash
codex mcp add bajuzjefe-aikido-mcp -- npx -y aikido-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "bajuzjefe-aikido-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "aikido-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add bajuzjefe-aikido-mcp --command npx --arg -y --arg aikido-mcp
```

### Hermes

```yaml
mcp_servers:
  bajuzjefe-aikido-mcp:
    command: "npx"
    args: ["-y", "aikido-mcp"]
```

### Other

```json
{
  "mcpServers": {
    "bajuzjefe-aikido-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "aikido-mcp"
      ]
    }
  }
}
```

## 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-08-04 (score 69, −1)

- [security regression] CVE-2026-69207 affects this package: medium
- [security regression] Known CVEs: partial → fail

### 2026-08-03 (score 70, +1)

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

### 2026-08-02 (score 69, +48)

- [security regression] Provenance: unverified → fail
- [security improvement] Known CVEs: unverified → partial
- [security improvement] Install scripts: unverified → pass
- [security improvement] Malware scan: unverified → pass
- [functional regression] Tool coverage: 100 → unverified
- [functional improvement] Schema quality: unverified → excellent
- [functional improvement] License: unverified → pass
- [functional improvement] Dependency health: unverified → partial
- [functional improvement] Maintenance: unverified → pass
- [functional improvement] MCP protocol: unverified → pass
- [functional improvement] Stability: unverified → 0.23
- [functional] First check of Schema quality: unverified
- [functional] Licence: MIT

### 2026-08-01 (score 21, −7)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-31 (score 28, −18)

- [security regression] Malware scan: pass → unverified

### 2026-07-27 (score 46)

First indexed and scored.

## MCP tools (4)

### `aikido_analyze` (~145 tokens)

Scan an Aiken smart contract project for security vulnerabilities. Returns findings with severity, location, CWC classification, and evidence. Exit code 2 (findings above threshold) is normal, not an error.

Input parameters:

- `config` (string): Path to custom .aikido.toml config file
- `diff` (string): Git ref for incremental analysis — only report findings in changed files
- `min_severity` (string): Minimum severity threshold to report
- `project_path` (string, required): Path to the Aiken project directory (must contain aiken.toml)
- `static_only` (boolean): Skip multi-lane orchestration (faster but less thorough)

### `aikido_list_rules` (~67 tokens)

List all 75 Aikido security detectors with severity, category, CWE mapping, and reliability tier.

Input parameters:

- `category` (string): Filter by category (e.g., 'authorization', 'arithmetic', 'minting')
- `severity` (string): Filter by minimum severity level

### `aikido_explain` (~60 tokens)

Get a detailed explanation of a specific Aikido security detector, including what it checks, why it matters, and remediation guidance.

Input parameters:

- `detector` (string, required): Detector name (e.g., 'missing-signature-check', 'value-not-preserved')

### `aikido_cwc_lookup` (~83 tokens)

Search the Cardano Weakness Classification (CWC) registry. Look up by CWC ID, severity, detector name, or keyword. Returns vulnerability descriptions, affected detectors, and remediation guidance.

Input parameters:

- `query` (string, required): CWC ID (e.g., 'CWC-001'), severity (e.g., 'critical'), detector name, or keyword

## Diagnostics

Captured diagnostic sections: Provenance, Vulnerabilities, Dependencies. The full working is on the page: https://verifymcp.io/servers/bajuzjefe-aikido-mcp/aikido-mcp#diagnostics

## Score history

- 2026-08-04: 69
- 2026-08-03: 70
- 2026-08-02: 69
- 2026-08-01: 21
- 2026-07-31: 28
- 2026-07-30: 46
- 2026-07-28: 46
- 2026-07-27: 46

## Links

- npm package: https://www.npmjs.com/package/aikido-mcp
- Socket report: https://socket.dev/npm/package/aikido-mcp
- Repository: https://github.com/Bajuzjefe/Aikido-Security-Analysis-Platform
- Changelog RSS feed: https://verifymcp.io/servers/bajuzjefe-aikido-mcp/aikido-mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/bajuzjefe-aikido-mcp/aikido-mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/bajuzjefe-aikido-mcp/aikido-mcp