Domain Intelligence

What Domain Intelligence MCP server does

The Domain Intelligence MCP server connects MCP-compatible AI clients to the hosted Domain Intelligence API at https://oti-labs.com/mcp. It provides domain reconnaissance and configuration data through six tools: domain_lookup, whois_lookup, dns_records, ssl_certificate, subdomains, and email_security.

The aggregate lookup combines WHOIS/RDAP, DNS, SSL/TLS, subdomain discovery, and email-security results in one response. The underlying API runs the five main sections concurrently. A failed section is returned with an error while the other sections remain available.

WHOIS/RDAP data can include registrar information, registration and expiry dates, nameservers, status codes, and registry handles. DNS results cover A, AAAA, MX, TXT, NS, CAA, and SOA records. TLS inspection performs a direct connection to port 443 and reports certificate details such as issuer, validity, subject, SANs, serial number, and signature algorithm.

How it works

The Domain Intelligence MCP server uses Streamable HTTP rather than a local process. Add the hosted endpoint to an MCP client, then let the client invoke individual tools or the combined lookup. The public service uses cached successful results by section: DNS for five minutes, WHOIS and email security for one hour, SSL for six hours, and subdomains for 24 hours.

Subdomain discovery combines certificate-transparency data, passive DNS sources, DNS brute force, and optionally the subfinder executable when it is installed on the service. Results distinguish live hosts and their IP addresses from historical names. A fast response may return while slower enrichment continues in the background; wait=1 is available at the API level when a complete wait is preferred.

Email-security checks read SPF and DMARC records and probe 29 common DKIM selectors. The service returns raw SPF and DMARC records rather than parsed policy objects.

Setup and configuration

For Claude Code, add the hosted endpoint with:

claude mcp add --transport http domain-intelligence https://oti-labs.com/mcp

The README also provides setup instructions for Cursor, VS Code, Windsurf, and Claude Desktop. No API key is required for the first 1,000 lookups per month per IP. After that allowance, requests can include a RapidAPI key through the X-RapidAPI-Key header; the exact header configuration depends on the MCP client.

Tools and capabilities

• domain_lookup: request the combined domain report.
• whois_lookup: inspect registration and RDAP/WHOIS fields.
• dns_records: retrieve supported DNS record types.
• ssl_certificate: inspect the certificate currently served on port 443.
• subdomains: discover names and identify currently resolving hosts.
• email_security: check SPF, DMARC, and discovered DKIM records.

Limitations and notes

The Domain Intelligence MCP server does not guarantee complete subdomain discovery. Names absent from public sources may not be found, and some sources can be unavailable or rate-limited. The service returns up to 2,000 names while reporting the full count.

Registrant contact details are not returned, and some registries redact fields. DKIM detection is limited to 29 common selectors, so custom or hash-based selectors such as Amazon SES may be missed. BIMI, MTA-STS, and blocklist checks are not included.

Input must be a bare hostname without a scheme or path. Invalid domains return an HTTP 400 response. TLS data reflects the certificate actually presented, including expired or mismatched certificates. Individual sections can time out independently, producing an error object instead of the requested data.