MCP.Market

Mailprotector MCP server

by wyre-technology·io.github.wyre-technology/mailprotector-mcp·v1.0.1
No reviews yet

MCP server for Mailprotector — customers, domains, users, quarantine, allow/block rules for MSPs.

B75/100grade B
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
B75/100

full report

Adoption
New

0 stars

Reviews

Write one

Nobody has reviewed Mailprotector yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Mailprotector tools

No tool declarations could be read from the package source. They show once the server is installed.

Public scan report

scanner v0.1.10 · 2026-11-02 · same rubric, same numbers if you re-run it

no findings
  • –Code scanpackage could not be scannedn/a
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitystatic API keys via environment variables6/15
  • Maintenancelast push 14 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year9/10
Overall 75/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Mailprotector compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
75/100
higher than 45% of 48,255 servers

Install Mailprotector in Claude Code, Cursor or VS Code

claude mcp add mailprotector-mcp -- docker run -i --rm ghcr.io/wyre-technology/mailprotector-mcp:v1.0.1
Add to Cursor

What the publisher says

From the Mailprotector repository's README, as published. We do not edit it. Read it on GitHub

mailprotector-mcp

MCP server for Mailprotector — email security management for MSPs (CloudFilter, Bracket, SafeSend, XtraMail): customers, domains, users, quarantine, allow/block rules, logs, configuration, and the full long-tail API via a router.

Built on the MCP 2026-07-28 spec via the split v2 SDK (@modelcontextprotocol/server / /node / /client ^2.0.0-beta.5) with dual-era serving: one shared McpServerFactory behind createMcpHandler({ legacy: 'stateless' }) answers both 2025-era initialize-handshake clients (the WYRE gateway today) and modern 2026-07-28 envelope clients — with an identical, deterministic 22-tool surface for every caller. Ships as a GHCR container only (no MCPB bundle).

Tools (22 first-class + routed long tail)

Router: mailprotectorstatus, mailprotectorlistcategories, mailprotectorlistcategorytools, mailprotectorexecutetool.

Promoted reads: mailprotectorcustomerslist/get, mailprotectordomainslist/get, mailprotectoruserslist/get/findbyaddress, mailprotectorusergroupslist, mailprotectormessageslist, mailprotectorallowblockruleslist, mailprotectorlogslist, mailprotectorconfiguration_get.

Promoted writes: mailprotectorcustomerscreate, mailprotectordomainscreate, mailprotectormessagesrelease / releasemany (⚠ HIGH-IMPACT), mailprotectorallowblockrulescreate (⚠ HIGH-IMPACT), and the ⚠ DESTRUCTIVE — IRREVERSIBLE mailprotectorallowblockrules_delete.

Router categories (52 routed operations via mailprotectorexecutetool): resellers (CRUD), customers (update/delete), domains (update/delete/move/aliases), usergroups (CRUD + services), users (create/createmany/update/delete/resetpassword/aliases), managers (CRUD + notification destinations), configuration (update), statements, emailrouting (destinations/sources for domain|usergroup), usersyncs (CRUD + schedule + filters), notifications (user notification destinations), results (findbycode). Every routed delete is ⚠ DESTRUCTIVE and confirmation-gated; discover schemas with mailprotectorlistcategory_tools.

Scoped tools

Mailprotector's hierarchy is Provider → Reseller → Customer → Domain → User Group → User, and many operations exist at several scopes. Scoped tools take scope (reseller | customer | domain | usergroup | user, per-tool subsets) plus scopeid; scopeid defaults to the bound reseller** when scope is "reseller".

Delete confirmations (MRTR elicitation)

Every delete flows through the SDK v2 MRTR seam: the handler returns inputrequired, interactive clients see a confirmation prompt, and declining cancels the delete. Callers that declared no elicitation capability — including stateless 2025-era callers such as the WYRE Conduit gateway — fall back to proceeding** per the integration contract: elicitation here is purely additive, and the gateway enforces destructive-tool access with its own server-side per-tool classification gate.

Credentials

In gateway mode a request missing either header (or with a non-numeric reseller id) is answered 401 (JSON-RPC error -32001) before the MCP handler runs — it never falls through to env credentials.

Running

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Mailprotector: common questions

Is Mailprotector MCP server safe?
Mostly: it is graded B (75/100). Read the Mailprotector safety report
How do I install Mailprotector?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Mailprotector need an API key?
Yes. The registry entry asks for MAILPROTECTOR_API_KEY.
Is Mailprotector maintained?
The last commit was 16 days ago (2026-10-19). The latest release is v1.0.1.

More from wyre-technology →