_ registry / mcp http-sse · checked 1h ago

mailvakt

https://mcp.mailvakt.com

Registry code: 5ece0e36ad8beb5d

api record

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

from a public catalogue that lists it, not from the operator

endpoint
https://mcp.mailvakt.com/mcp
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is mailvakt live?
Yes — it answered the hub's last check (checked 1h ago). It answered 98% of checks over the last 30 days.
Is mailvakt free to use?
Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.
What tools does mailvakt have?
8 tools: analyze_email_headers, start_inbox_test, add_domain, diagnose_domain, get_dmarc_summary, get_inbox_test, generate_dns_records, list_domains.
Is mailvakt safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
97.6%

90 days 98.6%· all time 98.6%

latency
381ms

last good check

priced tools
0

of 8 tools

_ answered our checks, 90 days 359 checks · signed record
  • down → live
  • degraded → down· timeout after 20000ms
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
used for
  • audit a domain's spf dkim and dmarc
  • generate email authentication dns records
  • analyze email headers
  • summarize dmarc reports
takes → gives
text → data
tools
6 reads2 changes data
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 8 tools
1 auth-required 7 never probed 1 of 8 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • list_domains reads auth-required 6h ago

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "properties": {}
    }
    arguments 5 lines
  • analyze_email_headers reads unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "headers"
      ],
      "properties": {
        "headers": {
          "type": "string",
          "maxLength": 262144,
          "minLength": 1,
          "description": "The raw message headers, as copied from \"Show original\""
        }
      }
    }
    arguments 15 lines
  • start_inbox_test changes data unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "properties": {
        "expected_from_domain": {
          "type": "string",
          "maxLength": 253,
          "minLength": 1,
          "description": "The domain the test email will be sent from, e.g. example.com"
        }
      }
    }
    arguments 12 lines
  • add_domain changes data unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "domain"
      ],
      "properties": {
        "domain": {
          "type": "string",
          "maxLength": 253,
          "minLength": 1,
          "description": "The domain to add, e.g. example.com"
        }
      }
    }
    arguments 15 lines
  • diagnose_domain reads unknown 3h ago

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "domain"
      ],
      "properties": {
        "fresh": {
          "type": "boolean",
          "description": "Bypass caches and re-query DNS"
        },
        "checks": {
          "type": "array",
          "items": {
            "enum": [
              "mx",
              "spf",
              "dkim",
              "dmarc",
              "alignment",
              "bimi",
              "mta-sts",
              "tls-rpt",
              "blocklists"
            ],
            "type": "string"
          },
          "description": "Run only these checks (default: all)"
        },
        "domain": {
          "type": "string",
          "maxLength": 253,
          "minLength": 1,
          "description": "The domain to check, e.g. example.com"
        },
        "dkim_selectors": {
          "type": "array",
          "items": {
            "type": "string",
            "maxLength": 63,
            "minLength": 1
          },
          "maxItems": 20,
          "description": "Extra DKIM selectors to probe, e.g. google, s1"
        }
      }
    }
    arguments 47 lines
  • get_dmarc_summary reads unknown 6h ago

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "domain"
      ],
      "properties": {
        "days": {
          "type": "integer",
          "default": 7,
          "maximum": 90,
          "minimum": 1,
          "description": "Window in days (default 7)"
        },
        "domain": {
          "type": "string",
          "maxLength": 253,
          "minLength": 1,
          "description": "One of the user's domains, e.g. example.com"
        }
      }
    }
    arguments 22 lines
  • get_inbox_test reads unknown 6h ago

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "id"
      ],
      "properties": {
        "id": {
          "type": "string",
          "pattern": "^[a-z2-7]{1,32}$",
          "description": "The id returned by start_inbox_test"
        }
      }
    }
    arguments 14 lines
  • generate_dns_records reads unknown 3h ago

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "domain"
      ],
      "properties": {
        "goal": {
          "enum": [
            "baseline",
            "enforce"
          ],
          "type": "string",
          "description": "baseline: monitor (p=none); enforce: quarantine/reject"
        },
        "domain": {
          "type": "string",
          "maxLength": 253,
          "minLength": 1,
          "description": "The domain the records are for, e.g. example.com"
        },
        "providers": {
          "type": "array",
          "items": {
            "type": "string",
            "maxLength": 64,
            "minLength": 1
          },
          "maxItems": 20,
          "description": "Provider ids or names, e.g. google-workspace, sendgrid (default: detected)"
        }
      }
    }
    arguments 33 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 5ece0e36ad8beb5d.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/5ece0e36ad8beb5d/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/5ece0e36ad8beb5d/badge.svg)](https://brick.blue/agent/5ece0e36ad8beb5d?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.