MisarMail MCP Server
NPM · @MISARMAIL/MCP · 2 COMPONENTS
Send transactional email, run campaigns, manage contacts and automations, audit deliverability.
Available components
Last scanned (19 hours ago)
Scores higher than 88% of npm servers
Category Marketing and SEO
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 Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 8 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability88
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 6021 tokens (~98/item across 61 items; 57 tools + 4 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
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
- All 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 58 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
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.
- 16 Oct 26 0
- Stability: 0.97 → pass security
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Oct 26 +1
- Security disclosure: unverified → fail ▼ functional
- 12 Oct 26 −2
- Security disclosure: fail → unverified ▼ functional
- 8 Oct 26 +2
No change was recorded against any check on this day. Stability & Change Management went from 83 to 97. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Oct 26 −2
- Stability: pass → 0.83 functional
- 3 Oct 26 0
- Stability: 0.97 → pass security
- 2 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
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 16 Oct 2026 · Analysed npm/@misarmail/mcp@5.1.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
send_email ~251
Send a transactional email from a verified MisarMail account. `from.email` must match an email account you have already verified — use list_domains to check which sender domains are available. Returns the message ID and queue status.
| Name | Type | Req | Description |
|---|---|---|---|
| alias_id | string | – | Route via a specific alias SMTP pool |
| bcc | array | – | BCC recipients (max 50, hidden from other recipients) |
| cc | array | – | CC recipients (max 50) |
| from | object | yes | Sender address (must match a verified MisarMail account) |
| html | string | – | HTML body (max 500KB, recommended) |
| idempotency_key | string | – | Unique key to prevent duplicate sends (max 128 chars) |
| metadata | object | – | Custom metadata key-value pairs (max 20 pairs) |
| reply_to | object | – | Reply-to address |
| subject | string | yes | Email subject (max 998 chars) |
| tags | array | – | Tags for tracking (max 10, each max 64 chars) |
| text | string | – | Plain text body (max 500KB, fallback for HTML) |
| to | array | yes | Recipient list (1–100 addresses) |
No output schema declared.
No examples provided.
toggle_automation ~129
Activate or pause one automation workflow. This is consequential in one direction: ACTIVATING starts enrolling contacts, which means real emails begin going out on the workflow's schedule without further confirmation. Pausing stops new enrolments. Read the workflow with get_automation first so you know what activating will actually send. Contacts already part-way through a paused workflow are held rather than dropped, so pausing is not a cancellation. Safe to repeat. Requires an API key.
| Name | Type | Req | Description |
|---|---|---|---|
| active | boolean | yes | true to activate, false to pause |
| automation_id | string | yes | Automation ID (UUID) |
No output schema declared.
No examples provided.
toggle_integration ~141
Turn one third-party integration on or off. This changes live behaviour: DISABLING stops all syncing through that integration, so data quietly stops flowing until it is re-enabled. It does not disconnect the integration or revoke its credentials — the connection and its scopes survive, which is why re-enabling picks up where it left off. Safe to repeat: setting an integration to the state it is already in changes nothing. Requires an API key. Call list_integrations first so you know the current state rather than toggling blind.
| Name | Type | Req | Description |
|---|---|---|---|
| enabled | boolean | yes | true to enable, false to disable |
| integration_id | string | yes | Integration ID |
No output schema declared.
No examples provided.
update_contact ~128
Update an existing contact by email address, including changing subscription status. Setting status to unsubscribed immediately excludes them from every future campaign.
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | – | Company name |
| custom_fields | object | – | Custom key-value attributes to merge |
| string | yes | Email address identifying the contact | |
| first_name | string | – | First name |
| job_title | string | – | Job title |
| last_name | string | – | Last name |
| phone | string | – | Phone number |
| status | string | – | New subscription status |
| tags | array | – | Replace segmentation tags |
No output schema declared.
No examples provided.
upgrade ~97
Show the current MisarMail plan, how much of each quota is left, and what upgrading unlocks. Call it any time — not only after hitting a limit. Set open=true to open the checkout page in the default browser.
| Name | Type | Req | Description |
|---|---|---|---|
| open | boolean | – | Open the upgrade/checkout page in the default browser. |
| plan | string | – | Plan slug to open (e.g. 'pro', 'max'). Defaults to the recommended plan. |
No output schema declared.
No examples provided.
validate_email ~48
Validate an email address before sending: syntax, MX records, disposable-domain and role-account detection. Use this to protect sender reputation on imported lists.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | Email address to validate |
No output schema declared.
No examples provided.
verify_domain ~51
Re-check a domain's DNS records and mark it verified if they resolve. Safe to retry — DNS propagation can take up to 48 hours.
| Name | Type | Req | Description |
|---|---|---|---|
| domain_id | string | yes | Domain ID returned by add_domain |
No output schema declared.
No examples provided.
How do I install the MisarMail MCP Server server?
MisarMail MCP Server runs locally as an npm package, launched with npx -y @misarmail/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @misarmail/mcp
claude mcp add misar-ai-misarmail-mcp -- npx -y @misarmail/mcp
What is the MisarMail MCP Server server?
MisarMail MCP Server is listed in the public MCP registry as io.github.Misar-AI/misarmail-mcp. Send transactional email, run campaigns, manage contacts and automations, audit deliverability. This page covers its npm package (@misarmail/mcp).
Is the MisarMail MCP Server server safe to use?
MisarMail MCP Server scores 86 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 16 October 2026. It declares no install or post-install scripts. 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 MisarMail MCP Server server expose?
MisarMail MCP Server exposes 57 tools: send_email, list_emails, get_email, reply_to_email, archive_email, and 52 more. Their descriptions and schemas cost roughly 5,919 tokens of context every time the server is loaded.
Is the MisarMail MCP Server server still maintained?
MisarMail MCP Server is still listed as active in the MCP registry. We last reached this channel on 16 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 MisarMail MCP Server server under?
MisarMail MCP Server declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.