Deliverability Doctor MCP

A stateless, authless MCP server that checks SPF, DKIM, DMARC, and MX records via public DNS to grade email security and detect spoofing risks for domains.

Endpoint and access

No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.

Community listingStreamable HTTPNo sign-inEndpoint checked 2026-11-06Published by Kacper Konieczny

MCP endpoint (Streamable HTTP)

https://deliverability-doctor.deliverability-doctor.workers.dev/mcp

Vendor documentation

What its tools do

2 tools, grouped by the hints the server advertises. Hints are self-declared, not verified behavior.

2 of 2 have a description · 0 of 2 declare behavior hints · 2 of 2 with parameters document them all

Checks and signals

Each line is separate evidence, not a trust score.

Passed Endpoint answered the live check · Nov 6, 2026, 3:19 PM UTC
Availability 1 of 1 checks passed in 30 days

What you can do with it

Check email security for a single domain
Compare email security for 2-5 domains side by side
Verify SPF, DKIM, and DMARC configurations

Source and maintenance

Community listingRegistry 1.0.2

mcp-registry: io.github.Integrity-Os/deliverability-doctor@1.0.2 Source repository

Maintenance checked: Nov 6, 2026, 3:14 PM UTC

Protocol and capabilities

Server: deliverability-doctor 1.0.0
MCP protocol negotiated in check: 2025-11-25
Tools: 2 advertised
Resources: Not advertised
Resource templates: Not advertised
Prompts: Not advertised

Server-advertised capabilities

{
  "tools": {}
}

Tools

2 advertised

check_email_security — Check a domain’s email security

Advertised by the server during the last successful anonymous check.

Checks whether a domain can be email-spoofed, using public DNS only. Verifies SPF (including the RFC 7208 multiple-record permerror), DMARC policy and reporting, MX, and DKIM at common selectors. Returns a graded report with concrete fixes. Accepts a bare domain, a URL, or an email address. Nothing is sent to the domain.

check_email_security input schema

{
  "type": "object",
  "required": [
    "domain"
  ],
  "properties": {
    "domain": {
      "type": "string",
      "description": "Domain, URL, or email address, e.g. example.com"
    }
  }
}

compare_email_security — Compare email security across domains

Advertised by the server during the last successful anonymous check.

Runs the email-security check on 2–5 domains and returns a comparison table with per-domain grades. Useful for checking your domain against competitors.

compare_email_security input schema

{
  "type": "object",
  "required": [
    "domains"
  ],
  "properties": {
    "domains": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "maxItems": 5,
      "minItems": 2,
      "description": "2–5 domains"
    }
  }
}

Prompts

Not advertised

No prompt definitions available.

Resources

Not advertised

No resource definitions available.

90-day uptime

A lightweight connection check about every six hours, sampled on hosts with many listings. It shows the server answered, not that its tools work.

Too few checks for a percentage yet (2 of 2 answered).

2026-11-06: 1 of 1 checks answered
2026-11-07: 1 of 1 checks answered

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks: 1 of 1 (100%)
Average latency: 212 ms
95th percentile latency: 212 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

Nov 6, 2026, 3:19 PM UTC · probe · passed · 212 ms · metadata changed · 2 tool(s)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.

Claude Code configuration

claude mcp add --transport http deliverability-doctor-mcp https://deliverability-doctor.deliverability-doctor.workers.dev/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).

Codex configuration

codex mcp add deliverability-doctor-mcp --url https://deliverability-doctor.deliverability-doctor.workers.dev/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable deliverability-doctor-mcp in your MCP settings.

Cursor configuration

{
  "mcpServers": {
    "deliverability-doctor-mcp": {
      "url": "https://deliverability-doctor.deliverability-doctor.workers.dev/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).

Cline configuration

{
  "mcpServers": {
    "deliverability-doctor-mcp": {
      "type": "streamableHttp",
      "url": "https://deliverability-doctor.deliverability-doctor.workers.dev/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start deliverability-doctor-mcp and inspect its tools.

VS Code configuration

{
  "servers": {
    "deliverability-doctor-mcp": {
      "type": "http",
      "url": "https://deliverability-doctor.deliverability-doctor.workers.dev/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.

Gemini CLI configuration

gemini mcp add --transport http deliverability-doctor-mcp https://deliverability-doctor.deliverability-doctor.workers.dev/mcp

Claude Desktop

Open Claude Settings > Connectors > Add custom connector, enter this server URL and enable it for the conversation. This is a manual remote-connector handoff, not a desktop JSON configuration.

Claude Desktop configuration

https://deliverability-doctor.deliverability-doctor.workers.dev/mcp

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.

Windsurf configuration

{
  "mcpServers": {
    "deliverability-doctor-mcp": {
      "serverUrl": "https://deliverability-doctor.deliverability-doctor.workers.dev/mcp"
    }
  }
}

Let your agent find its tools

Find servers like Deliverability Doctor MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.

Connect Koskamo Explore workflows

See all 8,355