Index / MCP servers / Email Deliverability

Email Deliverability MCP server

Connect Email Deliverability and your agent gets 28 tools, among them analyze_headers, apply_dns_fix, check_blocklists. It answers at https://mcp.inboxguard.io/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 6 of 6 times since 11 September 2026; the last check, on 24 October 2026, succeeded.

Status
Answering
Tools
28
Official
yes, served from inboxguard.io
Reliability
6 of 6 checks
Response time
351 ms
Transport
streamable HTTP
Last checked
24 October 2026

Scan and fix a domain's email deliverability (SPF, DKIM, DMARC, MTA-STS, BIMI, DNS blocklists).

Description as the publisher wrote it.

The 28 tools Email Deliverability offers

ToolWhat it does
analyze_headersRe-verify SPF, DKIM, DMARC, and ARC from a raw RFC 5322 email (full message or just the headers block). Returns InboxGuard's independent verdict (`ours`), the sender's own Authentication-Results (`theirs`), whether they `agree`, and parsed
Inputs: message, senderIp, helo, mailFrom
apply_dns_fixApply a DNS fix plan to a tracked domain by publishing records at the connected registrar. DESTRUCTIVE: it creates/updates/deletes DNS records. Two-step by design — first call get_dns_fix_plan, then pass its `connectionId` and `ops` here ve
Inputs: domain, connectionId, ops
check_blocklistsCheck a domain (apex + MX-host IPs) against supported DNS blocklists and return listings, targets checked, and issues (authoritative-side queries; no public-resolver false positives).
Inputs: domain
connect_inbox_placementStore the org's seed-list inbox-placement provider + API key (provider: 'mailreach' or 'glockapps'; GlockApps also needs projectId). Enables start_inbox_placement_test. Requires an owner/admin API key with write or full scope.
Inputs: provider, apiKey, projectId
connect_sndsStore this org's Microsoft SNDS (Smart Network Data Services) automated-data-access key so InboxGuard syncs per-IP Outlook/Hotmail reputation daily. Get the key from the SNDS Automated Data Access page (https://sendersupport.olc.protection.
Inputs: key, label
create_notification_channelCreate a channel that InboxGuard alerts are delivered to: webhook (HMAC-signed), Slack, Microsoft Teams, PagerDuty, SMS, or email. Returns the channel id, and for kind=webhook the `signing_secret` used to verify deliveries. Requires an owne
Inputs: kind, target, displayName, severityFilter
create_share_linkCreate a read-only public share link for a tracked domain's latest report (anyone with the URL can view it; no account). Returns a `token` and the public `url` (https://inboxguard.io/r/<token>). Requires an owner/admin API key with write or
Inputs: domain
get_deliverability_reportReturn a structured deliverability report for a tracked domain: the latest score + letter grade + `scoreSubtitle` (explains the denominator when a check was excluded, e.g. "80/100 · scored on 65 of 83 applicable points · 1 check unverified"
Inputs: domain
get_deliverability_scoreReturn the overall deliverability score and letter grade for a domain (runs a fresh scan).
Inputs: domain
get_dmarc_summarySummarize ingested DMARC aggregate (RUA) reports for a domain tracked in your InboxGuard account: report volume, pass rate, top sending sources, and the rua inbox to publish. The domain must already be added to the account, and the plan mus
Inputs: domain, days
get_dns_fix_planCompute the exact DNS-record changes needed to fix a tracked domain's deliverability, based on its latest scan and the org's connected registrar (Cloudflare/Route 53/GoDaddy/Namecheap). Read-only — nothing changes. Returns the `ops` to pass
Inputs: domain
get_domainFull detail for one tracked domain: the domain record, the latest scan with all per-check findings (spf, dmarc, dkim, ptr, mta_sts, tls_rpt, mx_tls, blocklist), recent score history, open/recent alerts, and Google Postmaster stats when conn
Inputs: domain
get_inbox_placement_statusReport whether a seed-list inbox-placement provider is connected for the org, which provider, and how many tests have run. Lists the supported providers when not connected.
get_inbox_placement_testPoll a seed-list inbox-placement test by testId. Returns status (running/completed/failed) and, once measured, the Inbox/Spam/Missing counts and inbox-placement score (0–100). Call after sending your campaign to the seed addresses from star
Inputs: testId
get_portfolioOrg-wide deliverability rollup across every monitored domain: average score + overall grade, the grade distribution (how many domains are A/B/C/D/F/unscored), total open alerts, the domains needing attention (lowest score / open alerts firs
get_scan_jobPoll an async batch scan started with scan_domains_batch: returns status (queued/running/succeeded/partial/failed), completed count, and per-domain results (domain, ok, score, grade) as they finish.
Inputs: jobId
get_snds_ip_statsReturn the latest per-IP reputation from Microsoft SNDS for the org's sending IPs: filter result (GREEN/YELLOW/RED), complaint-rate band, spam-trap hits, message volume, and current block status. Requires SNDS to be connected (see connect_s
get_snds_statusReport whether Microsoft SNDS is connected for the org, the last sync time + status, how many sending IPs are tracked, and how many are currently blocked by Outlook/Hotmail. Use before get_snds_ip_stats to confirm the integration is live.
list_alertsList the account's deliverability alerts (score drops, check failures, blocklist listings). Defaults to open alerts only.
Inputs: resolved, severity, limit
list_domainsList the account's tracked domains with latest scan score, last scan time, and open alert count.
list_inbox_placement_testsList recent seed-list inbox-placement tests for the org (most recent first) with their status and Inbox/Spam/Missing scores.
list_registrar_connectionsList the registrar accounts (Cloudflare, Route 53, GoDaddy, Namecheap) connected to the org — provider, verification, last-used time — plus the supported providers. Use this to check whether the detect-and-fix loop (get_dns_fix_plan / apply
list_scansList recent scans (id, domain, run time, score) across all tracked domains, or for one domain when a name is given.
Inputs: domain, limit
remove_domainStop monitoring a domain and delete it (and its scan history) from the account. DESTRUCTIVE and not reversible. Requires an owner/admin API key with write or full scope. (To ADD a domain, run scan_domain with this API key — authenticated sc
Inputs: domain
resolve_alertMark an alert resolved (or reopen it with resolved=false). Requires an API key with write/full scope. Resolving an already-resolved alert is a no-op.
Inputs: alertId, resolved
scan_domainRun a full email-deliverability scan (SPF, DKIM, DMARC, MTA-STS, TLS-RPT, MX TLS, BIMI, DNS blocklists) for a domain and return a 0-100 score with per-check findings. A check can come back `not_applicable` (does not apply to this domain, e.
Inputs: domain, dkimSelectors
scan_domains_batchQueue an asynchronous batch scan of up to 50 domains and get a jobId immediately (avoids the 30s per-call limit). Poll get_scan_job with the jobId until status is succeeded/partial/failed to read per-domain scores. Requires an API key with
Inputs: domains
start_inbox_placement_testStart a seed-list inbox-placement test. Returns a testId, the seed addresses to mail your campaign to, and (if the provider requires it) a header to insert. After sending to the seeds, poll get_inbox_placement_test for the Inbox/Spam/Missin
Inputs: subject

Add Email Deliverability to your AI client

Every block below points at https://mcp.inboxguard.io/mcp. Pick your client and copy.

Claude Code: one command in your terminal
claude mcp add --transport http email-deliverability https://mcp.inboxguard.io/mcp
Claude Desktop: claude_desktop_config.json
{
  "mcpServers": {
    "email-deliverability": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp.inboxguard.io/mcp"]
    }
  }
}
Cursor: ~/.cursor/mcp.json, or .cursor/mcp.json in a project
{
  "mcpServers": {
    "email-deliverability": {
      "url": "https://mcp.inboxguard.io/mcp"
    }
  }
}
VS Code and GitHub Copilot: .vscode/mcp.json
{
  "servers": {
    "email-deliverability": {
      "type": "http",
      "url": "https://mcp.inboxguard.io/mcp"
    }
  }
}
Zed: Zed settings.json
{
  "context_servers": {
    "email-deliverability": {
      "url": "https://mcp.inboxguard.io/mcp"
    }
  }
}
Windsurf: ~/.codeium/mcp_config.json
{
  "mcpServers": {
    "email-deliverability": {
      "serverUrl": "https://mcp.inboxguard.io/mcp"
    }
  }
}
JetBrains AI Assistant: Settings, Tools, AI Assistant, MCP, New MCP Server, as JSON
{
  "mcpServers": {
    "email-deliverability": {
      "url": "https://mcp.inboxguard.io/mcp"
    }
  }
}
Continue: .continue/mcpServers/neuronto.yaml
name: Email Deliverability
version: 0.0.1
schema: v1
mcpServers:
  - name: Email Deliverability
    type: streamable-http
    url: https://mcp.inboxguard.io/mcp
Gemini CLI: ~/.gemini/settings.json
{
  "mcpServers": {
    "email-deliverability": {
      "httpUrl": "https://mcp.inboxguard.io/mcp"
    }
  }
}
Codex CLI: MCP server config
{
  "mcpServers": {
    "email-deliverability": {
      "type": "http",
      "url": "https://mcp.inboxguard.io/mcp"
    }
  }
}
Warp: MCP servers, + Add, paste JSON
{
  "mcpServers": {
    "email-deliverability": {
      "url": "https://mcp.inboxguard.io/mcp"
    }
  }
}
Goose: a one-click extension link
goose://extension?url=https%3A%2F%2Fmcp.inboxguard.io%2Fmcp&type=streamable_http&id=email-deliverability&name=Email%20Deliverability

Is Email Deliverability up right now?

It answered our last check on 24 October 2026 in 351 ms. Over 6 checks since 11 September 2026 it answered 6. Status here comes from Neuronto's own probes, not from the publisher.

MCP servers similar to Email Deliverability

Questions about Email Deliverability

Is there an official Email Deliverability MCP server?

Yes. It is published by inboxguard.io and served from mcp.inboxguard.io, the vendor's own domain: https://mcp.inboxguard.io/mcp.

How many tools does Email Deliverability have?

28, as returned by the server's own tools/list on 22 September 2026: analyze_headers, apply_dns_fix, check_blocklists, connect_inbox_placement, connect_snds, create_notification_channel, create_share_link, get_deliverability_report, and 20 more.

Is Email Deliverability down?

It answered our last check on 24 October 2026 in 351 ms. Over 6 checks since 11 September 2026 it answered 6.

How do I add Email Deliverability to Cursor?

Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://mcp.inboxguard.io/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.

Does Email Deliverability need an API key?

It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.

Where this comes from

Publisher: io.inboxguard. Endpoint host: mcp.inboxguard.io. ARD identifier: urn:air:io.inboxguard:mcp:email-deliverability. First indexed 10 September 2026. The tools are exactly what the server returned; nothing on this page is inferred from its name. Ranking in Neuronto search is never for sale.

Is this your server? Get a message the day it stops answering or its tools change: monitoring, 14 days free. Or claim the domain to manage how it is listed.