Lordevo Shop (x402 website checks)

IP lookup: owner, network and abuse contact of an IP address (RDAP + reverse DNS) ($0.002/call)

ip_info

Read-onlyIdempotent

$0.002 per call (x402, USDC on Base; free trial: add "trial": true or use try_free). [Web and domain checks] IP lookup (IP WHOIS). Who holds a public IPv4/IPv6 address, from the Regional Internet Registry RDAP record: network name, handle, CIDR, address range, country, holding organisation, abuse mailbox, RIR (ARIN/RIPE/APNIC/LACNIC/AFRINIC) and reverse DNS (PTR). No geolocation database and no ASN. 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": {
      "ip": "<ip>"
    },
    "name": "ip_info"
  }
}

Input Schema

Name	Required	Description	Default
`ip`	Yes	Public IPv4 or IPv6 address, e.g. 8.8.8.8 or 2606:4700:4700::1111
`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
`ip`	No
`rir`	No
`tool`	No
`cache`	No
`_trial`	No	Present when the call was a free trial call.
`network`	No
`version`	No
`provider`	No
`price_usd`	No
`abuse_email`	No
`reverse_dns`	No
`organization`	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 / ip / description

Previous value: -"Public IPv4 or IPv6 address, e.g. 8.8.8.8"New value: +"Public IPv4 or IPv6 address, e.g. 8.8.8.8 or 2606:4700:4700::1111"

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",
+        "ip",
+        "network"
+      ]
+    },
+    {
+      "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"
+    },
+    "abuse_email": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "cache": {
+      "type": "object"
+    },
+    "ip": {
+      "type": "string"
+    },
+    "network": {
+      "type": "object"
+    },
+    "organization": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "price_usd": {
+      "type": "number"
+    },
+    "provider": {
+      "type": "string"
+    },
+    "reverse_dns": {
+      "type": "array"
+    },
+    "rir": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "tool": {
+      "type": "string"
+    },
+    "version": {
+      "type": "integer"
+    }
+  },
+  "type": "object"
+}

AddedOct 26, 2026

TDQS

A4.4/5.0

Behavior5/5

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

With annotations already covering readOnly/idempotent/openWorld/non-destructive, the description adds substantial context beyond them: 24 h caching, ~0.5-3 s latency, the x402/USDC payment mechanism, and a concrete trial quota (3 per IP per UTC day). It also qualifies input preconditions ("public" address only) and what data is deliberately absent, which no annotation conveys.

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 description is front-loaded with the price and then the core resource definition, and each subsequent clause (returns, exclusions, caching, latency) carries distinct information. The bracketed "[Web and domain checks]" label is minor clutter, and the pricing preamble sits ahead of the purpose statement, slightly delaying the key identification.

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 two-parameter read tool with an output schema, everything an agent needs is present: what is looked up, what is returned, what is out of scope, cost, latency, cache lifetime, and the free-trial escape hatch. Return-value detail is a bonus rather than a gap since an output schema exists.

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% for both parameters, so the baseline is 3. The description restates the trial mechanics ("add 'trial': true or use try_free") and echoes the per-IP daily limit already in the schema, adding little syntax or format meaning beyond what the structured fields provide.

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 — IP lookup / IP WHOIS for a public IPv4/IPv6 address — and enumerates exactly what the RDAP record yields (network name, handle, CIDR, range, country, org, abuse mailbox, RIR, PTR). It also carves out scope explicitly with "No geolocation database and no ASN", which lets an agent separate this from geolocation-style siblings without opening the 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?

The "[Web and domain checks]" tag and the ownership framing give clear context for when this is the right call, and the embedded "use try_free" pointer names an alternative for the free-trial path. It stops short of explicit routing to siblings like domain_rdap (for domains rather than IPs) or dns_lookup (for records rather than ownership), so no true when-not statement is present.

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?