MisarMail MCP Server
REMOTE · API.MISAR.IO · 2 COMPONENTS
Send transactional email, run campaigns, manage contacts and automations, audit deliverability.
Available components
Last scanned (22 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 →
add_domain ~50
Add a sending domain and return the DNS records to publish. The domain cannot send until those records are live and verify_domain succeeds.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain to add, e.g. example.com |
No output schema declared.
No examples provided.
archive_email ~36
Move an email to the archive folder. Reversible — the message is not deleted.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Email ID to archive |
No output schema declared.
No examples provided.
categorize_inbox_emails ~61
Run AI categorisation over a batch of inbox emails to label intent and priority. Consumes AI credits — pass only the emails you actually need triaged.
| Name | Type | Req | Description |
|---|---|---|---|
| email_ids | array | yes | Email IDs to categorise (max 50 per call) |
No output schema declared.
No examples provided.
check_dmarc ~62
Check live SPF, DKIM, and DMARC DNS records for a domain and report alignment problems with the exact record to publish. Works for any domain, not only your own.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain to check, e.g. example.com |
No output schema declared.
No examples provided.
clear_sandbox ~27
Delete every captured sandbox email. Affects only intercepted test messages, never real sent mail.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
configure_inbound_domain ~86
Configure inbound email routing for a subdomain so replies land in the MisarMail unified inbox. Returns the MX record to publish.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Root domain, e.g. example.com |
| subdomain | string | yes | Inbound subdomain label, e.g. reply |
| webhook_url | string | yes | HTTPS URL to POST inbound messages to (required) |
No output schema declared.
No examples provided.
create_ab_test ~322
Create one A/B test variant on a campaign. The real API stores a single variant per call, so build a test by calling this once per variant (e.g. twice for a plain A/B split) using the same campaign_id and distinct `variant` labels. Each variant gets send_percent of the audience; auto_select_winner (with winner_wait_hours) can pick and send the winner automatically, or use select_ab_test_winner to do it manually.
| Name | Type | Req | Description |
|---|---|---|---|
| auto_select_winner | boolean | – | Automatically select and send the winner after winner_wait_hours (default false) |
| body_html | string | – | Body HTML for content tests |
| campaign_id | string | yes | Campaign to test (UUID) |
| from_name | string | – | Sender name for from_name tests |
| preheader | string | – | Preheader text for preheader tests |
| send_percent | number | – | Percent of the audience that receives this variant (1-99, default 50) |
| send_time_a | string | – | ISO timestamp for this variant's send_time slot A |
| send_time_b | string | – | ISO timestamp for this variant's send_time slot B |
| subject | string | – | Subject line for subject tests |
| test_type | string | – | What this variant differs on (default: content) |
| variant | string | yes | Variant label, e.g. 'A' or 'B' (max 5 chars) |
| winner_wait_hours | number | – | Hours to wait before auto-selecting a winner (1-168, default 4) |
No output schema declared.
No examples provided.
create_automation ~116
Create an automation workflow from a trigger, saved as a paused draft. The API's create endpoint only accepts a name and trigger — it has no fields for workflow steps or starting active; configure the step sequence in the MisarMail dashboard's visual builder, and use toggle_automation to activate once reviewed.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Automation name |
| trigger | string | yes | Event that starts the workflow |
| trigger_config | object | – | Trigger parameters, e.g. { "tag": "trial" } for tag_added |
No output schema declared.
No examples provided.
create_campaign ~158
Create a new email marketing campaign as a draft. Creating never sends or schedules anything — once the content and audience are confirmed, call send_campaign to send it now or schedule it for later.
| Name | Type | Req | Description |
|---|---|---|---|
| from_email | string | yes | Verified sender address |
| from_name | string | yes | Sender display name (required) |
| html | string | – | HTML body content |
| name | string | yes | Internal campaign name (not shown to recipients) |
| reply_to | string | – | Reply-to address |
| segment_id | string | – | Audience segment to send to |
| subject | string | yes | Subject line recipients will see |
| template_id | string | – | Use a saved template instead of inline HTML |
| text | string | – | Plain text body content |
No output schema declared.
No examples provided.
create_contact ~125
Add a single contact. Adding a contact records consent to email them — only add addresses that opted in, or the send will damage sender reputation and may breach CAN-SPAM/GDPR.
| Name | Type | Req | Description |
|---|---|---|---|
| custom_fields | object | – | Custom key-value attributes |
| string | yes | Contact email address | |
| first_name | string | – | First name (max 100 chars) |
| last_name | string | – | Last name (max 100 chars) |
| source | string | – | Where this contact came from (max 100 chars) |
| tags | array | – | Segmentation tags |
No output schema declared.
No examples provided.
create_landing_page ~151
Create a hosted landing page with a single hero block (headline, subheadline, CTA). Returns the public URL. The real API stores pages as a page-builder block array with no dedicated headline/CTA fields, so this tool translates your inputs into one 'hero' block — for multi-block pages or a real CTA link, use the landing page editor in the MisarMail dashboard.
| Name | Type | Req | Description |
|---|---|---|---|
| cta_text | string | – | Call-to-action button text |
| headline | string | yes | Headline shown to visitors |
| name | string | yes | Page title |
| slug | string | – | URL slug (auto-generated from name when omitted) |
| subheadline | string | – | Supporting line under the headline |
No output schema declared.
No examples provided.
create_template ~111
Create a reusable email template. Use {{variable}} placeholders for personalisation — they are substituted at send time and previewable via render_template.
| Name | Type | Req | Description |
|---|---|---|---|
| html | string | yes | HTML body (supports {{variables}}) |
| name | string | yes | Template name |
| subject | string | yes | Default subject line (supports {{variables}}) |
| text | string | – | Plain text fallback body |
| type | string | – | Template type (default: marketing) |
| variables | array | – | Declared variable names used in the template |
No output schema declared.
No examples provided.
generate_report ~98
Generate a structured analytics report over a date range. Report types: campaign_performance, engagement_funnel, cohort_analysis, and send_time_heatmap (best hour/day to send).
| Name | Type | Req | Description |
|---|---|---|---|
| date_from | string | – | Start date, ISO 8601 (default: 30 days ago) |
| date_to | string | – | End date, ISO 8601 (default: today) |
| report_type | string | yes | Type of report to generate |
No output schema declared.
No examples provided.
generate_subject_lines ~90
Generate AI subject-line variants for a campaign topic, optionally tuned to a tone and audience. Good input for create_ab_test.
| Name | Type | Req | Description |
|---|---|---|---|
| audience | string | – | Who the email is for |
| count | number | – | How many variants to generate (default 5, max 10) |
| tone | string | – | Desired tone (default professional) |
| topic | string | yes | What the email is about |
No output schema declared.
No examples provided.
get_analytics ~136
Get delivery and engagement analytics — sent, delivered, opened, clicked, bounced, and complained — for the account or one campaign, grouped by day/week/month.
| Name | Type | Req | Description |
|---|---|---|---|
| campaign_id | string | – | Limit to one campaign (omit for account-wide) |
| end_date | string | – | End date, ISO 8601 |
| group_by | string | – | Time bucket for the series (default day) |
| period | string | – | Shorthand window used when start_date is omitted (default 30d) |
| start_date | string | – | Start date, ISO 8601 (e.g. 2026-01-01) |
No output schema declared.
No examples provided.
get_analytics_timeline ~149
Get a day/week/month breakdown of sent, delivered, opened, clicked, bounced, complained, replied, and unsubscribed — across every send medium (campaigns, inbox compose, API, MCP, SDKs, GraphQL, automations). The timeline counterpart to get_analytics's period totals.
| Name | Type | Req | Description |
|---|---|---|---|
| end_date | string | – | End date, ISO 8601 |
| group_by | string | – | Time bucket for each row (default day) |
| period | string | – | Shorthand window used when start_date is omitted (default 30d) |
| start_date | string | – | Start date, ISO 8601 (e.g. 2026-01-01) |
No output schema declared.
No examples provided.
get_automation ~42
Get one automation workflow in full: trigger, every step with its delay, and per-step completion stats.
| Name | Type | Req | Description |
|---|---|---|---|
| automation_id | string | yes | Automation ID (UUID) |
No output schema declared.
No examples provided.
get_campaign ~48
Get full details for one campaign: content, audience segment, schedule, and delivery statistics (sent, opened, clicked, bounced, complained).
| Name | Type | Req | Description |
|---|---|---|---|
| campaign_id | string | yes | Campaign ID (UUID) |
No output schema declared.
No examples provided.
get_contact_score ~67
Get engagement score, engagement tier, and churn risk for one contact — or the lowest-engagement contacts across the list when contact_id is omitted. Use before a re-engagement campaign.
| Name | Type | Req | Description |
|---|---|---|---|
| contact_id | string | – | Contact ID to score (omit to return the lowest-engagement contacts) |
No output schema declared.
No examples provided.
get_deliverability_score ~48
Get the account deliverability score (0–100) and letter grade (A–F) with the factors dragging it down. Start here when asked why emails are landing in spam.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_email ~48
Read the full content of a single email by ID, including headers, body, and attachments metadata. Side effect: marks the email as read.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Email ID (UUID) |
No output schema declared.
No examples provided.
get_form ~35
Get one signup form including its fields, embed code, and redirect behaviour.
| Name | Type | Req | Description |
|---|---|---|---|
| form_id | string | yes | Form ID (UUID) |
No output schema declared.
No examples provided.
get_form_submissions ~64
List submissions for a signup form, including the submitted field values and timestamps.
| Name | Type | Req | Description |
|---|---|---|---|
| form_id | string | yes | Form ID (UUID) |
| limit | number | – | Results per page (default 20) |
| page | number | – | Page number (default 1) |
No output schema declared.
No examples provided.
get_inbox_conversation_messages ~40
Get every message in one inbox conversation, oldest first, with sender and timestamps.
| Name | Type | Req | Description |
|---|---|---|---|
| conversation_id | string | yes | Conversation ID (UUID) |
No output schema declared.
No examples provided.
get_integration ~32
Get one integration's configuration, scopes, and last sync result.
| Name | Type | Req | Description |
|---|---|---|---|
| integration_id | string | yes | Integration ID |
No output schema declared.
No examples provided.
get_marketplace_item ~36
Get one marketplace listing with its full preview, author, and install count.
| Name | Type | Req | Description |
|---|---|---|---|
| item_id | string | yes | Marketplace item ID |
No output schema declared.
No examples provided.
get_monetization_stats ~46
Get newsletter monetization stats: paid subscribers, MRR, churn, and sponsorship revenue for the period.
| Name | Type | Req | Description |
|---|---|---|---|
| period | string | – | Time window (default 30d) |
No output schema declared.
No examples provided.
get_revenue_attribution ~58
Attribute ecommerce revenue to email — revenue per campaign, per contact, and average order value from tracked conversions.
| Name | Type | Req | Description |
|---|---|---|---|
| campaign_id | string | – | Limit to one campaign |
| period | string | – | Time window (default 30d) |
No output schema declared.
No examples provided.
get_warmup_status ~45
Get IP/domain warm-up progress and today's remaining send capacity. Exceeding warm-up capacity on a new domain is the fastest way to get throttled or blocklisted.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
import_contacts ~94
Bulk-import up to 5,000 contacts in one call. By default, addresses that already exist are skipped rather than duplicated — pass update_existing: true to update them instead. Returns per-row results so you can see which rows were rejected and why.
| Name | Type | Req | Description |
|---|---|---|---|
| contacts | array | yes | Contacts to import (max 5000) |
| update_existing | boolean | – | Update contacts that already exist instead of skipping them (default false) |
No output schema declared.
No examples provided.
list_ab_tests ~94
List A/B tests with per-variant results and whether a winner has been selected yet.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Results per page (default 20) |
| page | number | – | Page number (default 1) |
| type | string | – | Filter by test source: 'campaign' for campaign A/B tests (subject/content/send_time/from_name variants on a campaign), 'subject' for standalone subject-line tests |
No output schema declared.
No examples provided.
list_api_keys ~32
List API keys on the account with their scopes and last-used time. Key secrets are never returned — only metadata.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_automations ~70
List automation workflows (welcome series, re-engagement, drip sequences) with their trigger type and active state.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Results per page (default 20) |
| page | number | – | Page number (default 1) |
| status | string | – | Filter by automation status |
No output schema declared.
No examples provided.
list_campaigns ~80
List email marketing campaigns with their status, audience size, and headline metrics. Filter by status to find drafts ready to send or campaigns still sending.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Results per page (default 20, max 100) |
| page | number | – | Page number (default 1) |
| status | string | – | Filter by campaign status |
No output schema declared.
No examples provided.
list_contacts ~92
List contacts with their subscription status and engagement metrics. Filter by status to find unsubscribed or bounced addresses that should be excluded from sends.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Results per page (default 20, max 100) |
| page | number | – | Page number (default 1) |
| search | string | – | Search across email, name, and company |
| status | string | – | Filter by subscription status |
No output schema declared.
No examples provided.
list_domains ~67
List sending domains with verification status and their DKIM/SPF/DMARC records. Check here first when a send fails with an unverified-sender error.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Results per page (default 20) |
| page | number | – | Page number (default 1) |
No output schema declared.
No examples provided.
list_emails ~88
List emails from a mailbox folder with optional full-text search across subject and body. Use this for reading the unified inbox; use list_campaigns for marketing sends.
| Name | Type | Req | Description |
|---|---|---|---|
| folder | string | – | Folder to list (default: inbox) |
| limit | number | – | Number of emails to return (default 20, max 50) |
| search | string | – | Search query across subject and body |
No output schema declared.
No examples provided.
list_forms ~57
List signup forms with their embed status and conversion counts.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Results per page (default 20) |
| page | number | – | Page number (default 1) |
| status | string | – | Filter by form status |
No output schema declared.
No examples provided.
list_inbox_conversations ~126
List unified-inbox conversations (threads) with their status and detected intent. Use this for triage; use list_emails for individual messages in a folder.
| Name | Type | Req | Description |
|---|---|---|---|
| channel | string | – | Filter by channel, e.g. email |
| intent | string | – | Filter by detected intent, e.g. interested, unsubscribe, question |
| limit | number | – | Results to return (default 20) |
| offset | number | – | Offset for pagination |
| q | string | – | Free-text search across the thread |
| status | string | – | Filter by conversation status |
No output schema declared.
No examples provided.
list_integrations ~46
List connected third-party integrations and their sync status.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Results per page (default 20) |
| page | number | – | Page number (default 1) |
No output schema declared.
No examples provided.
list_marketplace_items ~79
Browse the MisarMail template marketplace for ready-made email and automation templates.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Filter by category, e.g. newsletter, ecommerce |
| limit | number | – | Results per page (default 20) |
| page | number | – | Page number (default 1) |
| search | string | – | Search marketplace listings |
No output schema declared.
No examples provided.
list_sandbox_sends ~39
List emails captured by sandbox mode. Sandbox intercepts sends instead of delivering them — use it to verify templates and automations without emailing anyone.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_templates ~67
List saved email templates with their variable placeholders, so you can pick one for a campaign or transactional send.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Results per page (default 20) |
| page | number | – | Page number (default 1) |
| type | string | – | Filter by template type |
No output schema declared.
No examples provided.
render_template ~67
Render a template with sample variables and return the resulting HTML and subject. Use this to preview personalisation before sending anything.
| Name | Type | Req | Description |
|---|---|---|---|
| template_id | string | yes | Template ID to render |
| variables | object | – | Variable values to substitute, e.g. { "first_name": "Ada" } |
No output schema declared.
No examples provided.
reply_to_email ~72
Reply to an existing email thread. The sender address and threading headers are derived from the original message, so only the body is required.
| Name | Type | Req | Description |
|---|---|---|---|
| email_id | string | yes | ID of the email to reply to |
| html | string | – | HTML reply body |
| text | string | – | Plain text reply body |
No output schema declared.
No examples provided.
run_deliverability_audit ~48
Run a full deliverability audit across authentication (SPF/DKIM/DMARC), domain reputation, list hygiene, content signals, and blocklist status. Returns prioritized findings.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
select_ab_test_winner ~86
Select the winning variant and send it to the remaining audience. This triggers a real send to everyone who was held back — it cannot be undone.
| Name | Type | Req | Description |
|---|---|---|---|
| metric | string | – | Metric the decision was based on (default opens) |
| test_id | string | yes | A/B test ID |
| winner_variant | string | yes | Label of the winning variant, e.g. B |
No output schema declared.
No examples provided.
send_campaign ~79
Send a campaign now, or schedule it for a future time by passing scheduled_at. This delivers real email to real recipients and cannot be undone once sending starts — confirm the audience with get_campaign first.
| Name | Type | Req | Description |
|---|---|---|---|
| campaign_id | string | yes | Campaign ID (UUID) |
| scheduled_at | string | – | ISO 8601 timestamp to schedule instead of sending immediately |
No output schema declared.
No examples provided.
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 ~53
Activate or pause an automation. Activating starts enrolling contacts and sending on the configured schedule.
| 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.
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.