# MailVakt (remote · mcp.mailvakt.com)

Use when email lands in spam: audits SPF, DKIM, DMARC, MX and returns the DNS records to fix it.

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

## Components

- remote · `mcp.mailvakt.com`: 78/100 (this document), [markdown](https://verifymcp.io/servers/com-mailvakt-mailvakt/mcp.md), [page](https://verifymcp.io/servers/com-mailvakt-mailvakt/mcp)

## Channel facts

- Endpoint: `https://mcp.mailvakt.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.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-06.

- **Endpoint Security**: 80/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 is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - 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**: 88/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1028 tokens (~114/item across 9 items; 8 tools + 1 resources), over budget; trim descriptions and params.
  - 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 8 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 9 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).
  - Supports UI / widget rendering.

## Install

### How do I install the MailVakt MCP server?

MailVakt is a hosted endpoint at https://mcp.mailvakt.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-mailvakt-mailvakt 'https://mcp.mailvakt.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-mailvakt-mailvakt": {
      "url": "https://mcp.mailvakt.com/mcp"
    }
  }
}
```

### VS Code

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

### Codex

```toml
[mcp_servers.com-mailvakt-mailvakt]
url = "https://mcp.mailvakt.com/mcp"
```

### opencode

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

### OpenClaw

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

### Hermes

```yaml
mcp_servers:
  com-mailvakt-mailvakt:
    url: "https://mcp.mailvakt.com/mcp"
```

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "com-mailvakt-mailvakt": {
      "type": "http",
      "url": "https://mcp.mailvakt.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-06 (score 78, +1)

- [security] Tool “analyze_email_headers” rewrote its description, which is the text the model reads
- [security] Tool “diagnose_domain” rewrote its description, which is the text the model reads

### 2026-10-04 (score 77, +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-03 (score 76, +7)

- [security improvement] HTTPS: unverified → pass
- [security improvement] HSTS header: fail → pass
- [functional improvement] Stability: unverified → 0.03

### 2026-10-02 (score 69)

First indexed and scored.

## MCP tools (8)

### `diagnose_domain` (~179 tokens)

Diagnose email domain

Audit a domain's SPF, DKIM, DMARC, MX, alignment, BIMI, MTA-STS and TLS-RPT setup and check it against free public blocklists (not Spamhaus) when troubleshooting email authentication or spam delivery. Takes a domain, optional checks and DKIM selectors, and fresh=true to bypass cached results. Returns a graded scorecard, findings, proposed DNS fixes and a public report permalink. Uses DNS and policy-file lookups; never changes DNS or guarantees inbox placement.

Input parameters:

- `checks` (array): Run only these checks (default: all)
- `dkim_selectors` (array): Extra DKIM selectors to probe, e.g. google, s1
- `domain` (string, required): The domain to check, e.g. example.com
- `fresh` (boolean): Bypass caches and re-query DNS

### `analyze_email_headers` (~113 tokens)

Analyze email headers

Analyze raw email headers supplied by the user to investigate authentication or delivery issues. Returns the SPF, DKIM and DMARC results reported in those headers, alignment, the sending IP, whether that IP and the From domain are on free public blocklists (not Spamhaus), and detected issues. It does not independently verify DKIM signatures or establish the receiving provider's exact spam-filter decision. Provide headers only, not the message body.

Input parameters:

- `headers` (string, required): The raw message headers, as copied from "Show original"

### `generate_dns_records` (~168 tokens)

Generate email DNS records

Propose email-authentication DNS records and policy files for a domain using its DNS configuration and optional provider names or IDs. Supports baseline (monitoring) or enforce goals; baseline is the default. Returns typed SPF, DKIM, DMARC, MTA-STS and TLS-RPT proposals or provider setup instructions where applicable. Provider-specific values and reporting addresses may need user input. Uses public DNS/policy lookups, possibly cached. Does not publish records or change DNS.

Input parameters:

- `domain` (string, required): The domain the records are for, e.g. example.com
- `goal` (string): baseline: monitor (p=none); enforce: quarantine/reject
- `providers` (array): Provider ids or names, e.g. google-workspace, sendgrid (default: detected)

### `start_inbox_test` (~118 tokens)

Start inbox test

Create an email-receipt test in MailVakt. Takes an optional expected sender domain; returns a test ID, unique recipient address and expiry time. The user must send a test message to that address before expiry, then use get_inbox_test to read the result. Creates a new test on each call. Does not send email or measure inbox-versus-spam placement at Gmail, Outlook or other mailbox providers.

Input parameters:

- `expected_from_domain` (string): The domain the test email will be sent from, e.g. example.com

### `get_inbox_test` (~109 tokens)

Get inbox test result

Read a MailVakt email-receipt test using the ID returned by start_inbox_test. Returns pending, received or expired status and, when processed, the received message's authentication, unsubscribe, content and deliverability findings. Reports processing failures as errors. Anyone with the test ID can retrieve it; use only an ID supplied by the user or created in this conversation. Does not measure placement at other mailbox providers.

Input parameters:

- `id` (string, required): The id returned by start_inbox_test

### `add_domain` (~104 tokens)

Add domain

Add a domain to the signed-in user's MailVakt account for DMARC report collection. Takes a domain; returns its DMARC reporting (rua) address and account entry. Repeated calls for the same account and domain return the existing entry. Requires domains:write permission. Does not verify domain ownership, modify DNS, or start receiving reports until the user publishes the reporting address in DNS.

Input parameters:

- `domain` (string, required): The domain to add, e.g. example.com

### `list_domains` (~73 tokens)

List domains

List domains in the signed-in user's MailVakt account, including each domain's DMARC reporting address. Takes no input and requires domains:read permission. Returns an empty list if the account has no domains. Use to find the account's available domains before requesting DMARC summaries; does not enumerate domains belonging to other users.

### `get_dmarc_summary` (~147 tokens)

DMARC report summary

Summarize received DMARC aggregate reports for a domain already in the signed-in user's MailVakt account. Takes the domain and a 1-to-90-day window (default 7); returns report and message totals, DMARC pass/fail counts, and per-source SPF/DKIM alignment and receiver actions. Requires domains:read and reports:read permissions. Returns zero totals if no reports were received, or an error if the domain is not in the account. Does not add domains or generate report traffic.

Input parameters:

- `days` (integer): Window in days (default 7)
- `domain` (string, required): One of the user's domains, e.g. example.com

## Diagnostics

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

## Score history

- 2026-10-06: 78
- 2026-10-04: 77
- 2026-10-03: 76
- 2026-10-02: 69

## Common questions

### What is the MailVakt MCP server?

MailVakt is an MCP server listed in the public MCP registry as com.mailvakt/mailvakt. Use when email lands in spam: audits SPF, DKIM, DMARC, MX and returns the DNS records to fix it. This page covers its hosted endpoint (https://mcp.mailvakt.com/mcp).

### Is the MailVakt MCP server safe to use?

MailVakt scores 78 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 MailVakt MCP server expose?

MailVakt exposes 8 tools: diagnose_domain, analyze_email_headers, generate_dns_records, start_inbox_test, get_inbox_test, and 3 more. Their descriptions and schemas cost roughly 1,011 tokens of context every time the server is loaded.

### Does the MailVakt MCP server require authentication?

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

### Is the MailVakt MCP server still maintained?

MailVakt is still listed as active in the MCP registry. We last reached this channel on 6 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://mcp.mailvakt.com/mcp
- Website: https://mailvakt.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-mailvakt-mailvakt/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-mailvakt-mailvakt/mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-mailvakt-mailvakt/mcp