Lordevo Shop (x402 website checks)

DNS records lookup (A, AAAA, CNAME, MX, TXT, NS, SOA, CAA) ($0.002/call)

dns_lookup

Read-onlyIdempotent

$0.002 per call (x402, USDC on Base; free trial: add "trial": true or use try_free). [Web and domain checks] Live DNS lookup, like dig or nslookup, for any public host name: one record type or ALL (A, AAAA, CNAME, MX, TXT, NS, SOA, CAA) in one call. Returns each record set, NXDOMAIN (exists: false), per-type errors and private-address flags. Use it to read MX and SPF/verification TXT records or find nameservers. DNS + RDAP + SPF/DMARC + TLS in one call: domain-intel. Cached 2 min. ~0.1-1 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": {
      "host": "<host>"
    },
    "name": "dns_lookup"
  }
}

Input Schema

Name	Required	Description	Default
`host`	Yes	Host name to look up, e.g. example.com or mail.example.com (a URL also works; the host part is used)
`type`	No	Record type (default ALL = A, AAAA, CNAME, MX, TXT, NS, SOA, CAA)	ALL
`trial`	No	Optional. true = free if a trial call is left (3 per IP per UTC day), else the payment terms.

Output Schema

Name	Required	Description
`host`	No
`tool`	No
`type`	No
`cache`	No
`_trial`	No	Present when the call was a free trial call.
`errors`	No
`exists`	No
`source`	No
`records`	No	One key per record type asked for; [] = no records of that type
`provider`	No
`price_usd`	No
`resolved_at`	No
`response_ms`	No
`private_addresses`	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 / host / description

Previous value: -"Public host name, e.g. example.com or www.example.com (a URL also works)"New value: +"Host name to look up, e.g. example.com or mail.example.com (a URL also works; the host part 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",
+        "host",
+        "exists",
+        "records"
+      ]
+    },
+    {
+      "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"
+    },
+    "cache": {
+      "type": "object"
+    },
+    "errors": {
+      "additionalProperties": {
+        "type": "string"
+      },
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "exists": {
+      "type": "boolean"
+    },
+    "host": {
+      "type": "string"
+    },
+    "price_usd": {
+      "type": "number"
+    },
+    "private_addresses": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "provider": {
+      "type": "string"
+    },
+    "records": {
+      "description": "One key per record type asked for; [] = no records of that type",
+      "properties": {
+        "A": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "AAAA": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "CAA": {
+          "items": {
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "CNAME": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "MX": {
+          "items": {
+            "properties": {
+              "exchange": {
+                "type": "string"
+              },
+              "priority": {
+                "type": "integer"
+              }
+            },
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "NS": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "SOA": {
+          "type": [
+            "object",
+            "null"
+          ]
+        },
+        "TXT": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        }
+      },
+      "type": "object"
+    },
+    "resolved_at": {
+      "type": "string"
+    },
+    "response_ms": {
+      "type": "integer"
+    },
+    "source": {
+      "type": "string"
+    },
+    "tool": {
+      "type": "string"
+    },
+    "type": {
+      "enum": [
+        "ALL",
+        "A",
+        "AAAA",
+        "CNAME",
+        "MX",
+        "TXT",
+        "NS",
+        "SOA",
+        "CAA"
+      ],
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

AddedOct 26, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, and the description adds genuinely new behavior: 2-minute caching, ~0.1-1 s latency, NXDOMAIN signaled as exists:false, per-type errors, private-address flags, and the exact price. That is strong beyond-annotation disclosure, though it does not say whether private-address flags refuse the lookup or merely annotate 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?

Pricing is front-loaded, purpose second, then scope, use cases, alternative, and performance facts — a sensible order with no filler sentences. The only redundancy is the price restated between the title and the first clause of the description.

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 read-only lookup tool with an output schema, the description covers cost, inputs, aggregation mode, error semantics, caching, latency, and the sibling alternative. Nothing an agent needs to call it correctly is missing.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3; the description adds the meaningful semantic that ALL means all eight types returned in a single call rather than requiring multiple calls. It also mentions the trial escape hatch, though the 3-per-IP-per-day detail is already in the schema and only repeated here.

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 ('Live DNS lookup, like dig or nslookup') plus the full record-type scope and the ALL-mode aggregation. It also names the sibling that covers broader needs (domain-intel), so an agent can distinguish it 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?

Gives concrete use cases ('read MX and SPF/verification TXT records or find nameservers') and explicitly routes broader DNS+RDAP+SPF/DMARC+TLS needs to domain-intel. It stops short of stating exclusions, such as private/non-public hosts being out of scope, so it is clear but not fully bounded.

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?