# Avanan (oci · ghcr.io/wyre-ai/avanan-mcp)

MCP server for Check Point Harmony Email & Collaboration (Avanan) email security.

- Trust score: 42/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-16

## Components

- oci · `ghcr.io/wyre-ai/avanan-mcp`: 42/100 (this document), [markdown](https://verifymcp.io/servers/wyre-ai-avanan-mcp/ghcr-io-wyre-ai-avanan-mcp.md), [page](https://verifymcp.io/servers/wyre-ai-avanan-mcp/ghcr-io-wyre-ai-avanan-mcp)

## Channel facts

- Registry: `oci`
- Package: `ghcr.io/wyre-ai/avanan-mcp`
- Version: `v2.2.5`
- 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-10-16.

- **Supply Chain Security**: 0/100
  - 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.
  - Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
  - Install-script risk not yet assessed.
  - Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
- **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 0 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 1175 tokens (~83/item across 14 items; 13 tools + 1 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 90/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 69% 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.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 14 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: 2 categories.** Categories scored 0 because we could not verify them: 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 Avanan MCP server?

Avanan runs locally as a container image, launched with docker run --rm -i -e AVANAN_CLIENT_ID -e AVANAN_CLIENT_SECRET -e AVANAN_API_URL -e MCP_TRANSPORT -e AUTH_MODE -e LOG_LEVEL ghcr.io/wyre-ai/avanan-mcp:v2.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.

### Claude

```bash
claude mcp add wyre-ai-avanan-mcp -- docker run --rm -i -e AVANAN_CLIENT_ID -e AVANAN_CLIENT_SECRET -e AVANAN_API_URL -e MCP_TRANSPORT -e AUTH_MODE -e LOG_LEVEL ghcr.io/wyre-ai/avanan-mcp:v2.2.5
```

This image reads AVANAN_CLIENT_ID, AVANAN_CLIENT_SECRET, AVANAN_API_URL, 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.

### Cursor

```json
{
  "mcpServers": {
    "wyre-ai-avanan-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "-e",
        "AVANAN_CLIENT_ID",
        "-e",
        "AVANAN_CLIENT_SECRET",
        "-e",
        "AVANAN_API_URL",
        "-e",
        "MCP_TRANSPORT",
        "-e",
        "AUTH_MODE",
        "-e",
        "LOG_LEVEL",
        "ghcr.io/wyre-ai/avanan-mcp:v2.2.5"
      ]
    }
  }
}
```

This image reads AVANAN_CLIENT_ID, AVANAN_CLIENT_SECRET, AVANAN_API_URL, 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.

### VS Code

```json
{
  "servers": {
    "wyre-ai-avanan-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "-e",
        "AVANAN_CLIENT_ID",
        "-e",
        "AVANAN_CLIENT_SECRET",
        "-e",
        "AVANAN_API_URL",
        "-e",
        "MCP_TRANSPORT",
        "-e",
        "AUTH_MODE",
        "-e",
        "LOG_LEVEL",
        "ghcr.io/wyre-ai/avanan-mcp:v2.2.5"
      ]
    }
  }
}
```

This image reads AVANAN_CLIENT_ID, AVANAN_CLIENT_SECRET, AVANAN_API_URL, 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.

### Codex

```bash
codex mcp add wyre-ai-avanan-mcp -- docker run --rm -i -e AVANAN_CLIENT_ID -e AVANAN_CLIENT_SECRET -e AVANAN_API_URL -e MCP_TRANSPORT -e AUTH_MODE -e LOG_LEVEL ghcr.io/wyre-ai/avanan-mcp:v2.2.5
```

This image reads AVANAN_CLIENT_ID, AVANAN_CLIENT_SECRET, AVANAN_API_URL, 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.

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "wyre-ai-avanan-mcp": {
      "type": "local",
      "command": [
        "docker",
        "run",
        "--rm",
        "-i",
        "-e",
        "AVANAN_CLIENT_ID",
        "-e",
        "AVANAN_CLIENT_SECRET",
        "-e",
        "AVANAN_API_URL",
        "-e",
        "MCP_TRANSPORT",
        "-e",
        "AUTH_MODE",
        "-e",
        "LOG_LEVEL",
        "ghcr.io/wyre-ai/avanan-mcp:v2.2.5"
      ],
      "enabled": true
    }
  }
}
```

This image reads AVANAN_CLIENT_ID, AVANAN_CLIENT_SECRET, AVANAN_API_URL, 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.

### Hermes

```yaml
mcp_servers:
  wyre-ai-avanan-mcp:
    command: "docker"
    args: ["run", "--rm", "-i", "-e", "AVANAN_CLIENT_ID", "-e", "AVANAN_CLIENT_SECRET", "-e", "AVANAN_API_URL", "-e", "MCP_TRANSPORT", "-e", "AUTH_MODE", "-e", "LOG_LEVEL", "ghcr.io/wyre-ai/avanan-mcp:v2.2.5"]
