dns-doctor
dns-doctor is an MCP server published by dnsdoctor.dev, verified on MCP revision 2025-11-25; support for the current revision (2026-07-28) is not yet confirmed. Last verified 2026-08-25.
Does dns-doctor support the current MCP specification (2026-07-28)?
Not yet confirmed. dns-doctor is verified on revision 2025-11-25; we have not confirmed support for the current revision (2026-07-28) as of 2026-08-25.
Is dns-doctor a first-party (official) MCP server?
Undetermined. We have not verified the publisher relationship for dns-doctor (as of 2026-08-25).
How do I connect to dns-doctor?
dns-doctor is available via a hosted remote endpoint at https://dnsdoctor.dev/mcp, the package npm:@dnsdoctor/mcp, the official MCP Registry under dev.dnsdoctor/dns-doctor, the source repository at https://github.com/dnsdoctor/claude-plugin. Authentication: none. Transports: streamable-http.
What tools does dns-doctor expose?
dns-doctor exposes 15 tools, including scan_domain, get_report, build_dmarc_upgrade, start_monitoring_signup, count_spf_lookups, validate_dmarc_record (last verified 2026-08-25).
Does dns-doctor support MCP revision 2025-11-25?
Yes. dns-doctor supports MCP revision 2025-11-25 (checked 2026-08-25).
When were dns-doctor's facts last verified?
2026-08-25. Each fact on this page links to the sources used to verify it.
Which tools does dns-doctor expose?
15 tools verified.
scan_domainget_reportbuild_dmarc_upgradestart_monitoring_signupcount_spf_lookupsvalidate_dmarc_recordgenerate_dmarc_recordcheck_dkim_selector
Scan and fix email auth (SPF, DMARC, DKIM, MX, blacklists, expiry) + DNS checks. Validated fixes.
Which MCP spec revisions does dns-doctor support?
dns-doctor has 1 verified spec-support record. Each row lists the revision, the verified status, the evidence URL, and the date that fact was last checked.
| Spec revision | Status | Last checked | Evidence |
|---|---|---|---|
| MCP 2025-11-25 | Supported | Source |
How widely adopted is dns-doctor?
Not ranked in The MCP 500: insufficient public data (coverage floor not met) (snapshot ). The Adoption Index measures public signals only; it says nothing about quality.
Repository and package signals for dns-doctor
Measured directly from the source registries, not asserted from a document. Each figure carries the date it was read; none of it affects the verified spec status above.
Repository as of
- Stars
- 2
- Forks
- 0
- Last pushed
- (59 days ago)
- Created
- Open issues
- 0
- Primary language
- TypeScript
- License (repository)
- Apache-2.0
- Continuous integration
- Present
- Tests
- Present
- Security policy
- None
Declared topics: claude, dkim, dmarc, email-security, mcp, spf — author-declared on the repository, not our taxonomy.
Package (npm) as of
- Latest version
1.4.0- Last published
- First published
- Releases
- 4
- License (package)
- Apache-2.0
- Maintainers
- 1
- Direct dependencies
- 1
- Unpacked size
- 84 KB
- Registry signature
- Signed
- Build provenance
- No attestation
How was this verified, and what are the sources?
Verified · method: endpoint-probe
· confidence 0.85 (Good).
- Official MCP Registry record for dev.dnsdoctor/dns-doctor at version 1.4.0 - lists remote endpoint https://dnsdoctor.dev/mcp and repository https://github.com/dnsdoctor/claude-plugin - accessed
- Endpoint probe of https://dnsdoctor.dev/mcp - declined server/discover; negotiated 2025-11-25 via the legacy initialize handshake; tools/list returned 15 tools - accessed
- Endpoint probe of https://dnsdoctor.dev/mcp - declined server/discover; negotiated 2025-11-25 via the legacy initialize handshake; tools/list returned 15 tools - accessed