@dnsdoctor/mcp 1.16.0 → 1.16.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +2 -2
- package/package.json +1 -1
- package/tools.json +2 -2
package/README.md
CHANGED
|
@@ -134,7 +134,7 @@ Two supported public transports, same 27 tools:
|
|
|
134
134
|
|
|
135
135
|
- **Hosted streamable HTTP** — `https://dnsdoctor.dev/mcp`, wired in this
|
|
136
136
|
plugin's `.mcp.json`. No install, no keys.
|
|
137
|
-
- **Local stdio** — `npx -y @dnsdoctor/mcp@1.16.
|
|
137
|
+
- **Local stdio** — `npx -y @dnsdoctor/mcp@1.16.1`. A thin server that runs on your
|
|
138
138
|
machine and calls the public DNS Doctor REST API; it holds no diagnosis logic
|
|
139
139
|
of its own and relays every record string verbatim.
|
|
140
140
|
|
|
@@ -143,7 +143,7 @@ Two supported public transports, same 27 tools:
|
|
|
143
143
|
"mcpServers": {
|
|
144
144
|
"dns-doctor": {
|
|
145
145
|
"command": "npx",
|
|
146
|
-
"args": ["-y", "@dnsdoctor/mcp@1.16.
|
|
146
|
+
"args": ["-y", "@dnsdoctor/mcp@1.16.1"],
|
|
147
147
|
"env": { "DNSDOCTOR_API_TOKEN": "dnsd_YOUR_TOKEN" }
|
|
148
148
|
}
|
|
149
149
|
}
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@dnsdoctor/mcp",
|
|
3
|
-
"version": "1.16.
|
|
3
|
+
"version": "1.16.1",
|
|
4
4
|
"mcpName": "dev.dnsdoctor/dns-doctor",
|
|
5
5
|
"description": "Thin stdio MCP server for DNS Doctor — 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.",
|
|
6
6
|
"license": "Apache-2.0",
|
package/tools.json
CHANGED
|
@@ -525,7 +525,7 @@
|
|
|
525
525
|
"readOnlyHint": true,
|
|
526
526
|
"title": "Get Monitoring Alerts"
|
|
527
527
|
},
|
|
528
|
-
"description": "Use this when a signed-in operator asks what changed on a monitored domain, or what the monitoring has flagged. Read the monitoring alert log for the domains the caller's account monitors, newest first. Requires an API token. Each row carries id, domain, type, check, summary, a deterministic detail map, created_at, email_sent_at, acknowledged_at and delivery_class \u2014 a 'dashboard_only' row was deliberately kept out of the digest mail, so an agent watching only the inbox would never see it; this log is the complete picture. PAGE DOWN BEFORE ADVANCING `since`: next_before is non-null exactly when older rows remain, and a caller that ignores it, takes a full page and moves its watermark to the newest row it saw drops every row it did not receive. `since` is an INCLUSIVE floor, so rows repeat rather than go missing \u2014 de-duplicate on id. READ-ONLY by decision: there is no ack and no delete here, because acknowledging an alert is the human's own triage on their dashboard and an agent that acks on their behalf silences a row they have never seen. Report what the log says and let them clear it.",
|
|
528
|
+
"description": "Use this when a signed-in operator asks what changed on a monitored domain, whether its website went down, or what the monitoring has flagged. Read the monitoring alert log for the domains the caller's account monitors, newest first, including website uptime incidents (site_down, site_partial, site_recovered, and site_blocked when the site's protection refuses our checks). Requires an API token. Each row carries id, domain, type, check, summary, a deterministic detail map, created_at, email_sent_at, acknowledged_at and delivery_class \u2014 a 'dashboard_only' row was deliberately kept out of the digest mail, so an agent watching only the inbox would never see it; this log is the complete picture. PAGE DOWN BEFORE ADVANCING `since`: next_before is non-null exactly when older rows remain, and a caller that ignores it, takes a full page and moves its watermark to the newest row it saw drops every row it did not receive. `since` is an INCLUSIVE floor, so rows repeat rather than go missing \u2014 de-duplicate on id. READ-ONLY by decision: there is no ack and no delete here, because acknowledging an alert is the human's own triage on their dashboard and an agent that acks on their behalf silences a row they have never seen. Report what the log says and let them clear it.",
|
|
529
529
|
"inputSchema": {
|
|
530
530
|
"properties": {
|
|
531
531
|
"before": {
|
|
@@ -949,7 +949,7 @@
|
|
|
949
949
|
"readOnlyHint": true,
|
|
950
950
|
"title": "Get Monitoring Signup Link"
|
|
951
951
|
},
|
|
952
|
-
"description": "Use this when the user asks for ongoing DMARC monitoring, RUA report monitoring, new-sender monitoring, email-authentication alerts
|
|
952
|
+
"description": "Use this when the user asks for ongoing DMARC monitoring, RUA report monitoring, new-sender monitoring, email-authentication alerts, ongoing DNS monitoring, or website uptime monitoring and down alerts for a domain they own (a verified domain's website is checked from five locations on four continents, with an email when it goes down); not for a one-off question about whether a site is down right now. Returns signup_url, a link to a dnsdoctor.dev page that explains monitoring and where the domain owner signs in themselves, and a short message. This call creates nothing and sends no email; the domain is filled in on their dashboard after they sign in, and monitoring starts once they prove ownership with a DNS record. Show the user the signup_url as a link together with the message.",
|
|
953
953
|
"inputSchema": {
|
|
954
954
|
"properties": {
|
|
955
955
|
"domain": {
|