Starts a free 48-hour watch on one DNS record, rechecking every 10 minutes and emailing when the change goes live or the expected value fails to appear.
Apache 2.0
776,791 tools. Updated 2026-11-13 14:38
"DNS Doctor" matching MCP tools:
- Add a domain to DNS Doctor monitoring and receive the exact ownership-check TXT record to publish, plus its DNS host, a provider-specific guide, and an apply link when supported.Apache 2.0
- Check whether a domain's DNS Doctor ownership TXT challenge is published, then mark the domain verified when the record is visible. Use only for domains already added to the account.Apache 2.0
- Lists every domain monitored by your DNS Doctor account, showing whether each is verified, pending, or verification-lapsed and the next action needed.Apache 2.0
- Add a domain to DNS Doctor monitoring and get the ownership-check TXT record to publish, plus DNS host details and provider-specific setup guidance.Apache 2.0
- Check whether a monitored domain's DNS Doctor ownership TXT record is published yet and mark the domain verified when found. Reports which nameservers were queried so pending, wrong-value, and transient lookup failures stay distinct.Apache 2.0
Matching MCP Servers
- AlicenseAqualityBmaintenanceDiagnoses a domain's email authentication — SPF, DMARC, DKIM, MX, blacklists and domain or SSL expiry - and returns copy-paste fix records generated by a validating engine, never a language model. The MCP server is hosted remotely; this repository carries the plugin manifest, connector config and bundled skill.27765 npm3Apache 2.0
DNS Doctorofficial
AlicenseAqualityBmaintenanceChecks and fixes a domain's email authentication (SPF, DKIM, DMARC), DNS health, propagation, blacklists and domain/SSL expiry, returning copy-paste fix records from a validating engine, never a model guess. Local stdio server (npx -y @dnsdoctor/mcp) with the same 27 tools as the hosted https://dnsdoctor.dev/mcp.29765 npmApache 2.0
Matching MCP Connectors
Scan, fix, verify and monitor DNS: SPF, DMARC, DKIM, propagation, health, expiry. Validated fixes.
DNS MCP — DNS and network lookup tools
- Use this when a signed-in operator asks which domains their DNS Doctor account monitors, or what to do next on them. Lists every domain on the caller's account with its state — verified, pending (added, ownership not proven yet) or…Apache 2.0
- Use this when a signed-in operator asks which domains their DNS Doctor account monitors, or what to do next on them. Lists every domain on the caller's account with its state — verified, pending (added, ownership not proven yet) or verification_lapsed (the ownership record was removed, so monitoring is paused for it) — and next_step, the one thing to do next for that domain. Needs a connected DNS Doctor account or an API token. Relay next_step as given.ConnectorNo auth
- Use this when the user asks to be told when a DNS change they are making has finished ("let me know when it's live"). Starts a free watch on ONE record for the signed-in user: DNS Doctor rechecks it every 10 minutes for up to 48 hours with the same verdict as check_record and sends ONE email to the address on their DNS Doctor account: when it is live, when the value has sat at a different name for an hour, when the zone has not served it for 6 hours, or when 48 hours pass. Same arguments as check_record; pass expected_value when the user is publishing a specific value. It reads the record once first and returns that reading: a record that is already live (verdict done), a domain whose nameservers do not answer, or a lookup fault starts nothing. Asking again for the same record returns the running watch, never a second one. Relay `watch.note`. Needs a linked DNS Doctor account; never ask the user for an email address. Nothing is applied to anyone's DNS.ConnectorNo auth
- Connects a generic DNS provider to a domain using provider-specific credentials, enabling DNS-based domain verification and configuration.MITDestructive
- Retrieve metadata for supported DNS providers, including required credential fields and documentation links, to configure DNS verification in Proof.MIT
- Store DNS provider credentials to enable automated domain verification through the Proof API.MITDestructive
- Starts a DNS or HTTP check to verify control of a pending domain after Proof API access is configured.MIT
- Connect a Cloudflare API token with DNS edit permissions to a domain to manage DNS records automatically.MITDestructive
- Read the shopper's local Portage setup, including doctor findings, spending policy, payment methods, and browser profile. Call at session start or after failures to diagnose gaps.MIT
- Protect parked domains from email spoofing by generating Null MX, hard-fail SPF, and reject-policy DMARC records. Use only after the owner confirms the domain sends no email.Apache 2.0
- Validate an SPF record and count its DNS lookups against the 10-lookup limit. Flags over-limit and near-limit records with the offending mechanisms causing SPF PermError.Apache 2.0
- Check whether a monitored domain is ready to advance DMARC enforcement from its aggregate report window; get the verdict, blockers, and validated next-step record when ready.Apache 2.0
- Run a fresh, full DNS and email-authentication report for a real domain, covering SPF, DKIM, DMARC, MX, DNS hardening, expiry, blacklists, and generated fix records.Apache 2.0
- Retrieve DNS records (A, CNAME, MX, TXT) for a domain to inspect current entries. Use after listing domains to get record details.MIT
- Fetch current DNS records for a domain via Cloudflare DNS over HTTPS. Specify record types like A, MX, or TXT to get live resolution data for the domain.Business Source 1.1