Skip to content
InboxGuard logo

InboxGuard MCP server

Which MCP servers are InboxGuard's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-20

← Back to InboxGuard

Whose server it is
  • Registry nameio.inboxguard/email-deliverabilityverified in the MCP registry

The registry name sits under inboxguard.io. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-20
  • Stateanswerschecked 2026-10-20
  • Tools28
  • Server calls itselfinboxguard
  • Server version1.6.0
  • Protocol version2025-06-18

On 2026-10-20 the server answered initialize and tools/list without a sign-in. First answer in 266 ms.

Should an agent connect itConnect it, with care
  • Its tools do every use case we checked: Scan a sending domain's SPF, DKIM and DMARC records; Publish the exact DNS fix at your registrar.

Once connected

  • For "Scan a sending domain's SPF, DKIM and DMARC records", the likely first call is scan_domain.
  • For "Publish the exact DNS fix at your registrar", the likely first call is get_dns_fix_plan.
  • remove_domain, create_notification_channel, create_share_link change data without a sign-in: anyone with the address can call them.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 7, the first on 2026-10-20
  • INITE MCP score79 of 100answers 100 · does the job 100 · definitions 100 · context 94 · connects 100 · lowered by the warning signs below
  • What an agent can do with it2 of 2 use cases
  • Answered100% of days7 of 7 daily checks
  • Median first answer273 ms
  • Space in an agent's context≈ 3,804 tokensthe definitions of all its tools (28), which an agent carries on every turn
  • Tool definitionsA · 100 of 100
  • Typed results0 of 28 toolsdeclared outputSchema: results come typed, read once
  • Every tool passes all six checks.

What an agent can do with it

  • can do · Scan a sending domain's SPF, DKIM and DMARC records
  • can do · Publish the exact DNS fix at your registrar
  • not sure · Ingest DMARC aggregate reports and receive alerts

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

  • Tools that change data, on a server that answers without a sign-in: remove_domain, create_notification_channel, create_share_link

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers28 tools · read 2026-10-20
  • 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…

  • 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…

  • 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…

  • 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…

  • 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…

  • 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…

  • 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…

  • 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…

  • 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 /…

  • 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…

  • 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…

  • 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…

  • 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_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…

  • 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…

  • 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…

  • 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…

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "email-deliverability": {
      "type": "http",
      "url": "https://mcp.inboxguard.io/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http inboxguard https://mcp.inboxguard.io/mcp

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://mcp.inboxguard.io/mcp as a custom connector in the settings.

OpenAPI spec

30 paths, read 2026-10-20. Open the spec ↗

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.