# Mail Security Tools (remote · api.mailsecuritytools.com)

DMARC/SPF/DKIM/MX checks, email score, 100-domain bulk score, webhook watch alerts (x402 USDC).

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

## Components

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

## Channel facts

- Endpoint: `https://api.mailsecuritytools.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.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**: 76/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 722 tokens (~103/item across 7 items; 7 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 13/100
  - Stability observed for 4 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 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 8 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 Mail Security Tools MCP server?

Mail Security Tools is a hosted endpoint at https://api.mailsecuritytools.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-mailsecuritytools-api-email-security 'https://api.mailsecuritytools.com/mcp'
```

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "com-mailsecuritytools-api-email-security": {
      "type": "http",
      "url": "https://api.mailsecuritytools.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 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-16 (score 68, +1)

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

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

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional regression] Schema quality: 484 → 722
- [functional improvement] Stability: unverified → 0.03
- [functional] Server version: 1.0.0 → 1.1.0
- [functional] New tool “bulk_email_security_score”
- [functional] New tool “watch_status”

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

First indexed and scored.

## MCP tools (7)

### `check_domain_email_security` (~80 tokens)

Free. Look up a domain's MX, SPF (record, DNS lookup count, all qualifier), DMARC (policy, rua) and DKIM (common selectors, key size) from live DNS and list issues. No payment.

Input parameters:

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

### `pricing` (~21 tokens)

Free. Prices of the paid tools, payment network and receiving address.

### `email_security_score` (~96 tokens)

Grade a domain's email security 0-100 (A-F): SPF 30, DMARC 40, DKIM 25, MX 5, from live DNS, with findings and the top 3 fixes. Read-only. Costs $0.01 USDC via x402; errors are not charged.

Input parameters:

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

### `check_email_address` (~69 tokens)

Check one email address: syntax, MX / null MX, disposable domain, role account, free provider; verdict ok / risky / undeliverable. No SMTP probe. Costs $0.01 USDC via x402; errors are not charged.

Input parameters:

- `email` (string, required): Email address

### `email_fix_plan` (~109 tokens)

Email security fix plan for one domain: the exact SPF, DKIM and DMARC records to publish (create / replace / keep, name, value, why), in order, with click-path steps for the domain's DNS host and a staged DMARC rollout. Non-sending domains get a lock-down set. Costs $1 USDC via x402; errors are not charged.

Input parameters:

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

### `bulk_email_security_score` (~114 tokens)

Score up to 100 domains' email security in one call (SPF 30, DMARC 40, DKIM 25, MX 5 from live DNS): per-domain score, grade and issues, plus a summary with grade counts, domains missing DMARC or SPF, and the worst 10. For MSPs and agents checking a client or vendor list. Costs $0.50 USDC via x402; errors are not charged.

Input parameters:

- `domains` (array, required): Domains, 1-100

### `watch_status` (~68 tokens)

Free. Status of a paid email setup watch (created with POST /v1/watch): items, expiry, last check, last webhook delivery and current SPF/DMARC/DKIM/MX state.

Input parameters:

- `watch_id` (string, required): Watch id, e.g. msw_abcdefghijklmnop

## Diagnostics

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

## Score history

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

## Common questions

### What is the Mail Security Tools MCP server?

Mail Security Tools is an MCP server listed in the public MCP registry as com.mailsecuritytools.api/email-security. DMARC/SPF/DKIM/MX checks, email score, 100-domain bulk score, webhook watch alerts (x402 USDC). This page covers its hosted endpoint (https://api.mailsecuritytools.com/mcp).

### Is the Mail Security Tools MCP server safe to use?

Mail Security Tools 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 Mail Security Tools MCP server expose?

Mail Security Tools exposes 7 tools: check_domain_email_security, pricing, email_security_score, check_email_address, email_fix_plan, and 2 more. Their descriptions and schemas cost roughly 557 tokens of context every time the server is loaded.

### Does the Mail Security Tools MCP server require authentication?

No. We connected to Mail Security Tools without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Mail Security Tools MCP server still maintained?

Mail Security Tools 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.mailsecuritytools.com/mcp
- Website: https://api.mailsecuritytools.com/llms.txt
- Changelog RSS feed: https://verifymcp.io/servers/com-mailsecuritytools-api-email-security/api.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-mailsecuritytools-api-email-security/api.json
- HTML version of this page: https://verifymcp.io/servers/com-mailsecuritytools-api-email-security/api