MCP Server FAQ¶
What is the DomainTools MCP Server?¶
The DomainTools MCP Server integrates DomainTools domain intelligence directly into AI-powered workflows through the Model Context Protocol (MCP). This hosted service works with MCP-compatible AI clients to accelerate domain triage and infrastructure investigation.
Does DomainTools provide the AI model?¶
No. DomainTools doesn't provide or operate the Large Language Models (LLMs). The MCP Server works with your existing AI models and agents. You control which LLM you use and how you use it.
Does DomainTools use generative AI within the product?¶
No. DomainTools doesn't use generative AI to produce outputs. All tool responses are constructed programmatically from DomainTools' proprietary databases.
How is the MCP Server delivered?¶
DomainTools hosts the MCP Server as a service. You connect to it over HTTPS using your MCP-compatible client — there's nothing to install or manage on your side.
What data does the MCP Server handle?¶
- Input: You provide domain names and IP addresses.
- Output: DomainTools returns threat intelligence about those indicators, combining publicly available data with DomainTools' proprietary intelligence.
Does DomainTools log or store my queries?¶
Yes. DomainTools logs customer queries only to investigate and resolve customer-reported support issues.
Do you use my queries to train DomainTools' models?¶
No. DomainTools doesn't train its internal predictive risk models on customer data.
How does the MCP Server validate inputs and ensure security?¶
- Input control: Your security team controls the prompts that invoke MCP Server tools.
- Validation: The MCP Server validates all tool inputs against declared parameter specifications and returns errors if parameters don't match.
- Output safety: DomainTools constructs all tool responses programmatically — they aren't AI-generated. Responses follow the tool specifications and are compacted variants of the standard DomainTools API responses.
How does the MCP Server handle encryption?¶
- Data in transit: All client connections to the MCP Server use TLS-encrypted HTTPS.
- Data at rest: You're responsible for encrypting data at rest on your own systems, if required.