FeaturesHow it worksUse casesPricingHelpLog inSign up
MCP

DNS evidence inside connected workflows

Give supported tools access to the DNSReach capabilities your account is allowed to use, without exposing DNSReach administration.

What MCP access means

MCP lets supported AI tools and connected workflows request DNSReach capabilities through a controlled interface. The goal is to let a tool ask DNS questions and receive structured evidence it can explain or act on.

Example

A support assistant could check a customer hostname, compare resolver agreement and authoritative DNS, then include the evidence in the support workflow.

What can be exposed

Eligible capabilities can include DNS checks, result retrieval and interpretation. Access is limited by the customer's plan and by the MCP tools DNSReach explicitly publishes.

Not unrestricted access

MCP does not expose server administration, node secrets or arbitrary internal functions.

Authentication, limits and privacy

MCP clients authenticate through the DNSReach account model. Rate and usage limits still apply. The MCP service uses mcp.dnsreach.eu, separate from public checking and geographic node traffic.

Documentation

Public pages explain the available product. Eligible signed-in accounts receive the exact connection details and enabled tools.