Skip to content
DomainTools Technical Documentation

MCP Server — DNSDB Passive DNS, Domain History, and OAuth support

← All updates ·

Added

  • DNSDB passive DNS tools — New tools expose passive DNS data from DNSDB directly through the MCP Server. Agents can run forward and inverse passive DNS lookups, time-fenced queries, and pattern-based searches to trace historical DNS resolution, identify infrastructure pivots, and surface related domains observed across the global DNS infrastructure.

  • Domain registration history tools — New tools surface domain registration history via the Domain History API. Agents can retrieve timestamped WHOIS and registration records — including registrar changes, contact updates, and infrastructure transitions — as part of investigation workflows.

  • OAuth 2.0 authentication — The MCP Server now supports OAuth with pre-registered client credentials, so MCP clients sign in with a DomainTools account instead of an API key. OAuth pre-registration is available for the following clients:

    • Claude Code — fixed callback port
    • Claude Desktop — Custom Connector with Advanced settings
    • Cursor — .cursor/mcp.json auth block
    • Gemini CLI — ~/.gemini/settings.json with static redirect URI
    • VS Code — Command Palette MCP Add, GitHub Copilot agent mode

    To request OAuth credentials, contact your DomainTools representative or email enterprisesupport@domaintools.com with your chosen client(s), redirect URIs, and an optional proposed client name. DomainTools returns a confirmed client name, client ID, and client secret.

    Client name match

    Except for VS Code, the name you use in your MCP client configuration must exactly match the client name registered with DomainTools. The server rejects connections where the name doesn’t match.

    Clients that don’t support OAuth pre-registration — such as Codex and Goose Desktop — continue to use API key authentication.

Documentation

Categories: AI, MCP Server