Lordevo Shop (x402 website checks)

WHOIS / RDAP domain lookup: age, registrar, expiry ($0.002/call)

domain_rdap

Read-onlyIdempotent

$0.002 per call (x402, USDC on Base; free trial: add "trial": true or use try_free). [Web and domain checks] WHOIS-style domain lookup. Registration facts for a domain from the official registry RDAP service (successor to WHOIS): registered or not, registrar and IANA id, created / updated / expiry dates, age in days, days to expiry, EPP status codes, nameservers and DNSSEC. Personal contact data is never returned. Cached 24 h. ~0.5-3 s.

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": "domain_rdap"
  }
}

Input Schema

Name	Required	Description	Default
`trial`	No	Optional. true = free if a trial call is left (3 per IP per UTC day), else the payment terms.
`domain`	Yes	Domain to look up, e.g. example.com (a URL or email address also works; the registrable domain is used)

Output Schema

Name	Required	Description
`tool`	No
`cache`	No
`_trial`	No	Present when the call was a free trial call.
`dnssec`	No
`domain`	No
`status`	No
`created`	No
`expires`	No
`age_days`	No
`provider`	No
`price_usd`	No
`registrar`	No
`registered`	No
`nameservers`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 5, 2026

changedInput schema / properties / trial / description

Previous value: -"Optional. true = answer free if a trial call is left (3 per IP per UTC day); otherwise you get the payment terms."New value: +"Optional. true = free if a trial call is left (3 per IP per UTC day), else the payment terms."

Changed1 schema field changedNov 3, 2026

changedInput schema / properties / domain / description

Previous value: -"Domain name, e.g. example.com (a URL or email address also works)"New value: +"Domain to look up, e.g. example.com (a URL or email address also works; the registrable domain is used)"

Changed2 schema fields changedNov 3, 2026

addedInput schema / properties / trial

Added value: +{
+  "description": "Optional. true = answer free if a trial call is left (3 per IP per UTC day); otherwise you get the payment terms.",
+  "type": "boolean"
+}

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "anyOf": [
+    {
+      "required": [
+        "tool",
+        "domain",
+        "registered"
+      ]
+    },
+    {
+      "properties": {
+        "accepts": {
+          "type": "array"
+        },
+        "error": {
+          "type": "string"
+        },
+        "resource": {
+          "type": "object"
+        },
+        "x402Version": {
+          "type": "integer"
+        }
+      },
+      "required": [
+        "x402Version",
+        "accepts"
+      ]
+    },
+    {
+      "properties": {
+        "charged": {
+          "type": "boolean"
+        },
+        "error": {
+          "type": "string"
+        },
+        "message": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "error"
+      ]
+    }
+  ],
+  "properties": {
+    "_trial": {
+      "description": "Present when the call was a free trial call.",
+      "type": "object"
+    },
+    "age_days": {
+      "type": [
+        "integer",
+        "null"
+      ]
+    },
+    "cache": {
+      "type": "object"
+    },
+    "created": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "dnssec": {
+      "type": [
+        "boolean",
+        "null"
+      ]
+    },
+    "domain": {
+      "type": "string"
+    },
+    "expires": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "nameservers": {
+      "type": "array"
+    },
+    "price_usd": {
+      "type": "number"
+    },
+    "provider": {
+      "type": "string"
+    },
+    "registered": {
+      "type": "boolean"
+    },
+    "registrar": {
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "status": {
+      "type": "array"
+    },
+    "tool": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

AddedOct 26, 2026

TDQS

A4.2/5.0

Behavior5/5

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

Beyond the readOnly/idempotent/openWorld annotations, the description discloses pricing and payment rail ($0.002/call, x402 USDC on Base), the trial escape hatch, a 24 h cache, a 0.5-3 s latency band, the upstream data source (official registry RDAP), and a privacy guarantee that personal contact data is never returned. These are exactly the operational facts an agent needs before spending money on a call.

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 and mostly front-loaded, with the cost model in the first sentence so a cost-sensitive agent sees it immediately. Slightly weakened by burying the actual purpose behind the pricing line, but no sentence is wasted.

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?

For a single-domain read tool with an output schema already covering return shape, the description still supplies cost, cache lifetime, latency, data provenance and privacy behavior. Nothing needed to call it correctly or judge whether it is worth the fee is missing.

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, including the flexible 'domain' input (URL or email accepted) and the trial semantics. The description only restates the trial flag in a pricing context; it adds no new syntax or constraint detail, 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 ('WHOIS-style domain lookup ... Registration facts for a domain from the official registry RDAP service') and enumerates the returned facts: registration status, registrar + IANA id, created/updated/expiry dates, age, days to expiry, EPP status, nameservers, DNSSEC. That field list cleanly separates it from siblings like dns_lookup or domain_intel even though those aren't named.

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

Usage Guidelines3/5

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

The '[Web and domain checks]' tag and the pointer to try_free give a loose context and a cost-based alternative, but there is no explicit statement of when to prefer this over dns_lookup, domain_intel, or url_trust, and no exclusions. Usage is implied rather than prescribed.

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

All Lordevo Shop (x402 website checks) 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?