MCP Server for Domain, DNS, SSL & WHOIS Lookups

Add it to your client

Claude Code

Run this once in a terminal. Add --scope user to make it available in every project.

shell

claude mcp add --transport http orbitprobe https://www.orbitprobe.com/api/mcp

Claude Desktop and claude.ai

Open Settings → Connectors → Add custom connector, give it a name and paste the URL below. Leave the OAuth fields empty. Whether custom connectors are available depends on your Claude plan.

URL

https://www.orbitprobe.com/api/mcp

If your version only reads claude_desktop_config.json, the third-party mcp-remote package (not made by OrbitProbe; needs Node.js) can bridge a local entry to the remote URL:

claude_desktop_config.json

{
  "mcpServers": {
    "orbitprobe": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://www.orbitprobe.com/api/mcp"
      ]
    }
  }
}

Cursor, VS Code and other clients

Any client that speaks Streamable HTTP can use the URL directly. Cursor reads .cursor/mcp.json, VS Code reads .vscode/mcp.json:

.cursor/mcp.json

{
  "mcpServers": {
    "orbitprobe": {
      "url": "https://www.orbitprobe.com/api/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "orbitprobe": {
      "type": "http",
      "url": "https://www.orbitprobe.com/api/mcp"
    }
  }
}

Try it with curl

Three requests: handshake, list of tools, one call.

shell

curl -s https://www.orbitprobe.com/api/mcp -H 'Content-Type: application/json' -H 'Accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-06-18","capabilities":{},"clientInfo":{"name":"curl","version":"0"}}}'

curl -s https://www.orbitprobe.com/api/mcp -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","id":2,"method":"tools/list"}'

curl -s https://www.orbitprobe.com/api/mcp -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","id":3,"method":"tools/call","params":{"name":"ssl_certificate","arguments":{"domain":"yourdomain.com"}}}'

Tools

Every tool takes a "domain" string, validated with the same rules as the site. Results are compact JSON text with a status, source and observedAt for each part.

Tool	Arguments	Returns
domain_lookup	domain	The full report: registration, DNS records, mail records, hosting network and HTTPS/TLS.
dns_records	domain, type?	A, AAAA, NS, MX, TXT, CAA, SOA and CNAME records. Optional "type" filters the list.
mail_security_check	domain	MX hosts, the SPF and DMARC records as published, and findings about them. DKIM is not tested because it needs a selector.
ssl_certificate	domain	Issuer, subject, validity dates, days left, names on the certificate, and whether the chain validated from our server.
dns_propagation	domain, type?	The answers of a fixed list of public resolvers for one record type (default A), worded "N of M resolvers".
whois_registration	domain	Registrar, creation and expiry dates, EPP status codes, nameservers and the DNSSEC flag from RDAP or WHOIS.

How to read the answers

Each part of a result carries its own status. "error" and "unsupported" mean that part could not be checked from our server at that moment; the result then also carries couldNotBeChecked: true. An assistant must not turn that into "there is no record", and must never conclude from a failed or empty registration lookup that a domain is free to register.

A tool call that cannot run at all (invalid name, reserved name such as example.com, a target that resolves only to private addresses, rate limit reached) comes back as a tool error with a sentence that says so.

All observations are made from one server location. Propagation results cover the listed resolvers only.

Limits

Tool calls use the same limiter as the HTTP API, per client IP address: 30 per minute and 300 per hour for the report-based tools and 12 per minute and 120 per hour for dns_propagation. Cached results do not count. When the limit is reached the tool returns an error that names the waiting time.

A request body may be at most 16 KB and a JSON-RPC batch at most 5 messages, which are processed one after another.

FAQ

Does the assistant get access to my account or portfolio?

No. The MCP server exposes public lookups only. It has no sign-in and cannot see any workspace data.

Can it change anything?

No. All six tools are read-only and are marked as such (readOnlyHint) in the tool list.

Why did a call for example.com fail?

Reserved documentation names are never looked up live. Ask about a real domain.

MCP server

Endpoint

Add it to your client

Claude Code

Claude Desktop and claude.ai

Cursor, VS Code and other clients

Try it with curl

Tools

How to read the answers

Limits

Related

FAQ