MisarMail MCP Server
REMOTE · API.MISAR.IO · 2 COMPONENTS
Send transactional email, run campaigns, manage contacts and automations, audit deliverability.
Available components
Last scanned (23 hours ago)
Scores higher than 99% of remote servers
Reachable. Last reached 16 Oct 2026.
Category Marketing and SEO
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security89
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token. See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
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 4578 tokens (~77/item across 59 items; 55 tools + 4 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
- Stability check failed: schema churn in the 30 days we've observed: 0 tool removals, 3 breaking changes, 0 auth/transport breaks, 1 additions. See how to fix → Fail
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 56 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
- 10 Oct 26 −1
- Stability: pass → fail ▼ security
- Schema quality: 100 → 77 ▲ functional
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Sept 26 0
- Stability: 0.97 → pass security
- 26 Sept 26 0
- Stability: pass → 0.97 functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 18 Sept 26 0
- Stability: 0.97 → pass security
- 17 Sept 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.
- 16 Sept 26 +56
- Authorization: unverified → fail ▼ security
- Injection markers: unverified → pass ▲ security
- HSTS header: fail → pass ▲ security
- Schema quality: unverified → fail ▼ functional
- Schema quality: unverified → excellent ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Schema quality: unverified → pass ▲ functional
- Stability: fail → 0.93 functional
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
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 · Probed https://api.misar.io/mail/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=misar.io | CN=WE1,O=Google Trust Services,C=US | 28 Sept 2026 | 27 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 88a9d3888ba6d1ff0e0a186c4817562d |
| SANs: misar.io, *.misar.io | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.misar.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| misar.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="MisarMail"
Bearer realm="MisarMail"| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | no_resource_metadata |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.misar.io/mail/mcp | Verified | 200 | |
| http (plaintext) | http://api.misar.io/mail/mcp | HTTPS enforced | 301 | https://api.misar.io/mail/mcp |
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 →
toggle_integration ~50
Enable or disable an integration. Disabling stops all syncing but preserves the stored credentials.
| 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 ~111
Update an existing contact by email address, including changing subscription status. Setting status to unsubscribed immediately excludes them from every future campaign. Does not support tags, phone, company, or job title — the API has no fields for them.
| Name | Type | Req | Description |
|---|---|---|---|
| custom_fields | object | – | Custom key-value attributes to merge |
| string | yes | Email address identifying the contact | |
| first_name | string | – | First name |
| last_name | string | – | Last name |
| status | string | – | New subscription status |
No output schema declared.
No examples provided.
upgrade ~142
Show the current MisarMail plan, how much of each quota is left, and what upgrading unlocks, with the link to upgrade. Call it any time — not only after hitting a limit. Reads only: it never changes the plan or takes payment; the user upgrades by following the link. On a local install, open=true also opens that link in the user's browser.
| Name | Type | Req | Description |
|---|---|---|---|
| open | boolean | – | Local installs only: also open the upgrade link in the user's browser. Ignored by the hosted server, which returns the link instead. |
| 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 is a hosted endpoint at https://api.misar.io/mail/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · api.misar.io
claude mcp add --transport http misar-ai-misarmail-mcp 'https://api.misar.io/mail/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 hosted endpoint (https://api.misar.io/mail/mcp).
Is the MisarMail MCP Server server safe to use?
MisarMail MCP Server scores 91 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 MisarMail MCP Server server expose?
MisarMail MCP Server exposes 55 tools: send_email, list_emails, get_email, reply_to_email, archive_email, and 50 more. Their descriptions and schemas cost roughly 4,476 tokens of context every time the server is loaded.
Does the MisarMail MCP Server server require authentication?
Yes. MisarMail MCP Server asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
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.