# Abnormal Security (oci · ghcr.io/wyre-ai/abnormal-mcp:v1.2.6)

MCP server for Abnormal Security — AI-powered email threat detection, cases, and remediation.

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

## Components

- oci · `ghcr.io/wyre-ai/abnormal-mcp:v1.2.6`: 54/100 (this document), [markdown](https://verifymcp.io/servers/wyre-ai-abnormal-mcp/ghcr-io-wyre-ai-abnormal-mcp-v1-2-6.md), [page](https://verifymcp.io/servers/wyre-ai-abnormal-mcp/ghcr-io-wyre-ai-abnormal-mcp-v1-2-6)

## Channel facts

- Registry: `oci`
- Package: `ghcr.io/wyre-ai/abnormal-mcp:v1.2.6`
- 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-09-20.

- **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 25 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 86/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 830 tokens (~75/item across 11 items; 10 tools + 1 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 83/100
  - Stability observed for 25 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.
- **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 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.
  - Supports UI / widget rendering.

**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

### How do I install the Abnormal Security MCP server?

Abnormal Security runs locally as a container image, launched with docker run --rm -i ghcr.io/wyre-ai/abnormal-mcp:v1.2.6. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add wyre-ai-abnormal-mcp -- docker run --rm -i ghcr.io/wyre-ai/abnormal-mcp:v1.2.6
```

### Cursor

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

### VS Code

```json
{
  "servers": {
    "wyre-ai-abnormal-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/wyre-ai/abnormal-mcp:v1.2.6"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add wyre-ai-abnormal-mcp -- docker run --rm -i ghcr.io/wyre-ai/abnormal-mcp:v1.2.6
```

### opencode

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

### Hermes

```yaml
mcp_servers:
  wyre-ai-abnormal-mcp:
    command: "docker"
    args: ["run", "--rm", "-i", "ghcr.io/wyre-ai/abnormal-mcp:v1.2.6"]
```

### Netclaw

```json
{
  "McpServers": {
    "wyre-ai-abnormal-mcp": {
      "Transport": "stdio",
      "Command": "docker",
      "Arguments": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/wyre-ai/abnormal-mcp:v1.2.6"
      ]
    }
  }
}
```

### Other

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

## 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 54, +1)

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

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

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

### 2026-09-15 (score 52, +1)

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

### 2026-09-13 (score 51, +1)

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

### 2026-09-11 (score 50, +1)

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

### 2026-09-08 (score 49, +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.

### 2026-09-06 (score 48, +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-09-04 (score 47, +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.

## MCP tools (10)

### `abnormal_navigate` (~126 tokens)

Discover available Abnormal Security tools by domain. Returns tool names and descriptions for the selected domain. All tools are callable at any time — this is a help/discovery aid, not a prerequisite.

Input parameters:

- `domain` (string, required): The domain to explore: - threats: Threat detection — list and inspect detected threat cases - messages: Message analysis — list and inspect individual emails within a threat - remediation: Remediatio…

### `abnormal_status` (~15 tokens)

Show connection status and available domains

### `abnormal_threats_list` (~110 tokens)

List detected threats and cases from Abnormal Security. Returns a paginated list of threat IDs with summary information.

Input parameters:

- `filter` (string): OData filter expression (e.g. 'receivedTime gt 2024-01-01T00:00:00Z')
- `pageNumber` (number): Page number to retrieve (1-indexed, default: 1)
- `pageSize` (number): Number of results per page (default: 100, max: 100)

### `abnormal_threats_get` (~50 tokens)

Get detailed information about a specific threat case by ID. Returns threat details including classification, severity, and related message IDs.

Input parameters:

- `threatId` (string, required): The unique threat ID (UUID format)

### `abnormal_messages_list` (~50 tokens)

List messages contained within a specific threat case. Returns message IDs and summary data for all emails associated with the threat.

Input parameters:

- `threatId` (string, required): The threat ID (UUID) to list messages for

### `abnormal_messages_get` (~76 tokens)

Get detailed analysis of a specific message within a threat case. Returns full message metadata, headers, URLs, attachments, and AI-based threat analysis.

Input parameters:

- `messageId` (string, required): The message ID to retrieve (URL-encoded email message ID)
- `threatId` (string, required): The threat ID (UUID) that contains the message

### `abnormal_remediation_manage` (~110 tokens)

Trigger or check the status of a remediation action for a specific threat message. Supports requesting remediation (removal from mailboxes) or checking current remediation status.

Input parameters:

- `action` (string, required): Action to perform: 'remediate' removes the message, 'unremediate' restores it, 'status' checks current state
- `messageId` (string, required): The message ID to remediate
- `threatId` (string, required): The threat ID (UUID) containing the message to remediate

### `abnormal_abuse_list` (~116 tokens)

List phishing emails reported by users via the Abuse Mailbox. Returns user-submitted reports with analysis results indicating whether Abnormal confirmed the threat.

Input parameters:

- `filter` (string): OData filter expression (e.g. 'firstReportedTime gt 2024-01-01T00:00:00Z')
- `pageNumber` (number): Page number to retrieve (1-indexed, default: 1)
- `pageSize` (number): Number of results per page (default: 100, max: 100)

### `abnormal_cases_list` (~108 tokens)

List all active security investigation cases in Abnormal Security. Cases group related threats for analyst review and workflow management.

Input parameters:

- `filter` (string): OData filter expression (e.g. 'createdTime gt 2024-01-01T00:00:00Z')
- `pageNumber` (number): Page number to retrieve (1-indexed, default: 1)
- `pageSize` (number): Number of results per page (default: 100, max: 100)

### `abnormal_cases_get` (~47 tokens)

Get detailed information about a specific security case by ID. Returns case status, analyst notes, associated threats, and timeline.

Input parameters:

- `caseId` (number, required): The numeric case ID to retrieve

## Diagnostics

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

## Score history

- 2026-09-20: 54
- 2026-09-19: 54
- 2026-09-18: 53
- 2026-09-17: 53
- 2026-09-16: 52
- 2026-09-15: 52
- 2026-09-14: 51
- 2026-09-13: 51
- 2026-09-12: 50
- 2026-09-11: 50
- 2026-09-10: 49
- 2026-09-09: 49
- 2026-09-08: 49
- 2026-09-07: 48
- 2026-09-06: 48
- 2026-09-05: 47
- 2026-09-04: 47
- 2026-09-03: 46
- 2026-09-02: 42
- 2026-09-01: 42
- 2026-08-31: 42
- 2026-08-30: 42
- 2026-08-29: 42
- 2026-08-28: 42
- 2026-08-27: 42
- 2026-08-26: 42

## Common questions

### What is the Abnormal Security MCP server?

Abnormal Security is an MCP server listed in the public MCP registry as io.github.WYRE-AI/abnormal-mcp. MCP server for Abnormal Security, AI-powered email threat detection, cases, and remediation. This page covers its container image (ghcr.io/wyre-ai/abnormal-mcp:v1.2.6).

### Is the Abnormal Security MCP server safe to use?

Abnormal Security scores 54 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 Abnormal Security MCP server expose?

Abnormal Security exposes 10 tools: abnormal_navigate, abnormal_status, abnormal_threats_list, abnormal_threats_get, abnormal_messages_list, and 5 more. Their descriptions and schemas cost roughly 808 tokens of context every time the server is loaded.

### Is the Abnormal Security MCP server still maintained?

Abnormal Security 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.

### What licence is the Abnormal Security MCP server under?

Abnormal Security declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- Repository: https://github.com/WYRE-AI/abnormal-mcp
- Changelog RSS feed: https://verifymcp.io/servers/wyre-ai-abnormal-mcp/ghcr-io-wyre-ai-abnormal-mcp-v1-2-6.xml
- Changelog JSON feed: https://verifymcp.io/servers/wyre-ai-abnormal-mcp/ghcr-io-wyre-ai-abnormal-mcp-v1-2-6.json
- HTML version of this page: https://verifymcp.io/servers/wyre-ai-abnormal-mcp/ghcr-io-wyre-ai-abnormal-mcp-v1-2-6