Abnormal Security
OCI · GHCR.IO/WYRE-TECHNOLOGY/ABNORMAL-MCP:V1.2.5
MCP server for Abnormal Security — AI-powered email threat detection, cases, and remediation.
Available components
Last scanned (22 hours ago)
Scores higher than 82% of OCI servers
Category Security
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
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
Provenance & Transparency19
- Repository check failed: the declared repository URL redirects; it must resolve directly. See how to fix → View diagnostics → Fail
- 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 56 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 Management97
- Stability observed for 29 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.
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.
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Oct 26 −2
- Stability: pass → 0.83 functional
- 10 Oct 26 +1
- Stability: 0.90 → pass security
- 7 Oct 26 +2
No change was recorded against any check on this day. Stability & Change Management went from 80 to 90. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Oct 26 −3
- Stability: pass → 0.80 functional
- 3 Oct 26 0
- Stability: 0.97 → pass security
- 2 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 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 16 Oct 2026 · Analysed oci/ghcr.io/wyre-technology/abnormal-mcp:v1.2.5
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.
How do I install the Abnormal Security MCP server?
Abnormal Security runs locally as a container image, launched with docker run --rm -i -e ABNORMAL_API_TOKEN -e MCP_TRANSPORT -e AUTH_MODE -e LOG_LEVEL ghcr.io/wyre-technology/abnormal-mcp:v1.2.5. 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-technology/abnormal-mcp:v1.2.5
claude mcp add wyre-technology-abnormal-mcp -- docker run --rm -i -e ABNORMAL_API_TOKEN -e MCP_TRANSPORT -e AUTH_MODE -e LOG_LEVEL ghcr.io/wyre-technology/abnormal-mcp:v1.2.5
This image reads ABNORMAL_API_TOKEN, MCP_TRANSPORT, AUTH_MODE and LOG_LEVEL. Set them in your client's env block for this server; docker run -e passes each one through to the container.
What is the Abnormal Security MCP server?
Abnormal Security is an MCP server listed in the public MCP registry as io.github.wyre-technology/abnormal-mcp. MCP server for Abnormal Security, AI-powered email threat detection, cases, and remediation. This page covers its container image (ghcr.io/wyre-technology/abnormal-mcp:v1.2.5).
Is the Abnormal Security MCP server safe to use?
Abnormal Security scores 51 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 16 October 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.