xAI · MCP with API key

DNSai for Grok

Connect DNSai to Grok through xAI's remote MCP tool in the API, the Grok Build CLI, or a custom connector on grok.com, and ask about domains, email security and DNS changes.

What you can ask Grok

Example answers use made-up domains.

“Which domains in my portfolio still have DMARC p=none?”

41 of 380. The biggest by traffic are contoso.example and tailspin.example; both publish rua reports, so they are ready to move to quarantine.

Connect in 3 steps (about 3 minutes)

Create a DNSai API key for Grok.
Add DNSai as a remote MCP tool in your xAI API call or Grok Build.
Ask Grok about your domains.

Signed-in Enterprise customers get the exact click-by-click steps and ready-to-paste configuration for Grok, a one-click API key for it, and a live connection check.

Grok requirements: xAI API access, Grok Build, or a grok.com plan with connectors. DNSai Enterprise plan.

Good for

Agents on the xAI API that need DNS facts
Quick lookups from the Grok Build terminal

Security

Grok sends an API key in the Authorization header. Use an expiring key made for Grok and keep it in an environment variable.
Account and organization owners can make API keys and assistants read-only, so they can read your data but never change it or start scans.
Starting a credit-spending Deep Scan always needs an estimate and your explicit confirmation.
DNSai data comes from public DNS and web records. Your watchlists, notes and tags stay private to your account and are only shared with an AI tool you connect yourself.

Connect Grok to DNSai

The API and AI connectors are included with DNSai Enterprise plans. Every member of your organization shares one set of limits, and every call counts from the first one.

Other integrations

Last checked 2026-10-29.