Is this a standalone VS Code extension?

No. MailVakt connects as an MCP server used by GitHub Copilot’s agent tools. Installing the editor alone does not enable it; you need an assistant with MCP access.

Will MailVakt change my DNS or send email as me?

No. Domain checks read public DNS and return findings and suggested fixes. You make any DNS edits yourself. For an inbox test, you send a message to a temporary test address; MailVakt does not send it for you.

Does fixing these records guarantee inbox placement?

No. Authentication is one part of deliverability. Sender reputation, message content and recipient behavior also matter. MailVakt helps you find and address configuration problems.

← All integrations

MailVakt + VS Code

Check email authentication from VS Code

Bring domain diagnostics into your editor’s chat. GitHub Copilot can call MailVakt while you investigate the application sending your emails.

Connect VS Code Try a domain check

Free public checks · No DNS access needed · You stay in control of changes

Inspect your domain

Check live email DNS records, including SPF, DKIM and DMARC, without handing over your DNS login.

Understand the findings

Ask GitHub Copilot in VS Code to explain failures and help prioritize the problems that could affect delivery.

Get a fix you can review

Get proposed record names and values. MailVakt does not edit DNS; you apply approved changes at your provider.

Get connected

Set up MailVakt in VS Code

Use a current VS Code with GitHub Copilot chat and MCP tool access enabled. Workspace trust and organization policy can affect server availability.

Create or open .mcp.json at your workspace root. Merge the mailvakt entry below into the mcpServers object, preserving existing servers. This is the portable configuration supported by current VS Code.
Run MCP: List Servers from the Command Palette and select MailVakt to check its status. Review any trust or sign-in prompts.
Open Copilot chat in an agent mode that can call tools. Enable MailVakt in the tool picker, then ask it to check your sending domain.

.mcp.json

{
  "mcpServers": {
    "mailvakt": {
      "type": "http",
      "url": "https://mcp.mailvakt.com/mcp"
    }
  }
}

Public checks and inbox tests need no MailVakt account. Sign in when prompted to manage domains or read DMARC summaries. Your assistant may ask you to connect an account during setup.

Setup guidance checked October 9, 2026. Official VS Code setup documentation.

Start with a question

Replace example.com with your sending domain, then paste a prompt into GitHub Copilot in VS Code.

Use MailVakt to check example.com and explain the email authentication findings in this chat.

Use MailVakt to investigate why emails from example.com might go to spam. Prioritize SPF, DKIM and DMARC problems.

Use MailVakt to prepare the DNS fixes for example.com, with a short explanation of each record.

Questions

Is this a standalone VS Code extension?: No. MailVakt connects as an MCP server used by GitHub Copilot’s agent tools. Installing the editor alone does not enable it; you need an assistant with MCP access.
Will MailVakt change my DNS or send email as me?: No. Domain checks read public DNS and return findings and suggested fixes. You make any DNS edits yourself. For an inbox test, you send a message to a temporary test address; MailVakt does not send it for you.
Does fixing these records guarantee inbox placement?: No. Authentication is one part of deliverability. Sender reputation, message content and recipient behavior also matter. MailVakt helps you find and address configuration problems.

Use MailVakt with another tool