Skip to content

InboxGuards Email Check MCP server

com.inboxguardstest.api/emailapi.inboxguardstest.comstreamable-httpv1.2.0Scanned

Check emails before you send, and get a $1 SPF/DKIM/DMARC fix plan for your domain. Pay per call.

4 tools: 2 change things and 2 only read.

Tools: 0 delete, 0 irreversible, 2 write, 2 read.
  • Reads private data · 1
  • Reads text others write · 2
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

2 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the InboxGuards Email Check MCP server can do

The InboxGuards Email Check MCP server is published by api.inboxguardstest.com, a domain the MCP Registry verified. It has 4 tools. It can create or change data (2 tools: pricing and check_email_address), but cannot delete data. 2 tools only read.

1 tool reads private data (email_fix_plan); 2 tools bring in text other people can write (check_email_address and email_fix_plan).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 13, 2026, version 1.2.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

4 tools

Changes things 2Claude Code: ask
  • check_email_addressCheck one email address before you send to it: syntax, whether the domain accepts mail (MX, null MX or implicit A record), a disposable-domain flag (public CC0 list of about 9,900 …Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Check one email address before you send to it: syntax, whether the domain accepts mail (MX, null MX or implicit A record), a disposable-domain flag (public CC0 list of about 9,900 domains), a role-account flag (info@, support@, noreply@...) and a free-provider flag. Returns a verdict of ok, risky or undeliverable with plain reasons. Use validate_email first if you only need syntax. No SMTP probe is made and no mail is sent, so it cannot confirm the mailbox exists. The address is not stored or logged. Read-only; one live DNS lookup via Cloudflare DoH. Costs $0.005 USDC per call via x402 (payment goes in _meta["x402/payment"]); invalid input or a DNS failure returns an error and is not charged.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true
    • destructiveHint: false
    • idempotentHint: true
  • pricingFree.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Free. Return the price of check_email_address (and of the HTTP-only email test report), the payment network (Base) and the receiving address. No input, no network request, no payment.

    Annotations the server declares

    • title: Prices (free)
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
    • destructiveHint: false
Only reads 2Show 2 read-only tools
  • email_fix_planGet an email security fix plan for one domain: the exact SPF, DKIM and DMARC DNS records to publish (create / replace / keep, record name, value and why), in order, plus click-path…Reads private dataReads text others writeNo findings

    Why it is in this group

    • The description's first verb is "get": a word for reading.

    What it can reach

    • private-dataThe name "email_fix_plan" says "email": it reads mail.
    • private-dataThe description's first sentence says "get" and "email": it reads mail.
    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe name "email_fix_plan" says "email": it reads inbound email, which other people can write.
    • untrusted-inputThe description's first sentence says "get" and "email": it reads inbound email, which other people can write.
    Description, as the server wrote it
    Get an email security fix plan for one domain: the exact SPF, DKIM and DMARC DNS records to publish (create / replace / keep, record name, value and why), in order, plus click-path steps for the domain's DNS host (Cloudflare, GoDaddy, Route 53, Namecheap, Squarespace/Google, Vercel and others). Reads live MX, NS, SPF, DKIM and DMARC; detects Google Workspace, Microsoft 365, Zoho, Proton, Fastmail, GoDaddy and Cloudflare Email Routing; merges SPF within the 10-lookup limit, keeps existing senders, and stages DMARC none -> quarantine -> reject. Domains that send no mail get a lock-down set. Use it when mail lands in spam, before a DMARC rollout, or for a client. DKIM keys are generated by the mail provider, so for those it gives the exact console path. Read-only; nothing is stored. Costs $1 USDC per call via x402 (payment goes in _meta["x402/payment"]); invalid input, an unknown domain or a DNS failure returns an error and is not charged.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true
    • destructiveHint: false
    • idempotentHint: true
  • validate_emailFree.No findings

    Why it is in this group

    • The name "validate_email" says "validate": a word for reading.
    Description, as the server wrote it
    Free. Check the syntax of an email address offline and get the normalized address and domain, before paying for check_email_address. No DNS lookup, no network request, no payment.

    Annotations the server declares

    • title: Validate email syntax (free)
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
    • destructiveHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write2
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:40 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
2
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://api.inboxguardstest.com/mcp: tools/list returned 4 tools to an anonymous client, including pricing (write), check_email_address (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.2.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http email https://api.inboxguardstest.com/mcp
claude mcp add --transport http email https://api.inboxguardstest.com/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__email__validate_email",
      "mcp__email__email_fix_plan"
    ],
    "ask": [
      "mcp__email__pricing",
      "mcp__email__check_email_address"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as email. Review it before you use it.

Capability tags behind 2 rules
  • mcp__email__check_email_address untrusted-input
  • mcp__email__email_fix_plan private-data, untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.inboxguardstest.api/email/verify?hash=bce74ff44da7d9da903d0fd00951300d961cb0e258aa98198b8a93796dae7068" | jq -e '.changed == false'

Pinned hash bce74ff44da7, from Nov 13, 2026, 12:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.inboxguardstest.api/email/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.inboxguardstest.api/email
[![Anlyon Radar](https://radar.anlyon.com/badge/com.inboxguardstest.api/email.svg)](https://radar.anlyon.com/servers/com.inboxguardstest.api/email)

Source: MCP Registry. Synced Oct 21, 2026, 17:56 UTC.

InboxGuards Email Check MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the InboxGuards Email Check MCP server safe?

No scan can promise that. What its definitions show: 4 tools, 2 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the InboxGuards Email Check MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the InboxGuards Email Check MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the InboxGuards Email Check MCP server have?

4 tools: 2 write, 2 read. pricing, check_email_address, validate_email and email_fix_plan.

Does the InboxGuards Email Check MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the InboxGuards Email Check MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the InboxGuards Email Check MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 13, 2026.