Avanan
OCI · GHCR.IO/WYRE-AI/AVANAN-MCP
MCP server for Check Point Harmony Email & Collaboration (Avanan) email security.
Available components
Last scanned (20 hours ago)
Scores higher than 60% 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 & 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 0 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 1175 tokens (~83/item across 14 items; 13 tools + 1 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage90
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 69% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 14 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: 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.
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.
- 15 Oct 26 +33
- 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). security
- Tool coverage: unverified → 100 ▲ functional
- Schema quality: unverified → 100 ▲ functional
- 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 functional
- 14 Oct 26 9
First indexed and scored.
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-ai/avanan-mcp@v2.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 →
hec_add_exception ~160
Add an entry to the whitelist or blacklist. At least one match field (senderEmail, senderDomain, subject, attachmentMd5, recipient) must be provided.
| Name | Type | Req | Description |
|---|---|---|---|
| attachmentMd5 | string | – | Attachment MD5 hash |
| comment | string | – | Comment explaining the exception |
| excType | string | yes | 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 | – | – |
No output schema declared.
No examples provided.
hec_delete_exception ~76
⚠ 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.
| Name | Type | Req | Description |
|---|---|---|---|
| excId | string | yes | The exception entity ID to delete |
| excType | string | yes | – |
No output schema declared.
No examples provided.
hec_get_email ~36
Get full details for a specific email entity by its entity ID.
| Name | Type | Req | Description |
|---|---|---|---|
| entityId | string | yes | The entity ID to retrieve |
No output schema declared.
No examples provided.
hec_get_event ~34
Get full details for a specific security event by ID.
| Name | Type | Req | Description |
|---|---|---|---|
| eventId | string | yes | The event ID to retrieve |
No output schema declared.
No examples provided.
hec_get_task_status ~51
Check the status of an action task (quarantine/restore). Use the taskId returned by quarantine or restore tools.
| Name | Type | Req | Description |
|---|---|---|---|
| taskId | string | yes | Task ID from a quarantine or restore action |
No output schema declared.
No examples provided.
hec_list_exceptions ~37
List whitelist or blacklist entries in Checkpoint Harmony Email.
| Name | Type | Req | Description |
|---|---|---|---|
| excType | string | yes | Whether to list the whitelist or blacklist |
No output schema declared.
No examples provided.
hec_quarantine_emails ~85
⚠ 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.
| Name | Type | Req | Description |
|---|---|---|---|
| entityIds | array | yes | List of entity IDs to quarantine |
| entityType | string | – | Entity type (e.g. email) |
No output schema declared.
No examples provided.
hec_quarantine_events ~71
⚠ 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.
| Name | Type | Req | Description |
|---|---|---|---|
| eventIds | array | yes | List of event IDs to quarantine |
No output schema declared.
No examples provided.
hec_query_events ~212
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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) |
No output schema declared.
No examples provided.
hec_restore_emails ~50
Restore specific quarantined email entities by entity ID.
| Name | Type | Req | Description |
|---|---|---|---|
| entityIds | array | yes | List of entity IDs to restore |
| entityType | string | – | Entity type (e.g. email) |
No output schema declared.
No examples provided.
hec_restore_events ~43
Restore one or more previously quarantined events by event ID. Returns task IDs to track progress.
| Name | Type | Req | Description |
|---|---|---|---|
| eventIds | array | yes | List of event IDs to restore |
No output schema declared.
No examples provided.
hec_search_emails ~177
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.).
| Name | Type | Req | Description |
|---|---|---|---|
| endDate | string | – | End date for the search (ISO 8601). |
| filters | array | – | Attribute filters. Each filter has saasAttrName, saasAttrOp, and saasAttrValue. |
| saas | string | yes | 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 | yes | Start date for the search (ISO 8601, required). |
No output schema declared.
No examples provided.
hec_update_exception ~124
Update an existing whitelist or blacklist entry by its entity ID.
| Name | Type | Req | Description |
|---|---|---|---|
| attachmentMd5 | string | – | – |
| comment | string | – | – |
| excId | string | yes | The exception entity ID to update |
| excType | string | yes | – |
| recipient | string | – | – |
| senderDomain | string | – | – |
| senderDomainMatching | string | – | – |
| senderEmail | string | – | – |
| senderEmailMatching | string | – | – |
| senderName | string | – | – |
| subject | string | – | – |
| subjectMatching | string | – | – |
No output schema declared.
No examples provided.
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.
oci · ghcr.io/wyre-ai/avanan-mcp
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.
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.