About Dns Lookup X402
Dns Lookup X402 looks up domain DNS records and returns multiple record types through Cloudflare DNS-over-HTTPS. It is aimed at AI agents, uses x402 pay-per-call, and provides an MCP interface.
Key features
- 01Look up eight DNS record types
- 02Query through Cloudflare DNS-over-HTTPS
- 03Return records as JSON
- 04x402 pay-per-call
Use cases
- 01Verify domain DNS configuration
- 02Check MX records before email setup
- 03Review SPF, DKIM, and DMARC TXT records
- 04Debug domain resolution issues
MCP support
Provides the network_lookup_dns tool over MCP, accepting a domain and optional record type and returning DNS records.
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://dns-lookup.api.klymax402.com/mcpclaude mcp add --transport sse dns-lookup-x402 https://dns-lookup.api.klymax402.com/mcp{"mcpServers":{"dns-lookup-x402":{"type":"sse","url":"https://dns-lookup.api.klymax402.com/mcp"}}}Open in Cursor{"servers":{"dns-lookup-x402":{"type":"sse","url":"https://dns-lookup.api.klymax402.com/mcp"}}}Open in VS Code{"mcpServers":{"dns-lookup-x402":{"type":"sse","url":"https://dns-lookup.api.klymax402.com/mcp"}}}{"mcpServers":{"dns-lookup-x402":{"serverUrl":"https://dns-lookup.api.klymax402.com/mcp"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
Tools
Details
From the project READMEDNS Lookup API
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.
Quickstart -- MCP
Add to your MCP client config (Claude Desktop, Cursor, ElizaOS, etc.):
{
"mcpServers": {
"dns-lookup": {
"url": "https://dns-lookup.api.klymax402.com/mcp"
}
}
}
Quickstart -- HTTP (x402)
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.
Tools
| Tool | Method | Path | Price | Description |
|---|---|---|---|---|
network_lookup_dns | POST | /api/lookup | $0.005 | Lookup DNS records for a domain |
network_lookup_dns
Use 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).
Example agent prompts
- "Look up DNS records for a domain"
Payment
- Protocol: x402 -- HTTP-native pay-per-call, no signup, no API key
- Network: Base L2 (
eip155:8453) - Asset: USDC
- Facilitator: Coinbase CDP (primary), PayAI (fallback)
- Also reachable via ATXP (OAuth-wrapped x402, RFC 9728 protected-resource metadata)
Part of klymax402
100 x402 micropayment APIs for AI agents -- one wallet, USDC on Base, zero signup.
- Catalog: https://klymax402.com/llms.txt
- Full API reference: https://klymax402.com/llms-full.txt
- Live stats: https://klymax402.com/stats
License
MIT
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.