Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Mimecast

OCI · GHCR.IO/WYRE-AI/MIMECAST-MCP:V1.3.6 · SCANNED SEP 20

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

+3 this week 54 Trust /100
Trust breakdown (7 categories)

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
  • Malware scan not yet available for this package.Unverified
  • Known CVEs could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.Unverified
  • Install-script risk not yet assessed.Unverified
  • Dependency health could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.Unverified
Provenance & Transparency45
Schema Quality & AI Usability85
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 796 tokens (~72/item across 11 items; 10 tools + 1 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management83
  • Stability observed for 25 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 11 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: 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 ghcr.io/wyre-ai/mimecast-mcp:v1.3.6. 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/mimecast-mcp:v1.3.6

# add to Claude Code
claude mcp add wyre-ai-mimecast-mcp -- docker run --rm -i ghcr.io/wyre-ai/mimecast-mcp:v1.3.6
// .cursor/mcp.json
{
  "mcpServers": {
    "wyre-ai-mimecast-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/wyre-ai/mimecast-mcp:v1.3.6"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "wyre-ai-mimecast-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/wyre-ai/mimecast-mcp:v1.3.6"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add wyre-ai-mimecast-mcp -- docker run --rm -i ghcr.io/wyre-ai/mimecast-mcp:v1.3.6
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "wyre-ai-mimecast-mcp": {
      "type": "local",
      "command": [
        "docker",
        "run",
        "--rm",
        "-i",
        "ghcr.io/wyre-ai/mimecast-mcp:v1.3.6"
      ],
      "enabled": true
    }
  }
}
# ~/.hermes/config.yaml
mcp_servers:
  wyre-ai-mimecast-mcp:
    command: "docker"
    args: ["run", "--rm", "-i", "ghcr.io/wyre-ai/mimecast-mcp:v1.3.6"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "wyre-ai-mimecast-mcp": {
      "Transport": "stdio",
      "Command": "docker",
      "Arguments": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/wyre-ai/mimecast-mcp:v1.3.6"
      ]
    }
  }
}
// mcp.json
{
  "mcpServers": {
    "wyre-ai-mimecast-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/wyre-ai/mimecast-mcp:v1.3.6"
      ]
    }
  }
}
Changelog

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.

  • 19 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.

  • 15 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

  • 13 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

  • 11 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

  • 9 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

  • 7 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

  • 4 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

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 20 Sept 2026 · Analysed oci/ghcr.io/wyre-ai/mimecast-mcp:v1.3.6

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 →

MCP tools · 10 exposed · ~778 tokens

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 →

Tool Tokens
mimecast_find_message ~173

Search for email messages using Mimecast message tracking. Filter by sender, recipient, subject, date range, or delivery status.

NameTypeReqDescription
from_datestringStart date-time in ISO 8601 format (e.g. 2026-03-01T00:00:00Z)
page_sizenumberNumber of results to return (default: 50, max: 100)
page_tokenstringPagination token for next page
recipient_addressstringFilter by recipient email address
sender_addressstringFilter by sender email address
statusstringFilter by message delivery status
to_datestringEnd date-time in ISO 8601 format
valuestringKeyword search across message fields

No output schema declared.

No examples provided.

mimecast_get_audit_events ~112

Retrieve Mimecast audit log entries. Useful for compliance reviews and investigating administrative changes.

NameTypeReqDescription
categoriesarrayFilter by event categories (e.g. ["administration", "policy"])
from_datestringStart date-time in ISO 8601 format
page_sizenumberNumber of results (default: 50)
page_tokenstringPagination token for next page
to_datestringEnd date-time in ISO 8601 format

No output schema declared.

No examples provided.

mimecast_get_message_info ~45

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

NameTypeReqDescription
idstringyesMimecast message ID

No output schema declared.

No examples provided.

mimecast_get_queue_status ~33

Get the current email delivery queue status from Mimecast, including counts and ages of queued inbound and outbound messages.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

mimecast_get_threat_incidents ~81

Get threat remediation incidents from Mimecast. Returns incidents where malicious content was detected and remediation actions were taken.

NameTypeReqDescription
page_sizenumberNumber of results (default: 50)
page_tokenstringPagination token for next page
statusstringFilter by incident status (e.g. open, closed)

No output schema declared.

No examples provided.

mimecast_get_ttp_logs ~111

Get Targeted Threat Protection logs. Retrieve URL click logs, attachment sandbox results, or impersonation protection hits.

NameTypeReqDescription
from_datestringStart date-time in ISO 8601 format
page_sizenumberNumber of results (default: 50)
page_tokenstringPagination token for next page
to_datestringEnd date-time in ISO 8601 format
typestringyesType of TTP log to retrieve

No output schema declared.

No examples provided.

mimecast_hold_message ~52

Place a message on hold in the Mimecast gateway to prevent delivery while under review.

NameTypeReqDescription
idstringyesMimecast message ID to hold
reasonstringReason for holding the message

No output schema declared.

No examples provided.

mimecast_navigate ~110

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.

NameTypeReqDescription
domainstringyesThe 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…

No output schema declared.

No examples provided.

mimecast_release_message ~39

Release a held message from the Mimecast gateway to allow delivery to the recipient.

NameTypeReqDescription
idstringyesMimecast message ID to release

No output schema declared.

No examples provided.

mimecast_status ~22

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

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:v1.3.6).

Is the Mimecast MCP server safe to use?

Mimecast scores 54 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 778 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 20 September 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.