ScrapeMole Domains

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

rdap

Read-onlyIdempotent

Use when you need to know who registered a domain through (registrar), when it was created, when it expires, its EPP status (e.g. clientTransferProhibited), nameservers and DNSSEC: queries the authoritative registry RDAP server (the modern WHOIS) found via the IANA bootstrap. Registrant personal data is never returned. Answers 404 (not charged) when the domain is not registered. Paid tool: x402 USDC on Base, $0.002 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": {
      "domain": "<domain>"
    },
    "name": "rdap"
  }
}

Input Schema

Name	Required	Description	Default
`domain`	Yes	Registrable domain, e.g. example.com.

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?

Adds substantial context beyond the readOnly/openWorld/idempotent annotations: registrant personal data is never returned, an unregistered domain yields 404 and is not charged, and the tool is paid via x402 USDC on Base at $0.002 per successful call, with a PaymentRequired object returned if called without payment. These are exactly the operational facts an agent needs before invoking it.

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?

Dense but efficient: the use-case trigger leads, followed by returned fields, privacy, error/charging behavior and payment terms. Slightly run-on with several clauses stacked, but every sentence carries information.

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?

No output schema exists, yet the description enumerates the returned fields (registrar, dates, EPP status, nameservers, DNSSEC), plus privacy, 404/charging behavior and payment mechanics. An agent has everything needed to call this correctly.

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?

Only one parameter and schema description coverage is 100%, so the schema already defines 'domain' with an example. The description adds no syntax or format detail beyond that, so the baseline 3 applies.

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?

States a specific verb and resource: queries the authoritative registry RDAP server (the modern WHOIS) found via IANA bootstrap, and enumerates exactly what it returns (registrar, creation/expiry dates, EPP status, nameservers, DNSSEC). This is cleanly separable from the sibling tools availability, dns, email_security, ssl and subdomains, which cover different data.

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?

Front-loads an explicit trigger, 'Use when you need to know who registered a domain...', which is a clear condition for selecting this tool. It does not name alternatives or state when not to use it (e.g. vs availability for registration status), so it stops short of full routing guidance.

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?