@dnsdoctor/mcp 1.7.1 → 1.7.3

package/README.md

@@ -180,7 +180,8 @@ client has no tools and none of its safety guidance.
 >
 > 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.
+> alerts? Here is the setup link — open it and sign in:
+> https://dnsdoctor.dev/start?domain=example.com&ref=agent
 
 ## Learn more
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@dnsdoctor/mcp",
-  "version": "1.7.1",
+  "version": "1.7.3",
   "mcpName": "dev.dnsdoctor/dns-doctor",
   "description": "Thin stdio MCP server for DNS Doctor \u2014 scan, fix and verify a domain's DNS: SPF, DMARC, DKIM, multi-region propagation, MX, DNS health, blacklists and expiry, over the public DNS Doctor REST API.",
   "license": "Apache-2.0",

package/tools.json

@@ -127,7 +127,7 @@
       "openWorldHint": true,
       "readOnlyHint": true
     },
-    "description": "Check whether a DNS change has propagated GLOBALLY: six vantage points (five owner-run probes on separate continents plus this server's own resolver) each read the same name through several resolvers, and the grid plus a deterministic verdict comes back. Call it after the human publishes a record \u2014 you have ONE network vantage point, and a record that resolves for you can still be missing elsewhere. `name` is the exact name (www. is not stripped, _dmarc.example.com works), `record_type` is A|AAAA|CNAME|MX|TXT|NS, and the optional `expected_value` turns each cell into match or mismatch instead of agreement-only. Observation only: no record is ever composed here. A cell that did not answer is `unavailable`, which is NOT a negative result, and when fewer than three vantage points were reached the verdict downgrades to `unknown` \u2014 report vantage_reached of vantage_total rather than calling a name converged on partial coverage.",
+    "description": "Check whether a DNS change has propagated GLOBALLY: six vantage points (five owner-run probes across four continents plus this server's own resolver) each read the same name through several resolvers, and the grid plus a deterministic verdict comes back. Call it after the human publishes a record \u2014 you have ONE network vantage point, and a record that resolves for you can still be missing elsewhere. `name` is the exact name (www. is not stripped, _dmarc.example.com works), `record_type` is A|AAAA|CNAME|MX|TXT|NS, and the optional `expected_value` turns each cell into match or mismatch instead of agreement-only. Observation only: no record is ever composed here. A cell that did not answer is `unavailable`, which is NOT a negative result, and when fewer than three vantage points were reached the verdict downgrades to `unknown` \u2014 report vantage_reached of vantage_total rather than calling a name converged on partial coverage.",
     "inputSchema": {
       "properties": {
         "expected_value": {