# Mimecast (oci · ghcr.io/wyre-ai/mimecast-mcp)

MCP server for Mimecast email security: message queue, held messages, domains, and threats.

- Trust score: 44/100 (low)
- Change this week: +35
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-18

## Components

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

## Channel facts

- Registry: `oci`
- Package: `ghcr.io/wyre-ai/mimecast-mcp`
- Version: `v1.3.9`
- 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-18.

- **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 8 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 84/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 1190 tokens (~108/item across 11 items; 10 tools + 1 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 13/100
  - Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% 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.
  - We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 11 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: 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.

## Install

### How do I install the Mimecast MCP server?

Mimecast runs locally as a container image, launched with docker run --rm -i -e MIMECAST_CLIENT_ID -e MIMECAST_CLIENT_SECRET -e MIMECAST_REGION -e MCP_TRANSPORT -e AUTH_MODE -e LOG_LEVEL ghcr.io/wyre-ai/mimecast-mcp:v1.3.9. 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-mimecast-mcp -- docker run --rm -i -e MIMECAST_CLIENT_ID -e MIMECAST_CLIENT_SECRET -e MIMECAST_REGION -e MCP_TRANSPORT -e AUTH_MODE -e LOG_LEVEL ghcr.io/wyre-ai/mimecast-mcp:v1.3.9
```

This image reads MIMECAST_CLIENT_ID, MIMECAST_CLIENT_SECRET, MIMECAST_REGION, 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-mimecast-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "-e",
        "MIMECAST_CLIENT_ID",
        "-e",
        "MIMECAST_CLIENT_SECRET",
        "-e",
        "MIMECAST_REGION",
        "-e",
        "MCP_TRANSPORT",
        "-e",
        "AUTH_MODE",
        "-e",
        "LOG_LEVEL",
        "ghcr.io/wyre-ai/mimecast-mcp:v1.3.9"
      ]
    }
  }
}
```

This image reads MIMECAST_CLIENT_ID, MIMECAST_CLIENT_SECRET, MIMECAST_REGION, 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-mimecast-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "-e",
        "MIMECAST_CLIENT_ID",
        "-e",
        "MIMECAST_CLIENT_SECRET",
        "-e",
        "MIMECAST_REGION",
        "-e",
        "MCP_TRANSPORT",
        "-e",
        "AUTH_MODE",
        "-e",
        "LOG_LEVEL",
        "ghcr.io/wyre-ai/mimecast-mcp:v1.3.9"
      ]
    }
  }
}
```

This image reads MIMECAST_CLIENT_ID, MIMECAST_CLIENT_SECRET, MIMECAST_REGION, 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-mimecast-mcp -- docker run --rm -i -e MIMECAST_CLIENT_ID -e MIMECAST_CLIENT_SECRET -e MIMECAST_REGION -e MCP_TRANSPORT -e AUTH_MODE -e LOG_LEVEL ghcr.io/wyre-ai/mimecast-mcp:v1.3.9
```

This image reads MIMECAST_CLIENT_ID, MIMECAST_CLIENT_SECRET, MIMECAST_REGION, 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-mimecast-mcp": {
      "type": "local",
      "command": [
        "docker",
        "run",
        "--rm",
        "-i",
        "-e",
        "MIMECAST_CLIENT_ID",
        "-e",
        "MIMECAST_CLIENT_SECRET",
        "-e",
        "MIMECAST_REGION",
        "-e",
        "MCP_TRANSPORT",
        "-e",
        "AUTH_MODE",
        "-e",
        "LOG_LEVEL",
        "ghcr.io/wyre-ai/mimecast-mcp:v1.3.9"
      ],
      "enabled": true
    }
  }
}
```

This image reads MIMECAST_CLIENT_ID, MIMECAST_CLIENT_SECRET, MIMECAST_REGION, 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-mimecast-mcp:
    command: "docker"
    args: ["run", "--rm", "-i", "-e", "MIMECAST_CLIENT_ID", "-e", "MIMECAST_CLIENT_SECRET", "-e", "MIMECAST_REGION", "-e", "MCP_TRANSPORT", "-e", "AUTH_MODE", "-e", "LOG_LEVEL", "ghcr.io/wyre-ai/mimecast-mcp:v1.3.9"]
```

