Abnormal Security
OCI · GHCR.IO/WYRE-AI/ABNORMAL-MCP:V1.2.6 · SCANNED SEP 20
MCP server for Abnormal Security — AI-powered email threat detection, cases, and remediation.
Available components
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. How we score → Why this is hard to score →
Supply Chain Security0
- Malware scan not yet available for this package.Unverified
- 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.Unverified
- Install-script risk not yet assessed.Unverified
- 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.Unverified
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 25 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability86
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 830 tokens (~75/item across 11 items; 10 tools + 1 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management83
- Stability observed for 25 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
- Supports UI / widget rendering.Pass
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.
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.
oci · ghcr.io/wyre-ai/abnormal-mcp:v1.2.6
claude mcp add wyre-ai-abnormal-mcp -- docker run --rm -i ghcr.io/wyre-ai/abnormal-mcp:v1.2.6
{
"mcpServers": {
"wyre-ai-abnormal-mcp": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/wyre-ai/abnormal-mcp:v1.2.6"
]
}
}
} {
"servers": {
"wyre-ai-abnormal-mcp": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/wyre-ai/abnormal-mcp:v1.2.6"
]
}
}
} codex mcp add wyre-ai-abnormal-mcp -- docker run --rm -i ghcr.io/wyre-ai/abnormal-mcp:v1.2.6
{
"$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
}
}
} mcp_servers:
wyre-ai-abnormal-mcp:
command: "docker"
args: ["run", "--rm", "-i", "ghcr.io/wyre-ai/abnormal-mcp:v1.2.6"] {
"McpServers": {
"wyre-ai-abnormal-mcp": {
"Transport": "stdio",
"Command": "docker",
"Arguments": [
"run",
"--rm",
"-i",
"ghcr.io/wyre-ai/abnormal-mcp:v1.2.6"
]
}
}
} {
"mcpServers": {
"wyre-ai-abnormal-mcp": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/wyre-ai/abnormal-mcp:v1.2.6"
]
}
}
} 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 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.
- 17 Sept 26 +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.
- 15 Sept 26 +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.
- 13 Sept 26 +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.
- 11 Sept 26 +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.
- 8 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.
- 6 Sept 26 +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.
- 4 Sept 26 +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.
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 · Analysed oci/ghcr.io/wyre-ai/abnormal-mcp:v1.2.6
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | oci |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
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 →
abnormal_abuse_list ~116
List phishing emails reported by users via the Abuse Mailbox. Returns user-submitted reports with analysis results indicating whether Abnormal confirmed the threat.
| Name | Type | Req | Description |
|---|---|---|---|
| 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) |
No output schema declared.
No examples provided.
abnormal_cases_get ~47
Get detailed information about a specific security case by ID. Returns case status, analyst notes, associated threats, and timeline.
| Name | Type | Req | Description |
|---|---|---|---|
| caseId | number | yes | The numeric case ID to retrieve |
No output schema declared.
No examples provided.
abnormal_cases_list ~108
List all active security investigation cases in Abnormal Security. Cases group related threats for analyst review and workflow management.
| Name | Type | Req | Description |
|---|---|---|---|
| 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) |
No output schema declared.
No examples provided.
abnormal_messages_get ~76
Get detailed analysis of a specific message within a threat case. Returns full message metadata, headers, URLs, attachments, and AI-based threat analysis.
| Name | Type | Req | Description |
|---|---|---|---|
| messageId | string | yes | The message ID to retrieve (URL-encoded email message ID) |
| threatId | string | yes | The threat ID (UUID) that contains the message |
No output schema declared.
No examples provided.
abnormal_messages_list ~50
List messages contained within a specific threat case. Returns message IDs and summary data for all emails associated with the threat.
| Name | Type | Req | Description |
|---|---|---|---|
| threatId | string | yes | The threat ID (UUID) to list messages for |
No output schema declared.
No examples provided.
abnormal_navigate ~126
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.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | 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… |
No output schema declared.
No examples provided.
abnormal_remediation_manage ~110
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.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Action to perform: 'remediate' removes the message, 'unremediate' restores it, 'status' checks current state |
| messageId | string | yes | The message ID to remediate |
| threatId | string | yes | The threat ID (UUID) containing the message to remediate |
No output schema declared.
No examples provided.
abnormal_status ~15
Show connection status and available domains
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
abnormal_threats_get ~50
Get detailed information about a specific threat case by ID. Returns threat details including classification, severity, and related message IDs.
| Name | Type | Req | Description |
|---|---|---|---|
| threatId | string | yes | The unique threat ID (UUID format) |
No output schema declared.
No examples provided.
abnormal_threats_list ~110
List detected threats and cases from Abnormal Security. Returns a paginated list of threat IDs with summary information.
| Name | Type | Req | Description |
|---|---|---|---|
| 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) |
No output schema declared.
No examples provided.
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.