AgentStack
MCP verified Apache-2.0 Self-run

Claude Plugin

mcp-dnsdoctor-claude-plugin · by dnsdoctor

DNS Doctor plugin for Claude Code — skill + MCP server for email-deliverability diagnosis with validated fix records

No reviews yet
0 installs
0 views
view→install

Install

$ agentstack add mcp-dnsdoctor-claude-plugin

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Claude Plugin? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

DNS Doctor — Claude Code plugin

Diagnose and fix a domain's email authentication (SPF, DMARC, DKIM, MX, blacklist, domain/SSL expiry) from inside Claude. This plugin bundles the DNS Doctor skill (the scan → diagnose → fix workflow) and an MCP server config pointing at the hosted DNS Doctor tools.

The moat: every fix record you get back is generated and validated by a deterministic engine — RFC grammar plus the SPF 10-lookup counter — never an LLM guess. Your agent hands the human a record that already parses correctly, not a plausible-looking string that silently fails.

What's inside

claude-plugin/
├── .claude-plugin/plugin.json   # plugin manifest
├── .mcp.json                    # MCP server: https://dnsdoctor.dev/mcp (HTTP)
├── skills/dns-doctor/SKILL.md   # the scan → diagnose → fix workflow
├── LICENSE                      # Apache-2.0
└── README.md

Tools it adds

| Tool | Does | |---|---| | scan_domain | Fresh scan of a domain; full report. | | get_report | Persisted report (scans once if none exists). | | build_dmarc_upgrade | A validated DMARC enforcement record — p=reject only when the server-derived alignment gate passes. | | enroll_monitoring_trial | Emails a human a double-opt-in link that creates their free account; monitoring starts once they add the domain and verify it with a TXT record. |

The dnsdoctor://domains resource (your monitored domains) is always listed; reading it needs an API token and is refused without one. Anonymous access is enough for a one-off diagnosis.

Install

Claude Code

Add the marketplace/repo and enable the plugin:

/plugin marketplace add dnsdoctor/claude-plugin
/plugin install dns-doctor

> Public home: github.com/dnsdoctor/claude-plugin > (org dnsdoctor, domain-verified). The plugin is developed in the DNS Doctor > monorepo and published here as clean release snapshots.

Or point Claude Code at a local checkout of this directory during development. Once enabled, the skill auto-loads and the dns-doctor MCP server connects to https://dnsdoctor.dev/mcp.

claude.ai (MCP connector)

Add a custom connector with:

  • URL: https://dnsdoctor.dev/mcp
  • Transport: Streamable HTTP
  • Auth: none (anonymous) — or a Bearer token (below)

Optional: API token for monitored domains

Anonymous access covers scanning and fixes. A per-account API token unlocks the dnsdoctor://domains resource (your continuously-monitored domains and their latest per-check statuses).

  1. Sign in at → Settings → API tokens → create a token.

The plaintext (dnsd_…) is shown once; copy it.

  1. Add the Authorization header to the server in .mcp.json:

``json { "mcpServers": { "dns-doctor": { "type": "http", "url": "https://dnsdoctor.dev/mcp", "headers": { "Authorization": "Bearer ${DNSDOCTOR_API_TOKEN}" } } } } ``

Then export DNSDOCTOR_API_TOKEN=dnsd_YOUR_TOKEN in your environment. Never commit the token.

Transport

The hosted streamable-HTTP endpoint (https://dnsdoctor.dev/mcp, wired in this plugin's .mcp.json) is the supported public transport — no install, no keys. (A local stdio entrypoint exists for DNS Doctor maintainers only; its source is not part of this repository.)

Worked example

> You: Our invoices keep landing in customers' spam. Domain is example.com. > > Claude (scan_domainexample.com): DMARC is at p=none, so nothing > enforces alignment — receivers can't tell your mail from a spoof. SPF passes with > 7 of 10 lookups used. DKIM: a selector was found and is valid. Not blacklisted. > Domain expires in 240 days. > > Claude (build_dmarc_upgradeexample.com): SPF is aligned and DKIM is > present, so enforcement to p=reject is safe. Publish this exact TXT record at > _dmarc.example.compaste it verbatim, don't edit it: > > `` > v=DMARC1; p=reject; rua=mailto:dmarc@example.com; adkim=r; aspf=r > `` > > Apply it in your DNS host once you've confirmed it's approved, then ask me to > re-scan to verify. Want the domain watched continuously with aggregate-report > alerts? I can send a setup link to your email.

Learn more

  • Methodology (how the verdicts are computed):
  • REST API / OpenAPI schema:

License

Apache-2.0 — see [LICENSE](./LICENSE).

Source & license

This open-source MCP server is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Versions

  • v0.1.0 Imported from the upstream source.