dns-check

Live DNS lookups for agents: A/MX/TXT/SPF/CNAME/PTR with TTLs and DNSSEC, via Google Public DNS.

我該用這個嗎

品質與安全性

A
說明品質
100%
結構描述完整度
100%
命名品質
80%
汙染風險
100%
權限相符程度
100%
協定合規性
100%

根據工具定義與協定合規性的自動化分析。

上下文成本

~320Token(工具定義)
~1.5 KB典型回應大小
極小的注意力影響(128k 上下文的 0.25%)

這是每次將伺服器的工具載入模型上下文時所消耗的約略 token 數量。數量越高,可用於其他工作的注意力就越少。

安裝

一鍵安裝

將以下內容加入你的 `claude_desktop_config.json` 檔案:

{
  "mcpServers": {
    "dns-check": {
      "url": "https://api.kaiv.ai/api/bridge/mcp/dns-check-e159a722"
    }
  }
}

遠端端點

https://api.kaiv.ai/api/bridge/mcp/dns-check-e159a722streamable-http

它能做什麼

工具清單

工具(1)

🟢 唯讀🟡 寫入🔴 刪除⚪ 未知
🟢resolve_dns(do, name, type)

Resolve any DNS record live via Google Public DNS. Answers: is DNS propagated? What are the MX/TXT/SPF/DKIM records? Where does this CNAME point? For reverse lookup pass name=<reversed-ip>.in-addr.arpa with type=PTR (e.g. 90.57.149.3.in-addr.arpa for 3.149.57.90). Returns Status (0 = NOERROR, 3 = NXDOMAIN), Answer records with TTLs, and the AD flag for DNSSEC validation.

輸入結構描述

{
  "type": "object",
  "properties": {
    "do": {
      "type": "string",
      "x-in": "query",
      "description": "Set 'true' to include DNSSEC records (RRSIG) in the response"
    },
    "name": {
      "type": "string",
      "x-in": "query",
      "description": "Domain name to resolve, e.g. 'kaiv.ai' (or reversed IP + .in-addr.arpa for PTR)"
    },
    "type": {
      "enum": [
        "A",
        "AAAA",
        "MX",
        "TXT",
        "NS",
        "CNAME",
        "SOA",
        "CAA",
        "PTR",
        "SRV"
      ],
      "type": "string",
      "x-in": "query",
      "default": "A",
      "description": "Record type: A, AAAA, MX, TXT, NS, CNAME, SOA, CAA, PTR, SRV. Default A."
    }
  },
  "required": [
    "name"
  ]
}

社群

為此伺服器評分

證據

近期觀測

已驗證未記錄版本1 個工具
已驗證未記錄版本1 個工具