```

This image reads AVANAN_CLIENT_ID, AVANAN_CLIENT_SECRET, AVANAN_API_URL, 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.

### Netclaw

```json
{
  "McpServers": {
    "wyre-ai-avanan-mcp": {
      "Transport": "stdio",
      "Command": "docker",
      "Arguments": [
        "run",
        "--rm",
        "-i",
        "-e",
        "AVANAN_CLIENT_ID",
        "-e",
        "AVANAN_CLIENT_SECRET",
        "-e",
        "AVANAN_API_URL",
        "-e",
        "MCP_TRANSPORT",
        "-e",
        "AUTH_MODE",
        "-e",
        "LOG_LEVEL",
        "ghcr.io/wyre-ai/avanan-mcp:v2.2.5"
      ]
    }
  }
}
```

This image reads AVANAN_CLIENT_ID, AVANAN_CLIENT_SECRET, AVANAN_API_URL, 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.

### Other

```json
{
  "mcpServers": {
    "wyre-ai-avanan-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "-e",
        "AVANAN_CLIENT_ID",
        "-e",
        "AVANAN_CLIENT_SECRET",
        "-e",
        "AVANAN_API_URL",
        "-e",
        "MCP_TRANSPORT",
        "-e",
        "AUTH_MODE",
        "-e",
        "LOG_LEVEL",
        "ghcr.io/wyre-ai/avanan-mcp:v2.2.5"
      ]
    }
  }
}
```

This image reads AVANAN_CLIENT_ID, AVANAN_CLIENT_SECRET, AVANAN_API_URL, 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.

## 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-10-15 (score 42, +33)

- [security improvement] Injection markers: unverified → pass
- [security] First check of Judged manipulation: pass
- [security] Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window).
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] Schema quality: unverified → 100
- [functional improvement] MCP protocol: unverified → pass
- [functional] First check of Schema quality: fail
- [functional] First check of Schema quality: excellent
- [functional] First check of Capabilities: pass
- [functional] First check of Destructive annotations: 100
- [functional] First check of Schema quality: pass
- [functional] First check of Tool coverage: 69
- [functional] Package version: v2.2.4 → v2.2.5

### 2026-10-14 (score 9)

First indexed and scored.

## MCP tools (13)

### `hec_query_events` (~212 tokens)

Query Checkpoint Harmony Email security events (phishing, malware, DLP, anomaly, shadow IT, etc.). Supports filtering by type, state, severity, date range, and SaaS platform. Returns events with available remediation actions.

Input parameters:

- `endDate` (string): End date/time (ISO 8601). Defaults to now.
- `eventIds` (array): Fetch specific event IDs
- `eventStates` (array): Filter by event state(s). Defaults to new/detected if omitted.
- `eventTypes` (array): Filter by event type(s)
- `saas` (array): Filter by SaaS platform(s)
- `scrollId` (string): Scroll ID for pagination (from previous response)
- `severities` (array): Filter by severity level(s) (e.g. Critical, High, Medium, Low)
- `startDate` (string): Start date/time (ISO 8601, e.g. 2026-01-01T00:00:00Z)

### `hec_get_event` (~34 tokens)

Get full details for a specific security event by ID.

Input parameters:

- `eventId` (string, required): The event ID to retrieve

### `hec_search_emails` (~177 tokens)

Search email and SaaS entities in Checkpoint Harmony Email. Filter by sender, recipient, subject, SaaS platform, and date range. Use extended filters for precise attribute matching (contains, startsWith, isEmpty, etc.).

Input parameters:

- `endDate` (string): End date for the search (ISO 8601).
- `filters` (array): Attribute filters. Each filter has saasAttrName, saasAttrOp, and saasAttrValue.
- `saas` (string, required): SaaS platform to search (required). E.g. office365_emails, google_mail.
- `saasEntity` (string): SaaS entity type filter (optional).
- `scrollId` (string): Scroll ID for pagination
- `startDate` (string, required): Start date for the search (ISO 8601, required).

### `hec_get_email` (~36 tokens)

Get full details for a specific email entity by its entity ID.

Input parameters:

- `entityId` (string, required): The entity ID to retrieve

### `hec_quarantine_events` (~71 tokens)

⚠ HIGH-IMPACT. Quarantine one or more security events by event ID. Quarantining is reversible via restore but affects user access to events. Returns task IDs to track progress. Confirm with the user before invoking.

Input parameters:

- `eventIds` (array, required): List of event IDs to quarantine

### `hec_restore_events` (~43 tokens)

Restore one or more previously quarantined events by event ID. Returns task IDs to track progress.

Input parameters:

- `eventIds` (array, required): List of event IDs to restore

### `hec_quarantine_emails` (~85 tokens)

⚠ HIGH-IMPACT. Quarantine specific email entities by entity ID. Quarantining is reversible via restore but affects user access to emails. Returns task IDs to track progress. Confirm with the user before invoking.

Input parameters:

- `entityIds` (array, required): List of entity IDs to quarantine
- `entityType` (string): Entity type (e.g. email)

### `hec_restore_emails` (~50 tokens)

Restore specific quarantined email entities by entity ID.

Input parameters:

- `entityIds` (array, required): List of entity IDs to restore
- `entityType` (string): Entity type (e.g. email)

### `hec_get_task_status` (~51 tokens)

Check the status of an action task (quarantine/restore). Use the taskId returned by quarantine or restore tools.

Input parameters:

- `taskId` (string, required): Task ID from a quarantine or restore action

### `hec_list_exceptions` (~37 tokens)

List whitelist or blacklist entries in Checkpoint Harmony Email.

Input parameters:

- `excType` (string, required): Whether to list the whitelist or blacklist

### `hec_add_exception` (~160 tokens)

Add an entry to the whitelist or blacklist. At least one match field (senderEmail, senderDomain, subject, attachmentMd5, recipient) must be provided.

Input parameters:

- `attachmentMd5` (string): Attachment MD5 hash
- `comment` (string): Comment explaining the exception
- `excType` (string, required): Whether to add to the whitelist or blacklist
- `recipient` (string): Recipient email address
- `senderDomain` (string): Sender domain
- `senderDomainMatching` (string)
- `senderEmail` (string): Sender email address
- `senderEmailMatching` (string)
- `senderName` (string): Sender display name
- `subject` (string): Email subject
- `subjectMatching` (string)

### `hec_update_exception` (~124 tokens)

Update an existing whitelist or blacklist entry by its entity ID.

Input parameters:

- `attachmentMd5` (string)
- `comment` (string)
- `excId` (string, required): The exception entity ID to update
- `excType` (string, required)
- `recipient` (string)
- `senderDomain` (string)
- `senderDomainMatching` (string)
- `senderEmail` (string)
- `senderEmailMatching` (string)
- `senderName` (string)
- `subject` (string)
- `subjectMatching` (string)

### `hec_delete_exception` (~76 tokens)

⚠ DESTRUCTIVE — IRREVERSIBLE. Delete a whitelist or blacklist entry by its entity ID. This action cannot be undone and will permanently remove the exception from security policy. Confirm with the user before invoking.

Input parameters:

- `excId` (string, required): The exception entity ID to delete
- `excType` (string, required)

## Diagnostics

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

## Score history

- 2026-10-16: 42
- 2026-10-15: 42
- 2026-10-14: 9

## Common questions

### What is the Avanan MCP server?

Avanan is an MCP server listed in the public MCP registry as io.github.WYRE-AI/avanan-mcp. MCP server for Check Point Harmony Email & Collaboration (Avanan) email security. This page covers its container image (ghcr.io/wyre-ai/avanan-mcp).

### Is the Avanan MCP server safe to use?

Avanan scores 42 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 Avanan MCP server expose?

Avanan exposes 13 tools: hec_query_events, hec_get_event, hec_search_emails, hec_get_email, hec_quarantine_events, and 8 more. Their descriptions and schemas cost roughly 1,156 tokens of context every time the server is loaded.

### Is the Avanan MCP server still maintained?

Avanan 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 Avanan MCP server under?

Avanan 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

- GitHub Container Registry: https://ghcr.io/wyre-ai/avanan-mcp
- Repository: https://github.com/WYRE-AI/avanan-mcp
- Changelog RSS feed: https://verifymcp.io/servers/wyre-ai-avanan-mcp/ghcr-io-wyre-ai-avanan-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/wyre-ai-avanan-mcp/ghcr-io-wyre-ai-avanan-mcp.json
- HTML version of this page: https://verifymcp.io/servers/wyre-ai-avanan-mcp/ghcr-io-wyre-ai-avanan-mcp