Lordevo Shop (x402 website checks)

Email validation / email verification API (syntax + domain + MX, no SMTP probing) ($0.002/call)

email_validate

Read-onlyIdempotent

$0.002 per call (x402, USDC on Base; free trial: add "trial": true or use try_free). [Web and domain checks] Validates one email address without contacting the mailbox: RFC 5321 syntax, domain exists, MX / null-MX / implicit-MX, MX hosts resolve, mail provider, disposable-domain flag (CC0 list), role account (info@, support@), free provider, typo suggestion (gmial.com -> gmail.com). Verdict valid / risky / invalid. ~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": {
      "email": "<email>"
    },
    "name": "email_validate"
  }
}

Input Schema

Name	Required	Description	Default
`email`	Yes	Email address, e.g. jane@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
`mx`	No
`tool`	No
`cache`	No
`email`	No
`flags`	No
`_trial`	No	Present when the call was a free trial call.
`reason`	No
`verdict`	No
`provider`	No
`price_usd`	No
`normalized`	No
`accepts_mail`	No
`did_you_mean`	No
`syntax_valid`	No
`domain_exists`	No
`mail_provider`	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",
+        "email",
+        "verdict",
+        "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"
+    },
+    "accepts_mail": {
+      "type": "boolean"
+    },
+    "cache": {
+      "type": "object"
+    },
+    "did_you_mean": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "domain_exists": {
+      "type": [
+        "boolean",
+        "null"
+      ]
+    },
+    "email": {
+      "type": "string"
+    },
+    "flags": {
+      "type": "object"
+    },
+    "mail_provider": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "mx": {
+      "type": "array"
+    },
+    "normalized": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "price_usd": {
+      "type": "number"
+    },
+    "provider": {
+      "type": "string"
+    },
+    "reason": {
+      "type": "string"
+    },
+    "syntax_valid": {
+      "type": "boolean"
+    },
+    "tool": {
+      "type": "string"
+    },
+    "verdict": {
+      "enum": [
+        "valid",
+        "risky",
+        "invalid"
+      ],
+      "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 establish read-only, idempotent, non-destructive behavior, and the description adds substantial operational context: cost per call, payment mechanism, trial path, latency range, no mailbox contact, and the verdict categories returned. This is strong disclosure beyond the structured annotations.

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 but front-loads the key cost and trial information, then moves into scope and validation checks. The long enumeration of checks earns its place by precisely defining what is validated, though the pricing-first framing is slightly unusual.

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?

The tool is simple: one required email parameter plus an optional trial flag, with full schema coverage, annotations, and an output schema. The description covers what is validated, what is not contacted, expected latency, verdict categories, and cost, which is complete for an agent to invoke it correctly.

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 description coverage is 100%, so both parameters are already well documented. The description adds pricing and trial context around the 'trial' parameter but does not introduce new syntax or semantic details beyond what the schema provides, making 3 the appropriate baseline.

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 gives a specific verb and resource: validates one email address, and enumerates the exact checks (RFC 5321 syntax, domain existence, MX, disposable, role account, typo suggestion). It clearly scopes the tool as non-SMTP, but it does not explicitly differentiate itself from related siblings such as email_auth or domain_intel.

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 capability list and the explicit 'without contacting the mailbox' scope, which tells an agent this is a non-intrusive validation tool. However, there is no explicit 'use this when' guidance or comparison to alternative tools like email_auth.

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?