avanan-legacy-mcp
This MCP server exposes the legacy Avanan SmartAPI for MSP tenant management and per-tenant security operations across configured Avanan regions.
Diagnostics: verify credentials, inspect key scopes, and probe MSP access with
avanan_test_connectionandavanan_list_scopes.Security events: query events with filters like SaaS, type, state, severity, dates, description, and fetch single event details.
Secured entities: search emails/SaaS objects by platform, date range, and attribute filters; fetch entity details.
Exceptions: list, view, add, update, and irreversibly delete whitelist/blacklist entries.
Remediation: quarantine/restore events or emails and check asynchronous task status.
Child MSPs: list, create, and delete child MSP partners (deletion also removes associated tenants).
MSP users: list, view, create, update, and delete MSP users, optionally scoped to a child MSP.
Customer tenants: list, view, create, and delete tenants;
avanan_get_tenantcan render an interactive tenant card in MCP Apps hosts.Licenses: list license packages/add-ons and assign a license with optional add-ons to a tenant.
Usage: get monthly or daily usage across customer tenants, optionally filtered to child MSPs.
Auth/transport: run over stdio or HTTP with env- or gateway-provided Avanan credentials and HMAC S2S protection for HTTP.
avanan-legacy-mcp
MCP server for the legacy Avanan SmartAPI on smart-api-production-*.avanan.net:
MSP tenant management plus per-tenant security (events, entities, exceptions, remediation).
Distinct from avanan-mcp, which targets the Check Point Infinity Portal HEC API.
Implements the Avanan MSP SmartAPI Reference Guide (22 July 2026) and the Avanan SmartAPI Reference Guide (Feb 2024):
Group | Tools |
Diagnostics |
|
Security events |
|
Secured entities |
|
Exceptions |
|
Remediation |
|
Child MSPs |
|
MSP users |
|
Customer tenants |
|
Licenses |
|
Usage |
|
Features
Interactive tenant card (MCP Apps, SEP-1865):
avanan_get_tenantrenders as an interactive card in MCP Apps hosts (Claude Desktop/web) showing domain, status, deployment mode, license package, protected users, PoC dates, and add-ons. The card is read-only, neutral by default, and brandable viawindow.__BRAND__injection orMCP_BRAND_*env vars (MCP_BRAND_NAME,MCP_BRAND_LOGO_URL,MCP_BRAND_PRIMARY_COLOR,MCP_BRAND_ACCENT_COLOR,MCP_BRAND_BG,MCP_BRAND_TEXT). Plain-JSON behavior is unchanged in other hosts. Rebuild the embedded card HTML after editingui/withnpm run build:ui.
Related MCP server: abnormal-mcp
Configuration
Env var | Required | Description |
| For stdio and | SmartAPI Client ID (sent as |
| For stdio and | SmartAPI Client Secret. Only ever used to sign requests; never sent on the wire. |
| no |
|
| no |
|
| no |
|
| no | Bind address when |
| no | HTTP transport port (default 8080). |
| no |
|
| Yes for HTTP | Service-to-service secret. HTTP logs an error and exits non-zero when this is empty or a known placeholder ( |
| no | Set to exactly |
Copy .env.example. Leave CONDUIT_S2S_SECRET empty there.
/health stays unauthenticated and does not read credentials. The stdio transport does not use CONDUIT_S2S_SECRET or X-Gateway-S2S.
HTTP authentication
With MCP_TRANSPORT=http and a real CONDUIT_S2S_SECRET, every request except /health must include X-Gateway-S2S:
t=<unix seconds>,v1=<hex>v1 is HMAC-SHA256 over the ASCII string t=<unix seconds> (the same t= prefix that starts the header), keyed with CONDUIT_S2S_SECRET, encoded as 64 lowercase hex characters. The timestamp must be within 300 seconds of the server clock. The comparison is timing-safe. A missing or invalid header returns 401 and does not touch Avanan credentials. The secret is never logged.
In AUTH_MODE=gateway, the request must also include X-Avanan-Client-Id and X-Avanan-Client-Secret (X-Avanan-Region is optional). Those headers are the only credential source. A request missing either one returns 401 and does not fall back to AVANAN_CLIENT_ID / AVANAN_CLIENT_SECRET.
In AUTH_MODE=env, /mcp still requires a valid X-Gateway-S2S header. Vendor credentials come from the environment when the request does not carry both client headers.
Docker
The image listens on 0.0.0.0 inside the container (MCP_HTTP_HOST) and sets AUTH_MODE=gateway. Publish the port on loopback and pass the S2S secret. In gateway mode, Avanan credentials arrive on each request as headers; they are not read from the environment.
docker build -t avanan-legacy-mcp .
docker run \
-e CONDUIT_S2S_SECRET="$CONDUIT_S2S_SECRET" \
-p 127.0.0.1:8080:8080 \
avanan-legacy-mcpCompose refuses to start when CONDUIT_S2S_SECRET is unset, sets AUTH_MODE=gateway, publishes 127.0.0.1:8080:8080, and does not put AVANAN_CLIENT_ID or AVANAN_CLIENT_SECRET in the service environment:
CONDUIT_S2S_SECRET="$CONDUIT_S2S_SECRET" docker compose upSingle-tenant HTTP (AUTH_MODE=env) still requires the S2S secret, then uses AVANAN_CLIENT_ID and AVANAN_CLIENT_SECRET. That is separate from the gateway Compose service.
docker run \
-e CONDUIT_S2S_SECRET="$CONDUIT_S2S_SECRET" \
-e AUTH_MODE=env \
-e AVANAN_CLIENT_ID=your-client-id \
-e AVANAN_CLIENT_SECRET=your-client-secret \
-e AVANAN_REGION=us \
-p 127.0.0.1:8080:8080 \
avanan-legacy-mcpLocal HTTP without a secret is development-only. It binds 127.0.0.1 even if MCP_HTTP_HOST is 0.0.0.0, and logs a warning:
MCP_TRANSPORT=http MCP_ALLOW_INSECURE_DEV=1 npm startGenerate a secret with openssl rand -hex 32. Do not leave a placeholder in CONDUIT_S2S_SECRET; startup treats those values as unset and exits.
The server performs the token handshake itself: it calls GET /v1.0/auth, caches the
one-hour JWT per client ID, and refreshes it a minute before expiry.
The MSP-management tools need anMSP API key. These are not self-service: Check
Point/Avanan Support issues them on request, through your distributor if you buy Avanan
through the channel, one per region. A key generated inside a customer tenant
authenticates successfully, but every /msp/* endpoint then answers
403 MSP endpoint, access denied. The security tools (events, entities, exceptions,
remediation) work with either kind of key. avanan_test_connection reports which kind
you have.
With an MSP key, the security tools cover every managed customer; pass scopes (query
and search) or scope (actions) with values from avanan_list_scopes to target one.
Parent MSPs can scope list and create calls to a child MSP with the optional MSPId
argument (msp_ids on the usage tools), as in Check Point's reference client.
Authentication details
The wire format was verified against the live US endpoint in September 2026 and is pinned
by tests/client.test.ts. Two details differ from the reference guide:
x-av-datemust not end inZ(2026-09-09T16:49:12.123). The documented.000Zform makes the API return HTTP 500.x-av-sigissha256(base64(reqId + clientId + date + path?query + secret))as hex. The path is omitted on the/authcall only, and the/authresponse body is the raw JWT rather than JSON.
Both match Check Point's reference
client.py.
Build
npm install
npm run build
npm startRegional endpoints
Region | Base |
|
|
|
|
|
|
|
|
|
|
|
|
All endpoints sit under /v1.0/msp/....
Available Tools
33 toolsavanan_add_exceptionA
Add a whitelist or blacklist entry. Provide at least one match field (senderEmail, senderDomain, senderName, recipient, subject, attachmentMd5, linkDomains, senderIp).
Inputs: excType (required), comment, subject, senderIp, +17 more.
avanan_assign_licenseB
Assign a license (and optional add-ons) to an existing customer tenant.
Inputs: tenant_id (required), licenseCodeName (required), addonIdList, maxLicensedUsers.
avanan_create_msp_partnerB
Create a new child MSP partner under the current MSP (msppartners-extended endpoint, July 2026 guide).
Inputs: zip (required), name (required), country (required), website (required), +1 more.
avanan_create_msp_userA
Create a new MSP user.
Inputs: role (required), email (required), lastName (required), firstName (required), +6 more.
avanan_create_tenantB
Create a new customer tenant under the current MSP.
Inputs: phone (required), adminName (required), adminEmail (required), tenantName (required), +3 more.
avanan_delete_exceptionADestructive
DESTRUCTIVE and irreversible: delete a whitelist or blacklist entry by its entity ID. Confirm with the user before invoking.
Inputs: excId (required), excType (required).
avanan_delete_msp_partnerA
Delete a child MSP partner by ID. WARNING: all tenants associated with this MSP are also deleted.
Inputs: msp_id (required).
avanan_delete_msp_userA
Delete an MSP user by ID.
Inputs: user_id (required).
avanan_delete_tenantA
Delete a customer tenant by ID. WARNING: this deletes the tenant and all its data.
Inputs: tenant_id (required).
avanan_get_daily_usageB
Get daily usage details across all customer tenants for a specific year/month/day.
Inputs: day (required), year (required), month (required), msp_ids, +1 more.
avanan_get_emailB
Get full details of one secured entity (email, file, message) by its Avanan entity ID.
Inputs: entityId (required).
avanan_get_eventA
Get full details of one security event by its Avanan event ID.
Inputs: eventId (required).
avanan_get_exceptionA
Get one whitelist or blacklist entry by its entity ID.
Inputs: excId (required), excType (required).
avanan_get_monthly_usageA
Get monthly usage details across all customer tenants for a given year/month. Returns per-day, per-tenant rows with user count, daily price, and cost.
Inputs: year (required), month (required), msp_ids, scrollId.
avanan_get_msp_userA
Get a single MSP user by ID.
Inputs: user_id (required).
avanan_get_task_statusA
Check the state of a quarantine/restore task by the task ID an action returned.
Inputs: taskId (required).
avanan_get_tenantA
Get details of a single customer tenant by ID, including license, PoC/paid dates, user count, and expiration.
Inputs: tenant_id (required).
avanan_list_addonsA
List all available license add-ons (id, name). Add-on IDs are used when assigning a license to a tenant.
Inputs: no named parameters.
avanan_list_exceptionsA
List whitelist or blacklist exception entries.
Inputs: excType (required).
avanan_list_licensesA
List all available license packages (id, codeName, displayName). Use the codeName when assigning a license to a tenant.
Inputs: no named parameters.
avanan_list_msp_partnersA
List all associated child MSP partners under the current MSP. Returns id and name for each child MSP.
Inputs: no named parameters.
avanan_list_msp_usersC
List all MSP users.
Inputs: MSPId, scrollId.
avanan_list_scopesA
List the farm:tenant scopes this key can query. A customer-tenant key has one; an MSP key has one per managed customer, usable as scopes / scope on the event, search and action tools.
Inputs: no named parameters.
avanan_list_tenantsA
List all customer tenants associated with the current MSP. Each tenant entry includes domain, deployment mode, user counts, status, license package and add-ons.
Inputs: MSPId, scrollId.
avanan_quarantine_emailsADestructiveIdempotent
HIGH IMPACT: quarantine specific secured entities (emails) by entity ID. Reversible with avanan_restore_emails. Returns task IDs. Confirm with the user before invoking.
Inputs: entityIds (required), scope, entityType.
avanan_quarantine_eventsADestructiveIdempotent
HIGH IMPACT: quarantine the emails behind one or more security events. Reversible with avanan_restore_events. Returns task IDs. Confirm with the user before invoking.
Inputs: eventIds (required), scope.
avanan_query_eventsA
Query Avanan security events (phishing, malware, DLP, anomaly, shadow IT, malicious URL). Filter by type, state, severity, SaaS, date range, or description text. Returns each event's available remediation actions.
Inputs: saas, scopes, endDate, eventIds, +7 more.
avanan_restore_emailsA
Restore specific quarantined entities (emails) by entity ID. Returns task IDs.
Inputs: entityIds (required), scope, entityType.
avanan_restore_eventsB
Restore previously quarantined emails behind one or more security events. Returns task IDs.
Inputs: eventIds (required), scope.
avanan_search_emailsC
Search secured entities (emails and SaaS objects) by platform and date range, with optional attribute filters (fromEmail, subject, recipients, isQuarantined, attachmentMd5, ...).
Inputs: saas (required), startDate (required), scopes, endDate, +3 more.
avanan_test_connectionA
Verify the configured Avanan credentials: performs the auth handshake, lists the key's scopes, and probes an MSP endpoint to confirm the key is MSP-scoped. Run this first when MSP tools return 403.
Inputs: no named parameters.
avanan_update_exceptionB
Update an existing whitelist or blacklist entry by its entity ID.
Inputs: excId (required), excType (required), comment, subject, +18 more.
avanan_update_msp_userB
Update an MSP user by ID. All fields are required per the SmartAPI spec.
Inputs: role (required), email (required), user_id (required), lastName (required), +6 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 33 tools
Tools are mostly grouped by clear resource domains (MSP partners, users, tenants, exceptions, events, emails). Potential confusion between query_events/search_emails and quarantine_events/quarantine_emails is mitigated by descriptions, and each tool has a distinct purpose.
All tools share the avanan_ prefix and generally follow verb_noun (list/get/update/delete/create). Minor inconsistency: query_events vs search_emails, and get_monthly_usage/get_daily_usage aren't resource-based, but the pattern is otherwise predictable.
33 tools is well above the comfortable 3-15 range. While they cover several distinct subdomains (MSP admin, tenant management, events, quarantine, usage), the surface is heavy and would benefit from consolidation or separate servers.
Most core entities have CRUD coverage: MSP users, exceptions, tenants (except update), partners (no update), plus query/search/actions. Obvious gaps include no update_tenant or update_msp_partner, and no way to list tenants by filter or fetch usage for a single tenant.
Maintenance
Related MCP Connectors
An MCP server that provides email capabilities, hosted on Alpic platform
An MCP server that provides email capabilities, hosted on Alpic platform
An MCP server that provides email capabilities, hosted on Alpic platform
Hosted MCP server for your Gmail, Outlook and IMAP mail, with mailboxes and scopes set per agent.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceAn advanced email security analysis MCP server for real-time phishing detection, comprehensive header analysis, and threat intelligence integration. It enables users to extract indicators of compromise and validate email authentication protocols like DKIM, SPF, and DMARC.MIT
- AlicenseAqualityBmaintenanceAn MCP server for Abnormal Security, enabling management of threat detection, email security cases, and AI-powered attack protection through Abnormal's API.10Apache 2.0
- AlicenseNot gradedqualityBmaintenanceAn MCP server for Datto SaaS Protection, providing tools to manage cloud backup and recovery for Microsoft 365 and Google Workspace data through Datto's API.2Apache 2.0
- AlicenseAqualityBmaintenanceMCP server for Checkpoint Harmony Email & Collaboration (Avanan). Enables AI assistants to manage email security, anti-phishing, anti-malware, and threat detection via the Avanan API.131Apache 2.0