Avanan

io.github.wyre-technologyPublished by GitHub account wyre-technologyv2.2.2Updated Oct 24, 2026

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

VerifiedSTDIODesktop onlyCommunication & CollaborationSecurity & Monitoring

Overview

AI-generated overview

Connects an AI assistant to Check Point Harmony Email & Collaboration (Avanan) for email security events, threat investigation, and remediation actions.

What you can do
This MCP server exposes Check Point Avanan (Harmony Email & Collaboration) to an MCP-compatible assistant. Its domains cover security event retrieval and investigation, actions on threats such as quarantine and release, management of email exceptions and allowlists, and search across email security data. One tool, hec_get_event, can render a read-only interactive event card in MCP Apps hosts showing severity, state, platform, and remediation status.
When to use it
Use it when an assistant needs to triage or investigate email security incidents, look up events, or apply remediation such as quarantining or releasing messages in an Avanan environment. It is also aimed at multi-tenant MSP operations across several email security tenants.
Requirements
Runs locally over stdio (the container image defaults to http). Needs Node.js for the npm package or Docker for the image, network access to the Avanan API, and Avanan/Check Point OAuth2 credentials supplied as AVANAN_CLIENT_ID and AVANAN_CLIENT_SECRET. AUTH_MODE selects whether credentials come from local environment variables or from gateway header injection; AVANAN_API_URL and LOG_LEVEL are optional.
Before you install
The server requires the secret AVANAN_CLIENT_SECRET together with AVANAN_CLIENT_ID, so store them securely and avoid exposing them in shared configs or logs. Its action domain can change state in your email security environment, for example quarantining or releasing messages, and exception or allowlist changes affect filtering, so review such operations before approving them. The README also lists CHECKPOINT_CLIENT_ID and CHECKPOINT_CLIENT_SECRET as the credential variables.

Installation

In SourceWeft

  1. Open Avanan in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

Avanan (Check Point) MCP Server

[License] [Node.js]

A Model Context Protocol (MCP) server for Check Point Avanan (Harmony Email & Collaboration). Enables AI assistants to manage security events, investigate threats, and handle multi-tenant MSP operations across your email security environment.

This is a Model Context Protocol (MCP) server that connects Claude (or any MCP-compatible AI) to your Check Point Avanan environment.

Part of the MSP Claude Plugins ecosystem — a growing suite of AI integrations for the MSP stack. Built by MSPs, for MSPs.

Features

  • Interactive Security Event Card (MCP Apps): hec_get_event renders as a read-only interactive card in MCP Apps hosts (Claude Desktop/web) showing severity, state, platform, and remediation status; neutral by default, brandable via window.__BRAND__ injection or MCP_BRAND_* env vars; plain-JSON behavior is unchanged in other hosts

Installation

bash
npm install @wyre-ai/avanan-mcp

Configuration

Copy .env.example and set the variables below. Leave CONDUIT_S2S_SECRET empty in that file.

VariableRequiredDescription
CHECKPOINT_CLIENT_IDFor stdio and AUTH_MODE=envCheckpoint/Avanan OAuth2 client ID
CHECKPOINT_CLIENT_SECRETFor stdio and AUTH_MODE=envCheckpoint/Avanan OAuth2 client secret
CHECKPOINT_REGIONNoAPI region (us, eu, au, in). Auto-detected from the JWT when omitted.
MCP_TRANSPORTNostdio (default) or http
AUTH_MODENogateway (Docker image and Compose default) or env. Gateway mode requires X-Checkpoint-Client-Id and X-Checkpoint-Client-Secret on each /mcp request and never falls back to CHECKPOINT_*. env uses those variables only after S2S auth succeeds.
CONDUIT_S2S_SECRETYes for HTTPService-to-service HMAC secret. The HTTP server logs an error and exits non-zero when this is empty or a known placeholder (changeme, replace-with-a-real-secret, your-s2s-secret, and the other public example values). MCP_ALLOW_INSECURE_DEV=1 does not accept a placeholder. Compose will not start without it. Never commit a real value. The value is never logged. Generate one with openssl rand -hex 32.
MCP_ALLOW_INSECURE_DEVNoSet to exactly 1 only for local development to start HTTP without CONDUIT_S2S_SECRET. The process logs a warning, does not enforce X-Gateway-S2S, and binds 127.0.0.1 only. A non-loopback MCP_HTTP_HOST (including 0.0.0.0) is overridden and the override is logged.
MCP_HTTP_HOSTNoBind address when MCP_TRANSPORT=http. Defaults to 127.0.0.1. A configured secret honors this value. The container image sets 0.0.0.0.
MCP_HTTP_PORTNoHTTP port. Defaults to 8080.

/health stays unauthenticated. The stdio transport does not use CONDUIT_S2S_SECRET.

