Security & Testing
dnsape.com
Perform DNS, WHOIS, and HTTP header lookups for domains and URLs.
ENDPOINT 1
https://dnsape.com/mcp
MCP server metadata
- Name
- DNSApe
- Version
- 1.0.0
DNSApe MCP Server provides DNS and network diagnostic tools for AI assistants. Available tools: - dns_lookup: Query DNS records (A, AAAA, MX, TXT, NS, CNAME, SOA) - dns_cache: Check DNS propagation across public resolvers worldwide, with a propagation percentage - dns_history: Get DNS record change history for a tracked domain - whois_lookup: Get WHOIS information for domains and IPs - whois_history: Get WHOIS registration change history (registrar, nameservers, dates) - http_headers: Fetch HTTP headers and analyze security headers - http_headers_history: Get HTTP security-header change history - ssl_check: Check SSL/TLS certificates and expiration - ssl_history: Get SSL certificate change history (rotations, issuer/SAN changes) - tcp_ping: Test connectivity and measure latency - email_security: Validate SPF, DKIM, DMARC, MTA-STS, and TLS-RPT configuration - email_security_history: Get email-authentication change history - blacklist_history: Get DNSBL listing/delisting change history - seo: Score a domain's SEO health (robots.txt, sitemap, meta tags, Open Graph, schema.org) - ai_readiness: Score a domain's readiness for AI agents (llms.txt, MCP, x402, etc.) Pricing: every tool is FREE for the first 6 calls per hour (per client), up to 120 calls/hour total. Beyond the free allowance each call requires a small x402 micropayment in USDC — the price is advertised per tool in tools/list (_meta["x402/price"]) and in the payment-required response. x402-aware MCP clients pay automatically; others can add an x402 payment proxy (see https://x402.org) or use the REST API at https://dnsape.com/.well-known/x402.json. Use these tools to help users diagnose DNS issues, check domain configurations, verify email authentication, troubleshoot network connectivity, audit SEO health, and assess how well sites are prepared for autonomous AI agents.
Known tools 15
dns-cacheCheck DNS propagation by comparing a record across public resolvers worldwide — global anycast networks (Cloudflare, Google, Quad9, OpenDNS, and others) plus genuine regional resolvers in Europe, Russia, China, South Korea, Australia, and Canada.
Inferred read-onlyemail-security-historyGet the email-authentication change history for a domain.
Potential side effectsCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.dnsape]
url = "https://dnsape.com/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"dnsape": {
"type": "http",
"url": "https://dnsape.com/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: dnsape
Remote MCP URL: https://dnsape.com/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"dnsape": {
"url": "https://dnsape.com/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"dnsape": {
"type": "http",
"url": "https://dnsape.com/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "dnsape",
"transport": "streamable-http",
"url": "https://dnsape.com/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Trust Data Available
BuiltWith Trust API v2 evidence for dnsape.com was fetched 2026-07-26T04:38:46.151Z and is being refreshed.
dnsape.com is assessed as Trusted: Domain has an established technology history spanning over a year.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.