MailVakt
REMOTE · MCP.MAILVAKT.COM · SCANNED OCT 4
Use when email lands in spam: audits SPF, DKIM, DMARC, MX and returns the DNS records to fix it.
Available components
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. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability88
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1007 tokens (~111/item across 9 items; 8 tools + 1 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
- Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
- Supports UI / widget rendering.Pass
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.
remote · mcp.mailvakt.com
claude mcp add --transport http com-mailvakt-mailvakt 'https://mcp.mailvakt.com/mcp'
{
"mcpServers": {
"com-mailvakt-mailvakt": {
"url": "https://mcp.mailvakt.com/mcp"
}
}
} {
"servers": {
"com-mailvakt-mailvakt": {
"type": "http",
"url": "https://mcp.mailvakt.com/mcp"
}
}
} [mcp_servers.com-mailvakt-mailvakt] url = "https://mcp.mailvakt.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-mailvakt-mailvakt": {
"type": "remote",
"url": "https://mcp.mailvakt.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-mailvakt-mailvakt --url 'https://mcp.mailvakt.com/mcp' --transport streamable-http
mcp_servers:
com-mailvakt-mailvakt:
url: "https://mcp.mailvakt.com/mcp" {
"McpServers": {
"com-mailvakt-mailvakt": {
"Transport": "http",
"Url": "https://mcp.mailvakt.com/mcp"
}
}
} assistant mcp add com-mailvakt-mailvakt -t streamable-http -u 'https://mcp.mailvakt.com/mcp'
{
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Oct 26 +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.
- 3 Oct 26 +7
- HTTPS: unverified → pass ▲ security
- HSTS header: fail → pass ▲ security
- Stability: unverified → 0.03 ▲ functional
- 2 Oct 26 69
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Oct 2026 · Probed https://mcp.mailvakt.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mailvakt.com | CN=WE1,O=Google Trust Services,C=US | 2 Oct 2026 | 31 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | ec001237891ca9550ec5b9dc92f9a2de |
| SANs: mailvakt.com, mcp.mailvakt.com, *.mcp.mailvakt.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.mailvakt.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| mailvakt.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.mailvakt.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.mailvakt.com/mcp | HTTPS enforced | 301 | https://mcp.mailvakt.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
add_domain Add domain ~104
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.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | The domain to add, e.g. example.com |
No output schema declared.
No examples provided.
analyze_email_headers Analyze email headers ~105
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, sending IP and detected issues. Parses the supplied text without external DNS or HTTP lookups; it does not independently verify DKIM signatures or establish the receiving provider's exact spam-filter decision. Provide headers only, not the message body.
| Name | Type | Req | Description |
|---|---|---|---|
| headers | string | yes | The raw message headers, as copied from "Show original" |
No output schema declared.
No examples provided.
diagnose_domain Diagnose email domain ~166
Audit a domain's SPF, DKIM, DMARC, MX, alignment, BIMI, MTA-STS and TLS-RPT configuration 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.
| Name | Type | Req | Description |
|---|---|---|---|
| checks | array | – | Run only these checks (default: all) |
| dkim_selectors | array | – | Extra DKIM selectors to probe, e.g. google, s1 |
| domain | string | yes | The domain to check, e.g. example.com |
| fresh | boolean | – | Bypass caches and re-query DNS |
No output schema declared.
No examples provided.
generate_dns_records Generate email DNS records ~168
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.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | 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) |
No output schema declared.
No examples provided.
get_dmarc_summary DMARC report summary ~147
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.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | Window in days (default 7) |
| domain | string | yes | One of the user's domains, e.g. example.com |
No output schema declared.
No examples provided.
get_inbox_test Get inbox test result ~109
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The id returned by start_inbox_test |
No output schema declared.
No examples provided.
list_domains List domains ~73
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
start_inbox_test Start inbox test ~118
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.
| Name | Type | Req | Description |
|---|---|---|---|
| expected_from_domain | string | – | The domain the test email will be sent from, e.g. example.com |
No output schema declared.
No examples provided.
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 77 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 990 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 4 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.