# Ironscales (oci · ghcr.io/wyre-technology/ironscales-mcp:v1.2.1)

MCP server for Ironscales phishing incident management — incidents, mailboxes, and reporting.

- Trust score: 48/100 (low)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-22

## Components

- oci · `ghcr.io/wyre-technology/ironscales-mcp:v1.2.1`: 48/100 (this document), [markdown](https://verifymcp.io/servers/wyre-technology-ironscales-mcp/ghcr-io-wyre-technology-ironscales-mcp-v1-2-1.md), [page](https://verifymcp.io/servers/wyre-technology-ironscales-mcp/ghcr-io-wyre-technology-ironscales-mcp-v1-2-1)

## Channel facts

- Registry: `oci`
- Package: `ghcr.io/wyre-technology/ironscales-mcp:v1.2.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-22.

- **Supply Chain Security**: 0/100
  - Malware scan not yet available for this package.
  - Known CVEs could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.
  - Install-script risk not yet assessed.
  - Dependency health could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.
- **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 (Apache-2.0).
  - Actively maintained (last published 15 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 80/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 108 tokens (~36/item across 3 items; 2 tools + 1 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 50/100
  - Stability observed for 15 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.

**Unverified: 1 category.** A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

## Install

### Claude

```bash
claude mcp add wyre-technology-ironscales-mcp -- docker run --rm -i ghcr.io/wyre-technology/ironscales-mcp:v1.2.1
```

### Codex

```bash
codex mcp add wyre-technology-ironscales-mcp -- docker run --rm -i ghcr.io/wyre-technology/ironscales-mcp:v1.2.1
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "wyre-technology-ironscales-mcp": {
      "type": "local",
      "command": [
        "docker",
        "run",
        "--rm",
        "-i",
        "ghcr.io/wyre-technology/ironscales-mcp:v1.2.1"
      ],
      "enabled": true
    }
  }
}
```

### Hermes

```yaml
mcp_servers:
  wyre-technology-ironscales-mcp:
    command: "docker"
    args: ["run", "--rm", "-i", "ghcr.io/wyre-technology/ironscales-mcp:v1.2.1"]
```

### Other

```json
{
  "mcpServers": {
    "wyre-technology-ironscales-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/wyre-technology/ironscales-mcp:v1.2.1"
      ]
    }
  }
}
```

## 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-22 (score 48, +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-08-21 (score 47, +1)

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

### 2026-08-18 (score 46, +1)

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

### 2026-08-16 (score 45, +1)

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

### 2026-08-15 (score 44, +4)

- [functional improvement] Stability: unverified → 0.27

### 2026-08-12 (score 40, 0)

- [functional regression] Security disclosure: unverified → fail

### 2026-08-11 (score 40, 0)

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

### 2026-08-10 (score 40, 0)

- [functional regression] Security disclosure: unverified → fail

## MCP tools (2)

### `ironscales_navigate` (~64 tokens)

Navigate to a domain to see its available tools. Domains: incidents (phishing incidents), email (email classification), remediation (incident remediation), stats (company statistics), allowlist (sender allowlist management).

Input parameters:

- `domain` (string, required): The domain to navigate to

### `ironscales_status` (~22 tokens)

Check Ironscales API connection status and available domains.

## Diagnostics

Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/wyre-technology-ironscales-mcp/ghcr-io-wyre-technology-ironscales-mcp-v1-2-1#diagnostics

## Score history

- 2026-08-22: 48
- 2026-08-21: 47
- 2026-08-20: 46
- 2026-08-19: 46
- 2026-08-18: 46
- 2026-08-17: 45
- 2026-08-16: 45
- 2026-08-15: 44
- 2026-08-14: 40
- 2026-08-13: 40
- 2026-08-12: 40
- 2026-08-11: 40
- 2026-08-10: 40
- 2026-08-09: 40
- 2026-08-08: 40
- 2026-08-07: 40

## Links

- Repository: https://github.com/wyre-technology/ironscales-mcp
- Changelog RSS feed: https://verifymcp.io/servers/wyre-technology-ironscales-mcp/ghcr-io-wyre-technology-ironscales-mcp-v1-2-1.xml
- Changelog JSON feed: https://verifymcp.io/servers/wyre-technology-ironscales-mcp/ghcr-io-wyre-technology-ironscales-mcp-v1-2-1.json
- HTML version of this page: https://verifymcp.io/servers/wyre-technology-ironscales-mcp/ghcr-io-wyre-technology-ironscales-mcp-v1-2-1