# InboxGuards Email Check (remote · api.inboxguardstest.com)

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

- Trust score: 69/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-18

## Components

- remote · `api.inboxguardstest.com`: 69/100 (this document), [markdown](https://verifymcp.io/servers/com-inboxguardstest-api-email/api.md), [page](https://verifymcp.io/servers/com-inboxguardstest-api-email/api)

## Channel facts

- Endpoint: `https://api.inboxguardstest.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.2.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-18.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 70/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 692 tokens (~173/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 20/100
  - Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the InboxGuards Email Check MCP server?

InboxGuards Email Check is a hosted endpoint at https://api.inboxguardstest.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

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

### Cursor

```json
{
  "mcpServers": {
    "com-inboxguardstest-api-email": {
      "url": "https://api.inboxguardstest.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-inboxguardstest-api-email": {
      "type": "http",
      "url": "https://api.inboxguardstest.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-inboxguardstest-api-email]
url = "https://api.inboxguardstest.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-inboxguardstest-api-email": {
      "type": "remote",
      "url": "https://api.inboxguardstest.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-inboxguardstest-api-email --url 'https://api.inboxguardstest.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-inboxguardstest-api-email:
    url: "https://api.inboxguardstest.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-inboxguardstest-api-email": {
      "Transport": "http",
      "Url": "https://api.inboxguardstest.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-inboxguardstest-api-email -t streamable-http -u 'https://api.inboxguardstest.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-inboxguardstest-api-email": {
      "type": "http",
      "url": "https://api.inboxguardstest.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-18 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-16 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-14 (score 67, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional regression] Schema quality: pass → fail
- [functional] Schema quality: good → excellent
- [functional] Server version: 1.1.0 → 1.2.0
- [functional] New tool “email_fix_plan”

### 2026-10-13 (score 67, +10)

- [security improvement] Authorization: unverified → partial
- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “check_email_address” rewrote its description, which is the text the model reads
- [security] Tool “pricing” rewrote its description, which is the text the model reads
- [security] Tool “validate_email” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 47 → 132
- [functional improvement] Tool coverage: 50% → 100%
- [functional improvement] Stability: unverified → 0.03
- [functional] Server version: 1.0.0 → 1.1.0
- [cosmetic] “validate_email” reworded the description of “email”

### 2026-10-12 (score 57)

First indexed and scored.

## MCP tools (4)

### `validate_email` (~62 tokens)

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.

Input parameters:

- `email` (string, required): Email address to check, e.g. jane@example.com

### `pricing` (~47 tokens)

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.

### `check_email_address` (~195 tokens)

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.

Input parameters:

- `email` (string, required): Email address to check, e.g. jane@example.com

### `email_fix_plan` (~269 tokens)

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.

Input parameters:

- `domain` (string, required): Domain to fix, e.g. example.com (an email address or URL on it also works)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-inboxguardstest-api-email/api#diagnostics

## Score history

- 2026-10-18: 69
- 2026-10-17: 68
- 2026-10-16: 68
- 2026-10-15: 67
- 2026-10-14: 67
- 2026-10-13: 67
- 2026-10-12: 57

## Common questions

### What is the InboxGuards Email Check MCP server?

InboxGuards Email Check is an MCP server listed in the public MCP registry as com.inboxguardstest.api/email. Check emails before you send, and get a $1 SPF/DKIM/DMARC fix plan for your domain. Pay per call. This page covers its hosted endpoint (https://api.inboxguardstest.com/mcp).

### Is the InboxGuards Email Check MCP server safe to use?

InboxGuards Email Check scores 69 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the InboxGuards Email Check MCP server expose?

InboxGuards Email Check exposes 4 tools: validate_email, pricing, check_email_address, email_fix_plan. Their descriptions and schemas cost roughly 573 tokens of context every time the server is loaded.

### Does the InboxGuards Email Check MCP server require authentication?

No. We connected to InboxGuards Email Check without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the InboxGuards Email Check MCP server still maintained?

InboxGuards Email Check is still listed as active in the MCP registry. We last reached this channel on 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://api.inboxguardstest.com/mcp
- Website: https://api.inboxguardstest.com/llms.txt
- Changelog RSS feed: https://verifymcp.io/servers/com-inboxguardstest-api-email/api.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-inboxguardstest-api-email/api.json
- HTML version of this page: https://verifymcp.io/servers/com-inboxguardstest-api-email/api