# Iris Code (npm · @iris-code/mcp)

Local code-quality rules, findings, preview-first safe fixes and gate results for coding agents.

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

## Components

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

## Channel facts

- Registry: `npm`
- Package: `@iris-code/mcp`
- Version: `0.2.2`
- 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-11-05.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 0 of 1 dependencies flagged as unhealthy.
- **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 7 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 59/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1623 tokens (~162/item across 10 items; 10 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 91/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 74% 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 10 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the Iris Code MCP server?

Iris Code runs locally as an npm package, launched with npx -y @iris-code/mcp. 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 daiveedjay-iris-code -- npx -y @iris-code/mcp
```

### Cursor

```json
{
  "mcpServers": {
    "daiveedjay-iris-code": {
      "command": "npx",
      "args": [
        "-y",
        "@iris-code/mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "daiveedjay-iris-code": {
      "command": "npx",
      "args": [
        "-y",
        "@iris-code/mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add daiveedjay-iris-code -- npx -y @iris-code/mcp
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add daiveedjay-iris-code --command npx --arg -y --arg @iris-code/mcp
```

### Hermes

```yaml
mcp_servers:
  daiveedjay-iris-code:
    command: "npx"
    args: ["-y", "@iris-code/mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "daiveedjay-iris-code": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@iris-code/mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add daiveedjay-iris-code -t stdio -c npx -a -y @iris-code/mcp
```

### Other

```json
{
  "mcpServers": {
    "daiveedjay-iris-code": {
      "command": "npx",
      "args": [
        "-y",
        "@iris-code/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-11-04 (score 69, +1)

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

### 2026-11-02 (score 68, +1)

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

### 2026-10-31 (score 67, +1)

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

### 2026-10-29 (score 66, +1)

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

### 2026-10-28 (score 65)

First indexed and scored.

## MCP tools (10)

### `iris_schema` (~156 tokens)

Report database tables, columns and relations read from repository schema code, with unresolved references and conflicts disclosed. Before writing a query, migration or model change, call this to get the real table and column names instead of guessing. Schema structure and usage for one named table are Free. Pass a saved project evidence_id for aggregate usage without rescanning. (Free)

Input parameters:

- `evidence_id` (string): Saved project review returned by iris_check. Uses captured schema and usage without scanning.
- `format` (string)
- `include_usage` (boolean): Usage and warnings. One named table is Free. Use evidence_id from a project review for all tables.
- `table` (string): Optional physical table name, model identifier or schema-qualified table id

### `iris_check` (~187 tokens)

Report code-health findings for a file, folder, or workspace: every rule that fired, each with its line, severity, and a stable id you can pass to iris_fix_safe. Also reports which files import each checked file, the project health score, and the gate threshold. Use this before editing a file to see what else to re-check, or to answer whether code is ready to commit or push. One file and its direct importers are Free. A directory captures a project review using the current local allowance. Pass its inspection.evidence_id to reopen captured findings without rescanning. (Free file checks; signed-in project reviews use the current workspace allowance)

Input parameters:

- `evidence_id` (string): Saved project review. Omit path to read its captured scope without a new scan or action.
- `path` (string): Path relative to the MCP root
- `scope` (string)

### `iris_explain` (~110 tokens)

Explain a finding: the rule behind it, why it fired here, and what would satisfy it. Use this when you need the cause rather than the label, so a fix addresses the rule instead of silencing it. (Saved explanations included; fresh file explanations require Pro)

Input parameters:

- `evidence_id` (string): Saved project review. Omit path to read its captured scope without a new scan or action.
- `path` (string): Path relative to the MCP root
- `scope` (string)

### `iris_gate` (~114 tokens)

Report whether this project's configured quality gate would pass, and which files fail which rule. This is the same decision the pre-push hook and CI make, so use it to answer whether a push or build would be blocked. (Saved gate previews included; fresh enforcement requires paid access to this workspace)

Input parameters:

- `evidence_id` (string): Saved project review. Omit path to read its captured scope without a new scan or action.
- `path` (string): Path relative to the MCP root
- `scope` (string)

### `iris_config` (~93 tokens)

Report the rules this project actually enforces, as Iris Code resolves them: thresholds, scoring weights, gate limits, naming policy, and which folder is being analysed and why. Use this before suggesting a change, so your advice matches what the pre-push hook and CI block on rather than a general convention. (Free)

Input parameters:

- `path` (string, required): Path relative to the MCP root
- `scope` (string)

### `iris_fix_safe` (~215 tokens)

Preview, then apply, only the changes Iris Code can prove safe: merge compatible imports, remove unused import bindings or statements, remove isolated debug statements, or remove literal-only unused variables, including proved multiline ranges. console.error and unused functions are never auto-fixed. Previews by default and returns a preview_token that a later apply must echo back; changed source requires a fresh preview. Refuses per finding with a reason: anything needing a name or a judgement stays your work, and a secret is never auto-fixed. One file is Free; folder and workspace scope need Pro. (Free)

Input parameters:

- `apply` (boolean): Apply validated edits; false previews only
- `finding_ids` (array): Finding IDs returned by iris_check
- `path` (string, required): Path relative to the MCP root
- `preview_token` (string): Required with apply: true. Returned by a previous preview call, single-use, valid 10 minutes. Iris only applies an edit set it has already shown you.
- `scope` (string)

### `iris_refactor_plan` (~123 tokens)

Report a refactor plan for a source file: proved mechanical fixes first, then located suggestions ordered by risk, with destinations from project conventions. Returns a baseline_id held in this session. Apply fixes, preserve behavior and exports, and verify after each move. One planned file remains Free. Fresh folder/workspace plans require sign-in and use one local project action on Free; paid local access is unmetered. The earned project baseline is saved locally. (Free)

Input parameters:

- `path` (string, required): Path relative to the MCP root
- `scope` (string)

### `iris_verify_refactor` (~175 tokens)

Report verification of a refactor against the session baseline_id or git HEAD. Discovers changed and new workspace files even if omitted from files. Rejects packing, broken imports, new cycles, removed imported exports and new findings, and reports code-line movement, health scores, disabled checks and a correction instruction. Never supply before content. One-file verification remains Free. Verification of an earned multi-file baseline uses no additional action, including after allowance exhaustion; never supply a before-source snapshot. (Free)

Input parameters:

- `baseline_id` (string): Session baseline returned by iris_refactor_plan or a failing iris_check; omit for disclosed git HEAD fallback
- `files` (array): Additional affected source paths. Changed/new files are discovered independently.
- `path` (string): Path relative to the MCP root
- `scope` (string)

### `iris_check_dependency` (~140 tokens)

Report known vulnerabilities for this project's dependencies from OSV: severity, confidence, and the nearest fixed version, per package. Saved reports stay readable without refreshing. A fresh audit needs sign-in and network consent, and uses one local project action on Free. no_cache explicitly refreshes provider data. (Saved reports are Free; fresh audits use the current workspace allowance)

Input parameters:

- `allow_network` (boolean): Allow fresh registry and OSV lookups when no usable cache exists
- `no_cache` (boolean): Ignore the local dependency cache and require a fresh scan
- `path` (string, required): Path relative to the MCP root
- `scope` (string)

### `iris_check_package` (~310 tokens)

Report whether one package is safe to add, BEFORE you add or upgrade it as a dependency: whether the version that would install has a known vulnerability, is reported malicious, is yanked, deprecated or a prerelease, or was published so recently it breaks this project's policy - and which version to install instead. Call this before every install command you run and before editing a manifest to add or bump a package. Pass ecosystem (npm, python, cargo, go, rubygems, nuget, maven), name, and optionally version (exact, a range, or a tag). If blocks is true, do not install that version; use suggestedCommand. Needs allow_network: true the first time on a machine. (Free)

Input parameters:

- `allow_network` (boolean): Allow fresh registry and OSV lookups when no usable cache exists
- `ecosystem` (string, required): The registry: npm, python (PyPI), cargo (crates.io), go, rubygems, nuget or maven
- `name` (string, required): Package name, e.g. "lodash", "@scope/pkg", "requests", "github.com/gin-gonic/gin", "org.apache.commons:commons-lang3"
- `no_cache` (boolean): Ignore the local package cache
- `version` (string): Optional. An exact version, a range such as ^1.2.0 or >=2,<3, or a tag such as latest. Omit to check what a bare install would pick.

## Diagnostics

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

## Score history

- 2026-11-05: 69
- 2026-11-04: 69
- 2026-11-03: 68
- 2026-11-02: 68
- 2026-11-01: 67
- 2026-10-31: 67
- 2026-10-30: 66
- 2026-10-29: 66
- 2026-10-28: 65

## Common questions

### What is the Iris Code MCP server?

Iris Code is an MCP server listed in the public MCP registry as io.github.Daiveedjay/iris-code. Local code-quality rules, findings, preview-first safe fixes and gate results for coding agents. This page covers its npm package (@iris-code/mcp).

### Is the Iris Code MCP server safe to use?

Iris Code scores 69 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 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 Iris Code MCP server expose?

Iris Code exposes 10 tools: iris_schema, iris_check, iris_explain, iris_gate, iris_config, and 5 more. Their descriptions and schemas cost roughly 1,623 tokens of context every time the server is loaded.

### Is the Iris Code MCP server still maintained?

Iris Code is still listed as active in the MCP registry. We last reached this channel on 5 November 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 Iris Code MCP server under?

Iris Code declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/@iris-code/mcp
- Socket report: https://socket.dev/npm/package/@iris-code/mcp
- Repository: https://github.com/Daiveedjay/iris-code-mcp
- Website: https://www.iriscode.co/mcp
- Changelog RSS feed: https://verifymcp.io/servers/daiveedjay-iris-code/iris-code-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/daiveedjay-iris-code/iris-code-mcp.json
- HTML version of this page: https://verifymcp.io/servers/daiveedjay-iris-code/iris-code-mcp