Domain & Company Intel MCP

DNS Lookup

dns_lookup

Read-onlyIdempotent

Look up DNS records for a domain via Cloudflare DNS-over-HTTPS. Returns A, AAAA, MX, NS, TXT, CNAME, and SOA records. Use to see where a domain is hosted, who runs its mail and DNS, and what verification/policy TXT records it publishes.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`types`	No	Optional subset of record types, e.g. ["MX","TXT"]. Defaults to all common types.
`domain`	Yes	Domain name, e.g. stripe.com

Output Schema

TableJSON Schema

Name	Required	Description
`domain`	No
`records`	No
`provenance`	No	Where this answer came from. served_at is when Datakoot answered (UTC); upstream lists the official sources consulted. Datakoot may serve a briefly cached copy, so the source's own observation can be older than served_at.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 8, 2026

addedOutput schema / properties / provenance

Added value: +{
+  "description": "Where this answer came from. served_at is when Datakoot answered (UTC); upstream lists the official sources consulted. Datakoot may serve a briefly cached copy, so the source's own observation can be older than served_at.",
+  "properties": {
+    "may_be_cached": {
+      "type": "boolean"
+    },
+    "publisher": {
+      "type": "string"
+    },
+    "served_at": {
+      "format": "date-time",
+      "type": "string"
+    },
+    "upstream": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}

Changed1 schema field changedOct 3, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "domain": {},
+    "records": {}
+  },
+  "type": "object"
+}

First observedSep 6, 2026

TDQS

A4/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already cover readOnly, idempotent, openWorld and destructive=false, so the safety profile is handled. The description adds genuinely useful behavioral context beyond them: the upstream provider (Cloudflare DoH, a third-party network dependency) and the enumerated record set returned. It omits failure behavior for nonexistent domains or empty record sets, which would be the remaining gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, zero filler, front-loaded with what the tool does before the usage hint. Every clause carries information (mechanism, record types, use cases).

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return structure need not be explained, and annotations cover the safety semantics. Purpose, scope and usage are all present; only edge-case behavior (nonexistent domain, empty results, rate limiting on the upstream resolver) is unaddressed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so both parameters are already documented in the schema. The description reinforces the record-type dimension by enumerating A, AAAA, MX, NS, TXT, CNAME and SOA, but adds no format or syntax detail beyond that. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a precise verb+resource ('Look up DNS records for a domain') plus the mechanism (Cloudflare DNS-over-HTTPS) and the exact record types returned, so the agent knows this is a raw DNS resolver rather than an aggregate. It does not explicitly name or contrast with siblings like domain_intel or domain_report, which keeps it short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear usage context ('Use to see where a domain is hosted, who runs its mail and DNS, and what verification/policy TXT records it publishes'), which maps directly to concrete intents. No when-not conditions or named alternatives are offered, so it is context without routing.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Domain & Company Intel MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.