Lordevo Shop (x402 website checks)

Link check: is it alive, where does it really go (redirects resolved) ($0.002/call)

link_check

Read-onlyIdempotent

$0.002 per call (x402, USDC on Base; free trial: add "trial": true or use try_free). [Web and domain checks] Resolve one link the way a browser would: follows up to 10 redirects (HEAD first, GET fallback), returns alive true/false with a reason (http_404, dns_not_found, timeout...), the final URL and domain, every hop with its status, cross-domain and HTTPS-downgrade flags, URL-shortener detection, content type/length, Last-Modified/ETag, X-Robots-Tag and TLS validity. robots.txt is checked before the link and each redirect is requested; a disallowed link is refused (not charged), a disallowed hop is reported. Dead links are an answer, not an error. Cached up to 5 min. ~0.3-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": {
      "url": "<url>"
    },
    "name": "link_check"
  }
}

Input Schema

Name	Required	Description	Default
`url`	Yes	Public http(s) URL or bare domain, e.g. https://example.com
`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
`tls`	No
`url`	No
`tool`	No
`alive`	No
`cache`	No
`flags`	No
`_trial`	No	Present when the call was a free trial call.
`reason`	No
`provider`	No
`final_url`	No
`price_usd`	No
`redirects`	No
`shortener`	No
`response_ms`	No
`content_type`	No
`cross_domain`	No
`final_domain`	No
`final_status`	No
`content_length`	No
`redirect_count`	No
`https_downgrade`	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."

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",
+        "url",
+        "alive",
+        "reason"
+      ]
+    },
+    {
+      "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"
+    },
+    "alive": {
+      "type": [
+        "boolean",
+        "null"
+      ]
+    },
+    "cache": {
+      "type": "object"
+    },
+    "content_length": {
+      "type": [
+        "integer",
+        "null"
+      ]
+    },
+    "content_type": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "cross_domain": {
+      "type": "boolean"
+    },
+    "final_domain": {
+      "type": "string"
+    },
+    "final_status": {
+      "type": [
+        "integer",
+        "null"
+      ]
+    },
+    "final_url": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "flags": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "https_downgrade": {
+      "type": "boolean"
+    },
+    "price_usd": {
+      "type": "number"
+    },
+    "provider": {
+      "type": "string"
+    },
+    "reason": {
+      "type": "string"
+    },
+    "redirect_count": {
+      "type": [
+        "integer",
+        "null"
+      ]
+    },
+    "redirects": {
+      "items": {
+        "properties": {
+          "status": {
+            "type": "integer"
+          },
+          "url": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": [
+        "array",
+        "null"
+      ]
+    },
+    "response_ms": {
+      "type": "integer"
+    },
+    "shortener": {
+      "type": "boolean"
+    },
+    "tls": {
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "tool": {
+      "type": "string"
+    },
+    "url": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

AddedOct 26, 2026

TDQS

A4/5.0

Behavior5/5

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

Annotations already cover safety properties, but the description adds substantial behavioral context: redirect limit, HEAD-first/GET-fallback behavior, returned reason codes, robots.txt handling, charging rules for disallowed links, caching, and latency. It also clarifies that dead links are a valid answer rather than an error, which is important operational context.

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 dense and front-loads pricing and scope before behavior. It wastes little space, though it repeats the price/call and trial concept already present in the title and schema.

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 high-complexity link-resolution tool with an output schema and strong annotations, the description supplies enough context to call it correctly. It covers billing, trial behavior, redirect handling, robots.txt constraints, caching, and expected latency.

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 are already documented. The description adds pricing and trial context around the trial parameter, but it does not add much meaning beyond what the schema already states for url and trial.

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

Purpose4/5

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

The description uses a specific verb and resource: 'Resolve one link the way a browser would,' then enumerates redirects, alive status, final URL/domain, hops, and flags. It is clearly a single-URL link resolver, though it does not explicitly distinguish itself from close siblings such as redirect_chain or broken_links.

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?

Usage is implied by the scope: checking whether one link is alive and where it redirects. However, the description gives no explicit when-to-use guidance, no when-not-to-use exclusions, and no named alternatives for related tasks like batch checks or redirect-chain-only checks.

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?