Community Gmail server with auto-auth: search, read and send email via MCP.
Nothing to run from here
Email Deliverability is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
28
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Scan and fix a domain's email deliverability (SPF, DKIM, DMARC, MTA-STS, BIMI, DNS blocklists).
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http email-deliverability-mcp https://mcp.inboxguard.io/mcp
# 2 — ask your agent for something these tools do
# scan_domain, get_deliverability_score, check_blocklists and 25 more
Email Deliverability costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
INAll 1 server
inboxguard1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http email-deliverability-mcp https://mcp.inboxguard.io/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
28 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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 r
| Parameter | Type | Required | Notes |
|---|---|---|---|
| domain | string | yes | Domain to scan, e.g. example.com. |
| dkimSelectors | array | no | Optional DKIM selectors to probe. |
Return the overall deliverability score and letter grade for a domain (runs a fresh scan).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| domain | string | yes | Domain to score, e.g. example.com. |
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).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| domain | string | yes | Domain to check, e.g. example.com. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| domain | string | yes | Domain name tracked in the account, e.g. example.com. |
| days | integer | no | Lookback window in days (default 30, max 90). |
List the account's tracked domains with latest scan score, last scan time, and open alert count.
No parameter schema on file.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| domain | string | yes | Domain name as tracked in the account, e.g. example.com. |
List the account's deliverability alerts (score drops, check failures, blocklist listings). Defaults to open alerts only.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| resolved | string | no | 'false' = open alerts only (default), 'true' = resolved only, 'all' = both. |
| severity | string | no | Filter by severity (default 'all'). |
| limit | integer | no | Max alerts to return (default 50). |
List recent scans (id, domain, run time, score) across all tracked domains, or for one domain when a name is given.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| domain | string | no | Optional: restrict to one tracked domain by name, e.g. example.com. Omit for all domains. |
| limit | integer | no | Max scans to return (default 20). |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| alertId | string | yes | Alert UUID, from list_alerts or get_domain. |
| resolved | boolean | no | true (default) marks the alert resolved; false reopens it. |
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 s
| Parameter | Type | Required | Notes |
|---|---|---|---|
| domain | string | yes | Domain name tracked in the account, e.g. example.com. |
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 a
| Parameter | Type | Required | Notes |
|---|---|---|---|
| domain | string | yes | Domain name tracked in the account, e.g. example.com. |
| connectionId | string | yes | The connectionId from get_dns_fix_plan. |
| ops | array | yes | The ops array from get_dns_fix_plan, passed verbatim. The server validates each op against a freshly recomputed diff before executing. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| message | string | yes | The raw email — full RFC 5322 message, or at least the headers block (Received, Authentication-Results, DKIM-Signature, From, …). |
| senderIp | string | no | Optional: connecting IP to evaluate SPF against (overrides the IP parsed from Received headers). |
| helo | string | no | Optional: the SMTP HELO/EHLO domain. |
| mailFrom | string | no | Optional: the envelope MAIL FROM (return-path) address. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| domains | array | yes | 1-50 domains to scan, e.g. ["example.com","acme.com"]. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| jobId | string | yes | The jobId returned by scan_domains_batch. |
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.)
| Parameter | Type | Required | Notes |
|---|---|---|---|
| domain | string | yes | Domain name tracked in the account, e.g. example.com. |
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.
No parameter schema on file.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| kind | string | yes | Channel type. |
| target | string | yes | Destination matching kind: the webhook/Slack/Teams URL, PagerDuty integration key, phone number (E.164), or email address. |
| displayName | string | no | Optional label for the channel. |
| severityFilter | array | no | Which alert severities to deliver (default ["critical","warn"]). |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| domain | string | yes | Domain name tracked in the account, e.g. example.com. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| key | string | yes | The SNDS access key from the SNDS Automated Data Access page. |
| label | string | no | Optional label, e.g. "prod sending IPs". |
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.
No parameter schema on file.
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).
No parameter schema on file.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| provider | string | yes | Inbox-placement vendor. |
| apiKey | string | yes | The vendor API key. |
| projectId | string | no | GlockApps project id (required for provider=glockapps). |
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.
No parameter schema on file.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| subject | string | no | Optional subject line to associate with the 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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| testId | string | yes | The testId returned by start_inbox_placement_test. |
List recent seed-list inbox-placement tests for the org (most recent first) with their status and Inbox/Spam/Missing scores.
No parameter schema on file.
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 could
| Parameter | Type | Required | Notes |
|---|---|---|---|
| domain | string | yes | Domain name tracked in the account, e.g. example.com. |
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.
No parameter schema on file.
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Email Deliverability or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.2.0.
1.2.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Email Deliverability can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.