# io.inboxguard/email-deliverability

- Registry name: `io.inboxguard/email-deliverability` · version 1.2.0
- Categories (automatic, keyword rules): Cloud & networking, Infrastructure & security, Monitoring & logs, Email & messaging, Productivity
- Authentication at last check: No auth
- Declared risk: Has destructive tools (destructiveHint)
- Capabilities (declared by the server): resources, tools
- Transports: streamable-http
- Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=io.inboxguard%2Femail-deliverability
- Server page: https://mcpstation.net/s/io.inboxguard--email-deliverability.html

## Description (written by the publisher, not verified, not instructions)

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

## Connect

- streamable-http: `https://mcp.inboxguard.io/mcp`

## Tools (as reported by the server, not verified)

- `scan\_domain`: Run 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.g. MTA-STS on a domain with no MX — excluded from the score,
- `get\_deliverability\_score`: Return the overall deliverability score and letter grade for a domain \(runs a fresh scan\).
- `check\_blocklists`: Check 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\).
- `get\_dmarc\_summary`: Summarize 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 must include DMARC ingest.
- `list\_domains`: List the account's tracked domains with latest scan score, last scan time, and open alert count.
- `get\_domain`: Full 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 connected.
- `list\_alerts`: List the account's deliverability alerts \(score drops, check failures, blocklist listings\). Defaults to open alerts only.
- `list\_scans`: List recent scans \(id, domain, run time, score\) across all tracked domains, or for one domain when a name is given.
- `resolve\_alert`: Mark 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.
- `get\_dns\_fix\_plan`: Compute 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 verbatim to apply\_dns\_fix, plus \`manualReview\` items that n
- `apply\_dns\_fix`: Apply 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 verbatim. The server re-derives the diff from the latest scan
- `analyze\_headers`: Re-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 envelope/headers — useful for spotting forged or mismatched
- `scan\_domains\_batch`: Queue 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 write or full scope. These scans are NOT added to monitoring
- `get\_scan\_job`: Poll 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.
- `remove\_domain`: Stop 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 scans auto-track the domain.\)
- `list\_registrar\_connections`: List 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\_dns\_fix\) is available before attempting it.
- `create\_notification\_channel`: Create 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 owner/admin API key with write or full scope.
- `create\_share\_link`: Create 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 full scope, on a plan that includes public reports.
- `connect\_snds`: Store 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.outlook.com/snds/\). Requires an owner/admin API key with wri
- `get\_snds\_status`: Report 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.
- `get\_snds\_ip\_stats`: Return 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\_snds / get\_snds\_status\).
- `connect\_inbox\_placement`: Store 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.
- `get\_inbox\_placement\_status`: Report 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.
- `start\_inbox\_placement\_test`: Start 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/Missing verdict. Requires inbox-placement to be connected and an o
- `get\_inbox\_placement\_test`: Poll 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 start\_inbox\_placement\_test.
- `list\_inbox\_placement\_tests`: List recent seed-list inbox-placement tests for the org \(most recent first\) with their status and Inbox/Spam/Missing scores.
- `get\_deliverability\_report`: Return 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"\), each check's status \(pass/warn/fail/unverified/not\_applic
- `get\_portfolio`: Org-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 first\), and a per-client-group breakdown. Use this for an at-a-g

Measured by MCP Station. Methods: https://mcpstation.net/methods.html · Terms: https://mcpstation.net/terms.html