HTTP authentication

With MCP_TRANSPORT=http and a real CONDUIT_S2S_SECRET, every /mcp request must include X-Gateway-S2S. The header value is t=<unix seconds>,v1=<hex>, where the hex is HMAC-SHA256 of the literal string t=<unix seconds> keyed with CONDUIT_S2S_SECRET (64 lowercase hex characters). The timestamp must be within 300 seconds of the server clock. A missing or invalid header returns HTTP 401 before vendor credentials are read.

bash
TS=$(date +%s)SIG=$(printf 't=%s' "$TS" | openssl dgst -sha256 -hmac "$CONDUIT_S2S_SECRET" -hex | awk '{print $NF}')curl -sS http://127.0.0.1:8080/mcp \  -H 'Content-Type: application/json' \  -H 'Accept: application/json, text/event-stream' \  -H "X-Gateway-S2S: t=${TS},v1=${SIG}" \  -H 'X-Checkpoint-Client-Id: your-client-id' \  -H 'X-Checkpoint-Client-Secret: your-client-secret' \  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

In AUTH_MODE=gateway (the image and Compose default), /mcp also requires X-Checkpoint-Client-Id and X-Checkpoint-Client-Secret. Those headers are the only credential source for that request. A request missing either one returns 401 and does not fall back to CHECKPOINT_CLIENT_ID / CHECKPOINT_CLIENT_SECRET in the process environment.

Single-tenant HTTP (AUTH_MODE=env) still requires a valid X-Gateway-S2S header, then uses CHECKPOINT_CLIENT_ID and CHECKPOINT_CLIENT_SECRET when the request does not carry those headers.

Usage

Running with Claude Desktop

Add to your Claude Desktop claude_desktop_config.json:

json
{  "mcpServers": {    "avanan-mcp": {      "command": "npx",      "args": ["@wyre-ai/avanan-mcp"],      "env": {        "CHECKPOINT_CLIENT_ID": "your-checkpoint-client-id"        "CHECKPOINT_CLIENT_SECRET": "your-checkpoint-client-secret"      }    }  }}

Running with Claude Code (CLI)

bash
claude mcp add avanan-mcp \  -e CHECKPOINT_CLIENT_ID=your-value \  -e CHECKPOINT_CLIENT_SECRET=your-value \  -- npx -y @wyre-ai/avanan-mcp

Docker

The image listens on 0.0.0.0 inside the container (MCP_HTTP_HOST) and defaults to AUTH_MODE=gateway. Publish the port on loopback and pass a real S2S secret. In gateway mode, Checkpoint credentials arrive on each request as headers; they are not read from the environment.

bash
docker build -t avanan-mcp .docker run \  -e CONDUIT_S2S_SECRET=your-s2s-secret \  -p 127.0.0.1:8080:8080 \  avanan-mcp

Compose refuses to start when CONDUIT_S2S_SECRET is unset, sets AUTH_MODE=gateway, does not inject CHECKPOINT_CLIENT_ID or CHECKPOINT_CLIENT_SECRET, and publishes 127.0.0.1:8080:8080:

bash
CONDUIT_S2S_SECRET=your-s2s-secret docker compose up

Single-tenant HTTP (AUTH_MODE=env) still requires the S2S secret, then uses CHECKPOINT_CLIENT_ID and CHECKPOINT_CLIENT_SECRET. Keep that off the gateway Compose service:

bash
docker run \  -e CONDUIT_S2S_SECRET=your-s2s-secret \  -e AUTH_MODE=env \  -e CHECKPOINT_CLIENT_ID=your-value \  -e CHECKPOINT_CLIENT_SECRET=your-value \  -e CHECKPOINT_REGION=us \  -p 127.0.0.1:8080:8080 \  avanan-mcp

Local HTTP without a secret is development-only. It binds 127.0.0.1 even when MCP_HTTP_HOST is 0.0.0.0 or localhost, and logs a warning. A known placeholder secret still refuses to start:

bash
MCP_TRANSPORT=http MCP_ALLOW_INSECURE_DEV=1 npm start

Available Domains

Events

Security event retrieval and investigation

Actions

Take action on threats (quarantine, release, etc.)

Exceptions

Manage email exceptions and allowlists

Search

Search across email security data

Development

bash
# Clone the repositorygit clone https://github.com/WYRE-AI/avanan-mcp.gitcd avanan-mcp
# Install dependenciesnpm install
# Buildnpm run build
# Run testsnpm test

Contributing

Contributions are welcome! Please see CONTRIBUTING.md if present, or open an issue to discuss changes.

License

Licensed under the Apache License, Version 2.0. See LICENSE for details.

Source: README.md at commit a4af4ce

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v2.2.2LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts