Lordevo Shop (x402 website checks)

SSL/TLS certificate check (expiry, issuer, SANs, chain) ($0.002/call)

ssl_cert

Read-onlyIdempotent

$0.002 per call (x402, USDC on Base; free trial: add "trial": true or use try_free). [Web and domain checks] Connects to host:443 and reports the certificate: trusted or not (and why), hostname match, issuer, valid from/to, days left, expired / expiring within 21 days, SAN list, wildcard, key type and size, serial, SHA-256 fingerprint, OCSP/CA URLs, chain, TLS version, cipher and ALPN. Cached 1 h. ~0.2-1.5 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": "ssl_cert"
  }
}

Input Schema

Name	Required	Description	Default
`host`	Yes	Public host name, e.g. example.com or www.example.com (a URL also works)
`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
`san`	No
`host`	No
`tool`	No
`cache`	No
`valid`	No
`_trial`	No	Present when the call was a free trial call.
`issuer`	No
`issues`	No
`trusted`	No
`protocol`	No
`provider`	No
`valid_to`	No
`days_left`	No
`price_usd`	No
`hostname_match`	No
`https_available`	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",
+        "host",
+        "https_available"
+      ]
+    },
+    {
+      "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"
+    },
+    "days_left": {
+      "type": [
+        "integer",
+        "null"
+      ]
+    },
+    "host": {
+      "type": "string"
+    },
+    "hostname_match": {
+      "type": "boolean"
+    },
+    "https_available": {
+      "type": "boolean"
+    },
+    "issuer": {
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "issues": {
+      "type": "array"
+    },
+    "price_usd": {
+      "type": "number"
+    },
+    "protocol": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "provider": {
+      "type": "string"
+    },
+    "san": {
+      "type": "array"
+    },
+    "tool": {
+      "type": "string"
+    },
+    "trusted": {
+      "type": "boolean"
+    },
+    "valid": {
+      "type": "boolean"
+    },
+    "valid_to": {
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "type": "object"
+}

AddedOct 26, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Beyond the read-only and open-world annotations, it discloses the remote port-443 connection, one-hour cache, approximate 0.2-1.5 second latency, payment rail, and free-trial route. It also adds useful operational details, including reasons for trust failure and the 21-day threshold for an expiring certificate.

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?

Three compact sentences convey cost, purpose, behavior, cache freshness, and latency with little filler. The long enumeration of reported fields is dense and somewhat redundant with the output schema, and leading with pricing makes the purpose slightly less front-loaded.

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-only check with an output schema, the description supplies the operational context needed for correct selection and invocation: endpoint behavior, inspection scope, cost, trial access, caching, and latency. Explicit sibling-routing guidance would improve it, but no significant invocation detail 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 the baseline is 3, but the description adds that the supplied host is contacted specifically on port 443. It also clarifies that the trial can be accessed either through the trial parameter or try_free, although much of the remaining trial and pricing information repeats structured fields.

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 action and resource: it connects to host:443 and reports on the SSL/TLS certificate. Concrete details such as trust, hostname matching, validity, SANs, chain, cipher, and ALPN clearly distinguish it from broader domain, site, and security siblings.

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]" label and fixed host:443 behavior establish a clear certificate-checking use case, while try_free is identified for trial usage. It does not explicitly explain when to prefer alternatives such as security_scan_lite, url_trust, or site_check for broader assessments.

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?