MCPサーバー

email-deliverability

io.inboxguard/email-deliverability

このMCPでできること

Scans and monitors domain email deliverability, including SPF, DKIM, DMARC, DNS blocklists, inbox placement, reputation, alerts, and guided DNS fixes.

analyze_headers
Analyze raw email 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 auth results. No account needed.
読み取り専用 外部アクセスあり 冪等
入力スキーマ
{'type': 'object', 'required': ['message'], 'properties': {'helo': {'type': 'string', 'description': 'Optional: the SMTP HELO/EHLO domain.'}, 'message': {'type': 'string', 'minLength': 50, 'description': 'The raw email — full RFC 5322 message, or at least the headers block (Received, Authentication-Results, DKIM-Signature, From, …).'}, 'mailFrom': {'type': 'string', 'description': 'Optional: the envelope MAIL FROM (return-path) address.'}, 'senderIp': {'type': 'string', 'description': 'Optional: connecting IP to evaluate SPF against (overrides the IP parsed from Received headers).'}}}
apply_dns_fix
Apply the DNS fix plan
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 and rejects any op that no longer matches, so an agent can never apply arbitrary records. Requires an owner/admin API key with write or full scope. Re-scan afterward to confirm the fix.
破壊的操作あり
入力スキーマ
{'type': 'object', 'required': ['domain', 'connectionId', 'ops'], 'properties': {'ops': {'type': 'array', 'items': {'type': 'object'}, 'description': 'The `ops` array from get_dns_fix_plan, passed verbatim. The server validates each op against a freshly recomputed diff before executing.'}, 'domain': {'type': 'string', 'description': 'Domain name tracked in the account, e.g. example.com.'}, 'connectionId': {'type': 'string', 'format': 'uuid', 'description': 'The connectionId from get_dns_fix_plan.'}}}
check_blocklists
Check DNS 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).
読み取り専用 外部アクセスあり 冪等
入力スキーマ
{'type': 'object', 'required': ['domain'], 'properties': {'domain': {'type': 'string', 'description': 'Domain to check, e.g. example.com.'}}}
connect_inbox_placement
Connect an inbox-placement provider
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.
入力スキーマ
{'type': 'object', 'required': ['provider', 'apiKey'], 'properties': {'apiKey': {'type': 'string', 'description': 'The vendor API key.'}, 'provider': {'enum': ['mailreach', 'glockapps'], 'type': 'string', 'description': 'Inbox-placement vendor.'}, 'projectId': {'type': 'string', 'description': 'GlockApps project id (required for provider=glockapps).'}}}
connect_snds
Connect Microsoft 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 write or full scope. Data appears within ~24h of the first sync.
入力スキーマ
{'type': 'object', 'required': ['key'], 'properties': {'key': {'type': 'string', 'description': 'The SNDS access key from the SNDS Automated Data Access page.'}, 'label': {'type': 'string', 'description': 'Optional label, e.g. "prod sending IPs".'}}}
create_notification_channel
Create a 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.
入力スキーマ
{'type': 'object', 'required': ['kind', 'target'], 'properties': {'kind': {'enum': ['webhook', 'slack', 'teams', 'pagerduty', 'sms', 'email'], 'type': 'string', 'description': 'Channel type.'}, 'target': {'type': 'string', 'description': 'Destination matching `kind`: the webhook/Slack/Teams URL, PagerDuty integration key, phone number (E.164), or email address.'}, 'displayName': {'type': 'string', 'description': 'Optional label for the channel.'}, 'severityFilter': {'type': 'array', 'items': {'enum': ['info', 'warn', 'critical'], 'type': 'string'}, 'description': 'Which alert severities to deliver (default ["critical","warn"]).'}}}
create_share_link
Create a public 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.
入力スキーマ
{'type': 'object', 'required': ['domain'], 'properties': {'domain': {'type': 'string', 'description': 'Domain name tracked in the account, e.g. example.com.'}}}
get_deliverability_report
Get a 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_applicable — `not_applicable` means the check doesn't apply to this domain and `unverified` means it couldn't be checked this scan; neither is a failure), the top issues to fix, blocklist count, and DMARC policy. Includes `pdfUrl` — the same auth-gated endpoint that returns a branded one-page PDF (send your bearer token). Use this to summarize a domain's posture or hand a client a report.
読み取り専用 冪等
入力スキーマ
{'type': 'object', 'required': ['domain'], 'properties': {'domain': {'type': 'string', 'description': 'Domain name tracked in the account, e.g. example.com.'}}}
get_deliverability_score
Get deliverability score
Return the overall deliverability score and letter grade for a domain (runs a fresh scan).
読み取り専用 外部アクセスあり 冪等
入力スキーマ
{'type': 'object', 'required': ['domain'], 'properties': {'domain': {'type': 'string', 'description': 'Domain to score, e.g. example.com.'}}}
get_dmarc_summary
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.
読み取り専用 冪等
入力スキーマ
{'type': 'object', 'required': ['domain'], 'properties': {'days': {'type': 'integer', 'maximum': 90, 'minimum': 1, 'description': 'Lookback window in days (default 30, max 90).'}, 'domain': {'type': 'string', 'description': 'Domain name tracked in the account, e.g. example.com.'}}}
get_dns_fix_plan
Preview the 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 need a human decision (SPF sender list, DKIM keys, BIMI logo). Requires the domain to be tracked, a scan to exist, and a registrar connection covering the zone.
読み取り専用 冪等
入力スキーマ
{'type': 'object', 'required': ['domain'], 'properties': {'domain': {'type': 'string', 'description': 'Domain name tracked in the account, e.g. example.com.'}}}
get_domain
Get domain detail
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.
読み取り専用 冪等
入力スキーマ
{'type': 'object', 'required': ['domain'], 'properties': {'domain': {'type': 'string', 'description': 'Domain name as tracked in the account, e.g. example.com.'}}}
get_inbox_placement_status
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.
読み取り専用 冪等
入力スキーマ
{'type': 'object', 'properties': {}}
get_inbox_placement_test
Get an 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.
読み取り専用 冪等
入力スキーマ
{'type': 'object', 'required': ['testId'], 'properties': {'testId': {'type': 'string', 'format': 'uuid', 'description': 'The testId returned by start_inbox_placement_test.'}}}
get_portfolio
Get the domain portfolio rollup
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-glance portfolio health summary across an agency or multi-domain account.
読み取り専用 冪等
入力スキーマ
{'type': 'object', 'properties': {}}
get_scan_job
Get batch-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.
読み取り専用 冪等
入力スキーマ
{'type': 'object', 'required': ['jobId'], 'properties': {'jobId': {'type': 'string', 'format': 'uuid', 'description': 'The jobId returned by scan_domains_batch.'}}}
get_snds_ip_stats
Get Microsoft SNDS per-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).
読み取り専用 冪等
入力スキーマ
{'type': 'object', 'properties': {}}
get_snds_status
Get Microsoft 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.
読み取り専用 冪等
入力スキーマ
{'type': 'object', 'properties': {}}
list_alerts
List alerts
List the account's deliverability alerts (score drops, check failures, blocklist listings). Defaults to open alerts only.
読み取り専用 冪等
入力スキーマ
{'type': 'object', 'properties': {'limit': {'type': 'integer', 'maximum': 200, 'minimum': 1, 'description': 'Max alerts to return (default 50).'}, 'resolved': {'enum': ['false', 'true', 'all'], 'type': 'string', 'description': "'false' = open alerts only (default), 'true' = resolved only, 'all' = both."}, 'severity': {'enum': ['critical', 'warn', 'info', 'all'], 'type': 'string', 'description': "Filter by severity (default 'all')."}}}
list_domains
List tracked domains
List the account's tracked domains with latest scan score, last scan time, and open alert count.
読み取り専用 冪等
入力スキーマ
{'type': 'object', 'properties': {}}
list_inbox_placement_tests
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.
読み取り専用 冪等
入力スキーマ
{'type': 'object', 'properties': {}}
list_registrar_connections
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.
読み取り専用 冪等
入力スキーマ
{'type': 'object', 'properties': {}}
list_scans
List scan history
List recent scans (id, domain, run time, score) across all tracked domains, or for one domain when a name is given.
読み取り専用 冪等
入力スキーマ
{'type': 'object', 'properties': {'limit': {'type': 'integer', 'maximum': 100, 'minimum': 1, 'description': 'Max scans to return (default 20).'}, 'domain': {'type': 'string', 'description': 'Optional: restrict to one tracked domain by name, e.g. example.com. Omit for all domains.'}}}
remove_domain
Remove a monitored 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.)
破壊的操作あり
入力スキーマ
{'type': 'object', 'required': ['domain'], 'properties': {'domain': {'type': 'string', 'description': 'Domain name tracked in the account, e.g. example.com.'}}}
resolve_alert
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.
冪等
入力スキーマ
{'type': 'object', 'required': ['alertId'], 'properties': {'alertId': {'type': 'string', 'format': 'uuid', 'description': 'Alert UUID, from list_alerts or get_domain.'}, 'resolved': {'type': 'boolean', 'description': 'true (default) marks the alert resolved; false reopens it.'}}}
scan_domain
Scan domain deliverability
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, not a failure) or `unverified` (could not be determined this scan, e.g. DKIM behind an ESP with a random per-tenant selector like Amazon SES Easy DKIM — never treat as a failure). `scoreSubtitle` explains the denominator when anything was excluded. Runs at your plan tier (full blocklist set on paid plans) and saves the scan to the domain history in your account.
読み取り専用 外部アクセスあり 冪等
入力スキーマ
{'type': 'object', 'required': ['domain'], 'properties': {'domain': {'type': 'string', 'description': 'Domain to scan, e.g. example.com.'}, 'dkimSelectors': {'type': 'array', 'items': {'type': 'string'}, 'description': 'Optional DKIM selectors to probe.'}}}
scan_domains_batch
Batch-scan domains (async)
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 or saved to history.
外部アクセスあり
入力スキーマ
{'type': 'object', 'required': ['domains'], 'properties': {'domains': {'type': 'array', 'items': {'type': 'string'}, 'maxItems': 50, 'minItems': 1, 'description': '1-50 domains to scan, e.g. ["example.com","acme.com"].'}}}
start_inbox_placement_test
Start an 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 owner/admin API key with write or full scope.
入力スキーマ
{'type': 'object', 'properties': {'subject': {'type': 'string', 'description': 'Optional subject line to associate with the test.'}}}
追加
get_portfolio
2026年9月17日12:53
追加
get_deliverability_report
2026年9月17日12:53
追加
list_inbox_placement_tests
2026年9月17日12:53
追加
get_inbox_placement_test
2026年9月17日12:53
追加
start_inbox_placement_test
2026年9月17日12:53
追加
get_inbox_placement_status
2026年9月17日12:53
追加
connect_inbox_placement
2026年9月17日12:53
追加
get_snds_ip_stats
2026年9月17日12:53
追加
get_snds_status
2026年9月17日12:53
追加
connect_snds
2026年9月17日12:53
追加
create_share_link
2026年9月17日12:53
追加
create_notification_channel
2026年9月17日12:53
追加
list_registrar_connections
2026年9月17日12:53
追加
remove_domain
2026年9月17日12:53
追加
get_scan_job
2026年9月17日12:53
追加
scan_domains_batch
2026年9月17日12:53
追加
analyze_headers
2026年9月17日12:53
追加
apply_dns_fix
2026年9月17日12:53
追加
get_dns_fix_plan
2026年9月17日12:53
追加
resolve_alert
2026年9月17日12:53
追加
list_scans
2026年9月17日12:53
追加
list_alerts
2026年9月17日12:53
追加
get_domain
2026年9月17日12:53
追加
list_domains
2026年9月17日12:53
追加
get_dmarc_summary
2026年9月17日12:53
追加
check_blocklists
2026年9月17日12:53
追加
get_deliverability_score
2026年9月17日12:53
追加
scan_domain
2026年9月17日12:53