DNS Super

Check any domain's DNS, WHOIS/RDAP, email setup (SPF, DKIM, DMARC, MTA-STS), SSL certificates and website headers and SEO from your AI agent. 37 tools give compact answers with a plain fix for each problem. Remote HTTP server at https://mcp.dnssuper.com/mcp, authenticated with an API key as a Bearer token; free tier included.

Размещённый MCP-сервер

npx add-mcp 'https://mcp.dnssuper.com/mcp'

Устанавливается в Claude Code, Codex, Cursor и другие

Документация

Domain checks your AI agent can call

Add one server to Claude, Cursor, VS Code or any MCP client, and your agent can check DNS, WHOIS, email, certificates and websites with the same answers you see here.

Server URL

https://mcp.dnssuper.com/mcp

Connect your client

Create an API key in your dashboard first; each snippet sends it as a Bearer token.

Claude Code

Run this once in a terminal with your key in the environment.

Claude Code

claude mcp add --transport http dnssuper https://mcp.dnssuper.com/mcp --header "Authorization: Bearer $DNSSUPER_API_KEY"

Claude Desktop

In claude_desktop_config.json: Settings, Developer, Edit config; restart Claude Desktop after saving. The bridge runs on your machine.

claude_desktop_config.json

{
  "mcpServers": {
    "dnssuper": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.dnssuper.com/mcp",
        "--header",
        "Authorization: Bearer YOUR_API_KEY"
      ]
    }
  }
}

Cursor

In .cursor/mcp.json: In your project, or in ~/.cursor/mcp.json for every project.

.cursor/mcp.json

{
  "mcpServers": {
    "dnssuper": {
      "url": "https://mcp.dnssuper.com/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

VS Code

In .vscode/mcp.json: VS Code asks for the key the first time and keeps it in its secret storage.

.vscode/mcp.json

{
  "inputs": [
    {
      "type": "promptString",
      "id": "dnssuper-key",
      "description": "DNS Super API key",
      "password": true
    }
  ],
  "servers": {
    "dnssuper": {
      "type": "http",
      "url": "https://mcp.dnssuper.com/mcp",
      "headers": {
        "Authorization": "Bearer ${input:dnssuper-key}"
      }
    }
  }
}

Windsurf

In ~/.codeium/windsurf/mcp_config.json: Open it from the MCP settings in Cascade, then refresh the server list.

~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "dnssuper": {
      "serverUrl": "https://mcp.dnssuper.com/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

Other clients

Any client that speaks Streamable HTTP: the server URL plus an Authorization header.

Other clients

{
  "mcpServers": {
    "dnssuper": {
      "type": "http",
      "url": "https://mcp.dnssuper.com/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

Built for agents

  • Compact answers

    A few lines an agent can read and quote: the verdict, the key values and each finding, not a wall of JSON.
  • Full detail when asked

    Pass detail: "full" to get the same structured result the API returns.
  • Prices up front

    Every tool's description says what it costs, so the agent knows before it calls. Each answer ends with the credits used and left.

What your agent gets back

Sample output from our test fixtures, exactly as the MCP tools format it.

Where does example.com send its mail, and is DNSSEC on?

The agent calls lookup_dns (1 credit):

Sample output

example.com resolves to 2 IPv4 addresses and receives mail through 1 MX host.
A: 192.0.2.10, 192.0.2.11 (TTL 300)
MX: 10 mail.example.com (TTL 3600)
DNSSEC: insecure
- info: Your domain isn't signed with DNSSEC
Credits: 1 credit used, 498 remaining | fresh | checked 2026-11-14 10:00 UTC

Is email for example.com set up properly? What should I fix first?

The agent calls audit_email (2 credits):

Sample output

Email for example.com is set up well: grade A, 100 of 100. Mail is handled by Google Workspace.
Score: 100/100
Providers: Google Workspace (MX)
MX: aspmx.l.google.com (1), alt1.aspmx.l.google.com (5)
SPF: v=spf1 include:_spf.google.com ~all (4 of 10 lookups)
DMARC: p=reject, 1 report address
DKIM: google (2048-bit RSA); tried 40 selectors
Policies: MTA-STS enforced, TLS-RPT yes, BIMI no
- info: Your SPF record ends in ~all
- info: No BIMI record
6 checks passed
Credits: 2 credits used, 498 remaining | fresh | checked 2026-11-14 10:00 UTC

Is brightidea.io still available to register?

The agent calls check_availability (1 credit):

Sample output

brightidea.io is available. The .io registry has no record of it; check the price at your registrar before you buy.
brightidea.io: Available (confirmed; the registry has no record)
Checked: dns-parent -> rdap
- info: Check the price before you buy
Credits: 1 credit used, 498 remaining | fresh | checked 2026-11-14 10:00 UTC

Every tool, as an MCP tool

Give your agent a key

A free account comes with monthly credits that work over MCP.

MCP docs

MCP questions

Which clients work?

Any MCP client that speaks Streamable HTTP and can send a header: Claude Code, Claude Desktop, Cursor, VS Code, Windsurf and others.

How does the agent sign in?

With an API key from your dashboard, sent in the Authorization header as a Bearer token. Give each agent its own key so you can revoke one without the others.

What does it cost?

The same credits as the browser and the API; each tool's description tells the agent its price before it calls. The free account's 500 credits a month cover MCP calls too.

What do you keep?

The same as for any API call: a usage entry in your account with the tool, the target and the cost. We never sell lookups, and pasted content such as email headers is never stored.