What the MCP Server Makes Possible

The new MCP layer wraps the existing domainIQ API and exposes it as MCP-native tools. That means you can:

• Run domain, email, name, and IP reports from an MCP client
• Use reverse IP, reverse DNS, reverse MX, and domain search without hand-building API requests
• Call monitoring actions like listing reports, pulling summaries, or adding items
• Access history and research endpoints like domain history, registration history, new registration search, and phone search
• Fall back to a controlled raw access tool when you need an approved public service/action pair that does not yet have a dedicated wrapper

The current release includes 40 explicit tools, plus a generic domainiq_api_call tool for approved public endpoints.

Built for Analyst Workflows, Not Just API Demos

The MCP Server is not a separate data silo. It reuses the same domainIQ API surface, account permissions, and limit model that customers already know.

That gives you a cleaner workflow without changing your underlying access model:

• Your existing domainIQ API key still controls access
• Queue-aware tools can hide the backend polling flow for long-running requests
• CSV, XML, and JSON results are normalized for MCP clients
• The first release stays focused on public and clearly user-facing endpoints

In practice, that means less time translating API docs into custom scripts and more time actually investigating domains, infrastructure, and ownership signals.

Two Ways to Run It

The package supports both stdio and HTTP transports.

• stdio is ideal when your MCP client launches a local command and passes the API key in the environment
• HTTP is ideal when you want a long-running MCP service that clients can reach over a local or hosted endpoint

This makes the MCP Server useful both for individual analysts working locally and for teams that want a more centralized setup.

Why This Matters

Domain intelligence is most useful when it is close to the analyst's workflow.

When domain reports, reverse lookups, and history tools are available directly inside an MCP-compatible client, you can:

• Move from question to lookup faster
• Keep research context in one place
• Chain multiple domainIQ tools together naturally
• Reduce friction for repetitive investigation tasks

The result is a workflow that feels more conversational and less mechanical, without giving up the depth of domainIQ's underlying data.

If you are already using domainIQ through scripts or manual API calls, the MCP Server is the fastest way to bring that same intelligence into your AI-assisted workflow.