DNS record lookup — A, AAAA, MX, TXT, CNAME, NS via Cloudflare. x402 micropayment.
MCPpedia last refreshed this data
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"dns-lookup": {
"url": "https://dns-lookup.api.klymax402.com/mcp"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Lookup DNS records (A, AAAA, MX, TXT, CNAME, NS, SOA, SRV) via Cloudflare DNS-over-HTTPS. Fast and reliable. Pay-per-call via x402 (USDC on Base L2) -- no API key, no signup, no rate-limit wall.
No automated test available for this server. Check the GitHub README for setup instructions.
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
No package registry to scan.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in cloud / finance
Let AI agents create, discover, and track tokens across chains via Printr.
Real-time financial market data: stocks, forex, crypto, commodities, and economic indicators
MaverickMCP - Personal Stock Analysis MCP Server
MCP Server for kubernetes management commands
MCP Security Weekly
Get CVE alerts and security updates for io.github.Br0ski777/dns-lookup and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
Lookup DNS records (A, AAAA, MX, TXT, CNAME, NS, SOA, SRV) via Cloudflare DNS-over-HTTPS. Fast and reliable. Pay-per-call via x402 (USDC on Base L2) -- no API key, no signup, no rate-limit wall.
Part of the klymax402 marketplace -- 100 x402 micropayment APIs for AI agents, one wallet, USDC on Base.
Add to your MCP client config (Claude Desktop, Cursor, ElizaOS, etc.):
{
"mcpServers": {
"dns-lookup": {
"url": "https://dns-lookup.api.klymax402.com/mcp"
}
}
}
curl -X POST "https://dns-lookup.api.klymax402.com/api/lookup" \
-H "Content-Type: application/json" \
-d '{"domain":"..."}'
# -> 402 Payment Required, with an x402 payment challenge in the response body
Any x402-aware client (@x402/fetch, x402-agent-tools, ATXP) handles the 402 -> sign -> retry cycle automatically.
| Tool | Method | Path | Price | Description |
|---|---|---|---|---|
network_lookup_dns | POST | /api/lookup | $0.005 | Lookup DNS records for a domain |
network_lookup_dnsUse this when you need to look up DNS records for a domain. Returns all matching records in JSON via Cloudflare DNS-over-HTTPS.
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
domain | string | yes | Domain name to lookup (e.g. example.com) |
type | string | no | DNS record type: A, AAAA, MX, TXT, CNAME, NS, SOA, SRV (default: A) |
Example response:
{"domain":"example.com","type":"A","records":[{"name":"example.com","type":"A","data":"93.184.216.34","ttl":3600}],"queryTime":12,"resolver":"cloudflare"}
When to use: verifying DNS configuration, checking MX records before email setup, auditing TXT records for SPF/DKIM/DMARC, and debugging domain resolution issues.
Not for: SSL certificate check (use security_check_ssl), WHOIS domain info (use domain_lookup_intelligence), HTTP header analysis (use network_analyze_headers).
eip155:8453)100 x402 micropayment APIs for AI agents -- one wallet, USDC on Base, zero signup.
MIT