ScrapeMole Domains

ScrapeMole Domains: DNS, WHOIS/RDAP, domain availability, email security, SSL certificates and subdomains for AI agents: DNS lookup

dns

Read-onlyIdempotent

Use when you need the current DNS records of a domain or hostname: resolves the requested record types live over DNS-over-HTTPS (Cloudflare 1.1.1.1 with Google fallback) and returns every answer with TTL, plus the response code (NOERROR/NXDOMAIN) and whether DNSSEC validated. Up to 8 types per call. Paid tool: x402 USDC on Base, $0.001 per successful call; call without payment to receive the PaymentRequired object.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>"
    },
    "name": "dns"
  }
}

Input Schema

Name	Required	Description	Default
`name`	Yes	Domain or hostname, e.g. example.com or www.example.com.
`type`	No	Comma-separated record types (max 8). Supported: A, NS, CNAME, SOA, PTR, MX, TXT, AAAA, SRV, DS, DNSKEY, HTTPS, SVCB, CAA.	A,AAAA,CNAME,MX,NS,TXT

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 11, 2026

TDQS

A4.4/5.0

Behavior5/5

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

With annotations covering safety (readOnly, idempotent, openWorld), the description still adds substantial non-obvious behavior: the DoH resolvers used and fallback order, that TTL/response code/DNSSEC validation are returned, the 8-type ceiling, and the entire payment model (x402 USDC on Base, $0.001 per successful call, PaymentRequired object when unpaid). The payment disclosure is critical and appears nowhere in the structured fields.

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

Conciseness4/5

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

The tool's purpose and scope are front-loaded in the first clause, and the two trailing clauses (type limit, payment) are dense but each carries information an agent needs. It is slightly compressed into one long sentence, which makes it heavier to parse than a split structure would be.

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

Completeness5/5

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

Since there is no output schema, the description carries the return-value burden and does so explicitly (answers with TTL, response code NOERROR/NXDOMAIN, DNSSEC validation). Combined with the payment mechanics, an agent has everything needed to call and interpret the tool.

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 coverage is 100%, so both parameters (name, type) are already documented with examples and the supported type list. The description restates the resolution behavior and the 'up to 8 types' limit, both of which the schema already conveys, so it adds little parameter-level meaning beyond the baseline.

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

Purpose5/5

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

The description opens with a specific condition and verb/resource ('resolves the current DNS records of a domain or hostname') and names the mechanism (DNS-over-HTTPS via Cloudflare/Google), which cleanly separates it from sibling tools like ssl, subdomains, rdap, and email_security. An agent can identify this as the raw DNS-record tool without opening any schema.

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?

It gives a clear trigger ('Use when you need the current DNS records of a domain or hostname') and a usage constraint ('Up to 8 types per call'). It does not explicitly name alternatives or state when-not to use it versus the other ScrapeMole domain tools, so it stops short of a 5.

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

All ScrapeMole Domains 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.

Resources

Need Help?