This image reads MIMECAST_CLIENT_ID, MIMECAST_CLIENT_SECRET, MIMECAST_REGION, 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-mimecast-mcp": {
      "Transport": "stdio",
      "Command": "docker",
      "Arguments": [
        "run",
        "--rm",
        "-i",
        "-e",
        "MIMECAST_CLIENT_ID",
        "-e",
        "MIMECAST_CLIENT_SECRET",
        "-e",
        "MIMECAST_REGION",
        "-e",
        "MCP_TRANSPORT",
        "-e",
        "AUTH_MODE",
        "-e",
        "LOG_LEVEL",
        "ghcr.io/wyre-ai/mimecast-mcp:v1.3.9"
      ]
    }
  }
}
```

This image reads MIMECAST_CLIENT_ID, MIMECAST_CLIENT_SECRET, MIMECAST_REGION, 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-mimecast-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "-e",
        "MIMECAST_CLIENT_ID",
        "-e",
        "MIMECAST_CLIENT_SECRET",
        "-e",
        "MIMECAST_REGION",
        "-e",
        "MCP_TRANSPORT",
        "-e",
        "AUTH_MODE",
        "-e",
        "LOG_LEVEL",
        "ghcr.io/wyre-ai/mimecast-mcp:v1.3.9"
      ]
    }
  }
}
```

This image reads MIMECAST_CLIENT_ID, MIMECAST_CLIENT_SECRET, MIMECAST_REGION, 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-17 (score 44, +2)

- [functional improvement] Stability: unverified → 0.10

### 2026-10-14 (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 Destructive annotations: pass
- [functional] First check of Capabilities: pass
- [functional] First check of Schema quality: pass
- [functional] First check of Schema quality: good
- [functional] First check of Tool coverage: 100

### 2026-10-13 (score 9, 0)

- [functional regression] Security disclosure: unverified → fail

### 2026-10-12 (score 9, 0)

- [functional regression] Security disclosure: fail → unverified
- [functional] Package version: v1.3.7 → v1.3.9

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

First indexed and scored.

## MCP tools (10)

### `mimecast_navigate` (~110 tokens)

Discover available Mimecast 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.

Input parameters:

- `domain` (string, required): The domain to explore: - messages: Message tracking and management - find, hold, release email messages - threats: Threat detection and incident management - TTP logs, threat indicators, and security…

### `mimecast_status` (~22 tokens)

Show credentials status and available domains. All tools are always available.

### `mimecast_find_message` (~240 tokens)

Search for email messages using Mimecast message tracking. Filter by sender, recipient, subject, date range, or delivery status. Requires Gateway | Tracking | Read. Dates use ISO 8601 UTC (2026-03-01T00:00:00+0000); a trailing Z is accepted.

Input parameters:

- `from_date` (string): Start date-time in ISO 8601 UTC (2026-03-01T00:00:00+0000). A trailing Z is accepted and converted.
- `page_size` (number): Number of results to return (default: 50, max: 100)
- `page_token` (string): Pagination token for next page
- `recipient_address` (string): Filter by recipient email address
- `sender_address` (string): Filter by sender email address
- `status` (string): Filter by message delivery status
- `to_date` (string): End date-time in ISO 8601 UTC (2026-03-01T00:00:00+0000). A trailing Z is accepted and converted.
- `value` (string): Keyword search across message fields

### `mimecast_get_message_info` (~45 tokens)

Get detailed metadata for a specific message by its Mimecast ID, including headers, routing information, and rejection details.

Input parameters:

- `id` (string, required): Mimecast message ID

### `mimecast_hold_message` (~61 tokens)

Place a message on hold in the Mimecast gateway to prevent delivery while under review. Requires Account | Monitoring | Held | Edit.

Input parameters:

- `id` (string, required): Mimecast message ID to hold
- `reason` (string): Reason for holding the message

### `mimecast_release_message` (~48 tokens)

Release a held message from the Mimecast gateway to allow delivery to the recipient. Requires Account | Monitoring | Held | Edit.

Input parameters:

- `id` (string, required): Mimecast message ID to release

