mcpbeat Sign in

Domain Intelligence API MCP Server

not responding

Domain Intelligence API is listed as active in the registry but did not answer our last check. It exposes 1 tools. Last commit 2 Sep 2026.

WHOIS, DNS records, SSL certificate data for any domain in one call. x402.

Uptime history 51 days of history · worst day 0%
51 days agonow
0.0%
Uptime 24h
0 of 92 checks
1
Tools
read from the server
50 ms
Response time
average over 24h
0
Stars
last commit 2 Sep 2026

What changed 3652

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 8 August 2026. No other catalogue keeps this.

17 Sep a tool description was rewritten71 times that day domain_lookup_intelligence
16 Sep a tool description was rewritten92 times that day domain_lookup_intelligence
15 Sep a tool description was rewritten91 times that day domain_lookup_intelligence
14 Sep a tool description was rewritten91 times that day domain_lookup_intelligence
13 Sep a tool description was rewritten92 times that day domain_lookup_intelligence
12 Sep a tool description was rewritten91 times that day domain_lookup_intelligence
11 Sep a tool description was rewritten90 times that day domain_lookup_intelligence
10 Sep a tool description was rewritten93 times that day domain_lookup_intelligence
9 Sep a tool description was rewritten91 times that day domain_lookup_intelligence
8 Sep a tool description was rewritten91 times that day domain_lookup_intelligence
and 3642 more, back to 8 August 2026

Domain Intelligence API does not always answer

Over the last week it answered 30.0% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 3 min ago.

run in your terminal
claude mcp add domain-intelligence --transport http https://domain-intelligence.api.klymax402.com/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "domain-intelligence": {
      "url": "https://domain-intelligence.api.klymax402.com/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.domain-intelligence]
url = "https://domain-intelligence.api.klymax402.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "domain-intelligence": {
      "url": "https://domain-intelligence.api.klymax402.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "domain-intelligence": {
      "url": "https://domain-intelligence.api.klymax402.com/mcp"
    }
  }
}

Available tools 1

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

domain
domain_lookup_intelligence
Use this when you need comprehensive domain intelligence -- WHOIS, DNS, and SSL data in a single call. Returns structured JSON with full domain profile. POST variant of domain_lookup_intelligence -- same params passed as JSON body instead of query string. 1. whois.registrar (string) -- domain registrar name 2. whois.createdDate (string) -- domain registration date 3. whois.expiryDate (string) -- domain expiration date 4. whois.nameservers (array) -- authoritative nameservers 5. dns.a (array) -- A records (IPv4 addresses) 6. dns.aaaa (array) -- AAAA records (IPv6 addresses) 7. dns.mx (array) -- mail exchange records with priority 8. dns.txt (array) -- TXT records (SPF, verification, etc.) 9. dns.ns (array) -- NS records 10. dns.cname (array) -- CNAME aliases 11. ssl.issuer (string) -- certificate authority (Let's Encrypt, DigiCert, etc.) 12. ssl.validFrom (string) -- certificate start date 13. ssl.validTo (string) -- certificate expiry date 14. ssl.daysRemaining (number) -- days until SSL expiry 15. domainAge (number) -- domain age in days Example output: {"whois":{"registrar":"Cloudflare","createdDate":"2010-01-15","expiryDate":"2027-01-15","nameservers":["ns1.cloudflare.com"]},"dns":{"a":["104.26.10.1"],"mx":[{"priority":10,"exchange":"mx.example.com"}]},"ssl":{"issuer":"Let's Encrypt","daysRemaining":45},"domainAge":5932} Use this BEFORE domain purchases, security audits, phishing investigations, or due diligence on vendors. Essential for checking domain legitimacy, SSL health, and DNS configuration. Do NOT use for company data -- use company_enrich_from_domain instead. Do NOT use for IP geolocation -- use ip_lookup_geolocation instead. Do NOT use for website content -- use web_scrape_to_markdown instead. Do NOT use for email deliverability -- use email_audit_deliverability instead.

Endpoints

URLTransportStateLatencyChecked
https://domain-intelligence.api.klymax402.com/mcp sse answering 50 ms 3 min ago

Alternatives to Domain Intelligence API

same job, measured the same way
Domainintel MCP
by bishop81

Domain intelligence for agents: WHOIS, DNS, SSL/TLS, security headers, reputation, subdomains.

38 installs/wk local only
Bassethound
by bassethound

Company intelligence for AI agents: a five-layer domain dossier in one sniff_domain call.

answering
Whois MCP
by mrfentmen

RDAP whois records for domains and IPs.

local only
DomScan
by estevecastells

Domain intelligence for DNS, WHOIS/RDAP, TLS, reputation, valuation, and brand protection.

answering
A
CryptoPulse Data API
by saascloud

Pay-per-call crypto market intelligence for AI agents. USDC on Base via x402.

11 tools answering
Porkbun DNS 🐷
by major

Manage DNS records, domains, DNSSEC, SSL certificates via MCP

186 installs/wk local only
Dnstwister MCP
by mrfentmen

DNS twister domain threat intelligence: fuzz domains for typosquatting, check whois.

local only
Agent Newsstand
by agentnewsstand

Market data and web intelligence for AI agents, paid per call in USDC on Base via x402.

16 tools answering

Domain Intelligence API — questions

Answers built from our own checks of this server.

What can Domain Intelligence API do?
It exposes 1 tools, read directly from the server on our last check. Among them: domain_lookup_intelligence. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Domain Intelligence API working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 0 of 92 checks got a reply (0.0%), average response time 50 ms. The bar chart above shows every period we have measured.
The registry lists Domain Intelligence API as active — why does it not respond?
The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.
How do I connect Domain Intelligence API?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Domain Intelligence API need an API key?
No. Domain Intelligence API completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 1 of them are readable on this page. This is what we observed, not what the docs claim.
Is Domain Intelligence API open source?
Yes — it is published under the MIT licence, written in TypeScript, 0 stars on GitHub and 1 open issue. The source link is on this page, so you can read exactly what it does with your data before you connect it.