Lordevo Shop (x402 website checks)

HTTP ping: is a website up or down? Status and timings (DNS, TCP, TLS, TTFB) ($0.002/call)

http_ping

Read-onlyIdempotent

$0.002 per call (x402, USDC on Base; free trial: add "trial": true or use try_free). [Web and domain checks] Is this website up or down? One live request to a URL with no redirect following: up or down (and why: DNS, timeout, refused, TLS), status, Location, timings in ms for DNS, TCP connect, TLS handshake, time to first byte and total, IP, HTTP version, server header. Measured from Malaysia. Never cached. ~0.1-2 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": "http_ping"
  }
}

Input Schema

Name	Required	Description	Default
`url`	Yes	URL to ping: a 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
`ip`	No
`up`	No
`url`	No
`tool`	No
`cache`	No
`_trial`	No	Present when the call was a free trial call.
`status`	No
`provider`	No
`price_usd`	No
`timings_ms`	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 / url / description

Previous value: -"Public http(s) URL or bare domain, e.g. https://example.com"New value: +"URL to ping: a public http(s) URL or bare domain, e.g. https://example.com"

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",
+        "up"
+      ]
+    },
+    {
+      "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"
+    },
+    "ip": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "price_usd": {
+      "type": "number"
+    },
+    "provider": {
+      "type": "string"
+    },
+    "status": {
+      "type": [
+        "integer",
+        "null"
+      ]
+    },
+    "timings_ms": {
+      "type": "object"
+    },
+    "tool": {
+      "type": "string"
+    },
+    "up": {
+      "type": "boolean"
+    },
+    "url": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

AddedOct 26, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, open-world, non-destructive behavior, so the bar is lower. The description adds genuinely useful context beyond that: measurements originate from Malaysia, results are never cached, latency is roughly 0.1-2 s, and redirects are not followed — all of which shape interpretation of the output.

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 definition is dense but front-loaded with pricing and trial mechanics, then the purpose, then the returned metrics. Every clause carries information, though the pricing preamble occupying the first position slightly delays the functional statement.

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?

An output schema exists, so return values need not be explained, and the description nonetheless previews the metric set. Combined with the cost/trial terms, the measurement origin, and the no-cache/no-redirect behavior, nothing an agent needs in order to call this correctly 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 coverage is 100% and both parameters are documented in the schema, including the 'bare domain' allowance and the trial limit of 3 per IP per UTC day. The description restates the trial toggle and the x402/USDC payment mechanics but adds little syntax detail beyond the schema, so 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?

The description states a specific verb and resource ('One live request to a URL... up or down') and enumerates the diagnostic dimensions (DNS, timeout, refused, TLS), which clearly separates it from siblings like redirect_chain, link_check, or site_check. An agent can identify the tool's function 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 Guidelines3/5

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

Usage is implied rather than stated: 'Is this website up or down?' plus 'no redirect following' signals the scope, and the trial/pricing note tells the agent how to get a free call. However, no alternative tool is named, and there is no explicit when-not-to-use guidance (e.g., use redirect_chain when you need the full hop sequence).

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?