### `mimecast_get_threat_incidents` (~104 tokens)

Get threat remediation incidents from Mimecast. Returns incidents where malicious content was detected and remediation actions were taken. Requires the API application role permission Services | Threat Remediation | Read; a permissions error means that permission is missing.

Input parameters:

- `page_size` (number): Number of results (default: 50)
- `page_token` (string): Pagination token for next page
- `status` (string): Filter by incident status (e.g. open, closed)

### `mimecast_get_ttp_logs` (~229 tokens)

Get Targeted Threat Protection logs. Retrieve URL click logs, attachment sandbox results, or impersonation protection hits. Requires Monitoring | URL Protection | Read, Monitoring | Attachment Protection | Read, or Monitoring | Impersonation Protection | Read, matching type. Dates use ISO 8601 (2026-03-01T00:00:00+0000 or a trailing Z).

Input parameters:

- `from_date` (string): Start date-time in ISO 8601 UTC (2026-03-01T00:00:00+0000). A trailing Z is accepted and converted. Omit to use Mimecast's default (start of the current day).
- `page_size` (number): Number of results (default: 50)
- `page_token` (string): Pagination token for next page
- `to_date` (string): End date-time in ISO 8601 UTC (2026-03-01T00:00:00+0000). A trailing Z is accepted and converted.
- `type` (string, required): Type of TTP log to retrieve

### `mimecast_get_audit_events` (~263 tokens)

Retrieve Mimecast audit log entries. Useful for compliance reviews and investigating administrative changes. The API requires a start and end; when omitted, the last 7 days are used. History is limited to 60 days. Requires Account | Logs | Read. Category filters use codes such as account_logs or policy_logs (not display names); omit categories to return every category.

Input parameters:

- `categories` (array): Audit category codes from /api/audit/get-categories, for example ["account_logs", "policy_logs"]. Omit to return every category. Display names such as "administration" are mapped to account_logs.
- `from_date` (string): Start date-time in ISO 8601 UTC (2026-03-01T00:00:00+0000). A trailing Z is accepted. Must be within the last 60 days. Defaults to 7 days before to_date.
- `page_size` (number): Number of results (default: 50)
- `page_token` (string): Pagination token for next page
- `to_date` (string): End date-time in ISO 8601 UTC (2026-03-01T00:00:00+0000). A trailing Z is accepted. Defaults to now.

### `mimecast_get_queue_status` (~50 tokens)

Get the current email delivery queue status from Mimecast, including counts and ages of queued inbound and outbound messages. Requires Account | Dashboard | Read. A permissions error means that role permission is missing.

## Diagnostics

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

## Score history

- 2026-10-18: 44
- 2026-10-17: 44
- 2026-10-16: 42
- 2026-10-15: 42
- 2026-10-14: 42
- 2026-10-13: 9
- 2026-10-12: 9
- 2026-10-09: 9

## Common questions

### What is the Mimecast MCP server?

Mimecast is an MCP server listed in the public MCP registry as io.github.WYRE-AI/mimecast-mcp. MCP server for Mimecast email security: message queue, held messages, domains, and threats. This page covers its container image (ghcr.io/wyre-ai/mimecast-mcp).

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

Mimecast scores 44 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 Mimecast MCP server expose?

Mimecast exposes 10 tools: mimecast_navigate, mimecast_status, mimecast_find_message, mimecast_get_message_info, mimecast_hold_message, and 5 more. Their descriptions and schemas cost roughly 1,172 tokens of context every time the server is loaded.

### Is the Mimecast MCP server still maintained?

Mimecast is still listed as active in the MCP registry. We last reached this channel on 18 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 Mimecast MCP server under?

Mimecast 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/mimecast-mcp
- Repository: https://github.com/WYRE-AI/mimecast-mcp
- Changelog RSS feed: https://verifymcp.io/servers/wyre-ai-mimecast-mcp/ghcr-io-wyre-ai-mimecast-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/wyre-ai-mimecast-mcp/ghcr-io-wyre-ai-mimecast-mcp.json
- HTML version of this page: https://verifymcp.io/servers/wyre-ai-mimecast-mcp/ghcr-io-wyre-ai-mimecast-mcp