Skip to main content
Glama

Genesis402 by UnyKorn (x402 pay-per-call)

by io.github.FTHTrading
OverviewDiscussionsAdmin

Look up domain registration (RDAP)

genesis402_whois

Paid ($0.003 USDC). Registry data for one domain via RDAP. Young domains are a common phishing and fraud signal. Use to vet a website or counterparty domain. For mail setup (MX, SPF, DMARC) use genesis402_email_check; for page content use genesis402_web_extract. Returns registrar, registration and expiry dates, domain age in days, days to expiry, status codes, nameservers and DNSSEC state. Payment: call once without payment_signature to get the exact price quote (nothing is charged or signed), then call again with the signed payment to receive the result and settlement details.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainYesThe domain to look up, e.g. example.com. No scheme (https://), path or port.
payment_signatureNoOptional. An x402 v2 payment you signed for this call's quote (the PAYMENT-SIGNATURE header value). Omit to get the price quote first; nothing is charged without it.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeYesQUOTE_ONLY: price quote only, nothing signed or charged. PAID: the call was paid and result holds the data. FREE: the endpoint answered without payment.
paidYestrue only when a payment was settled for this call.
priceNoThe Base USDC quote. Present on QUOTE_ONLY and on PAID calls made by a local payer; null when the rail offered no Base USDC lane or the caller signed the payment.
resultNoPAID or FREE: the endpoint's JSON result.
resourceNoQUOTE_ONLY: the full URL of the paid resource.
how_to_payNoQUOTE_ONLY: how to sign and resend the call.
settlementNoPAID: decoded PAYMENT-RESPONSE settlement (transaction hash, network, payer), or null if the rail sent none.
what_you_getNoQUOTE_ONLY: the rail's description of what the payment buys.
payment_required_b64NoQUOTE_ONLY: the raw base64 PAYMENT-REQUIRED header, to sign with any x402 v2 client.
also_accepted_networksNoQUOTE_ONLY: every network the 402 challenge accepts.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed17 schema fields changed
    • changedInput schema / properties / domain / description
      Previous value: -"Domain name, e.g. example.com."New value: +"The domain to look up, e.g. example.com. No scheme (https://), path or port."
    • changedInput schema / properties / payment_signature / description
      Previous value: -"Optional. An x402 v2 payment you signed for this call's quote (the PAYMENT-SIGNATURE header value). Omit to get the price quote first."New value: +"Optional. An x402 v2 payment you signed for this call's quote (the PAYMENT-SIGNATURE header value). Omit to get the price quote first; nothing is charged without it."
    • changedOutput schema / properties / also_accepted_networks / description
      Previous value: -"Other payment networks this endpoint accepts."New value: +"QUOTE_ONLY: every network the 402 challenge accepts."
    • changedOutput schema / properties / how_to_pay / description
      Previous value: -"How to pay for this call."New value: +"QUOTE_ONLY: how to sign and resend the call."
    • changedOutput schema / properties / mode / description
      Previous value: -"QUOTE_ONLY when no payment was made; the quote is in price."New value: +"QUOTE_ONLY: price quote only, nothing signed or charged. PAID: the call was paid and result holds the data. FREE: the endpoint answered without payment."
    • addedOutput schema / properties / mode / enum
      Added value: +[
+  "QUOTE_ONLY",
+  "PAID",
+  "FREE"
+]
    • changedOutput schema / properties / paid / description
      Previous value: -"true or the paid quote when payment settled."New value: +"true only when a payment was settled for this call."
    • addedOutput schema / properties / paid / type
      Added value: +"boolean"
    • changedOutput schema / properties / payment_required_b64 / description
      Previous value: -"The raw x402 PAYMENT-REQUIRED header, base64."New value: +"QUOTE_ONLY: the raw base64 PAYMENT-REQUIRED header, to sign with any x402 v2 client."
    • addedOutput schema / properties / price / anyOf
      Added value: +[
+  {
+    "additionalProperties": false,
+    "properties": {
+      "atomic": {
+        "description": "Price in USDC atomic units (6 decimals), as a decimal string.",
+        "type": "string"
+      },
+      "network": {
+        "description": "CAIP-2 network id of the lane, eip155:8453 (Base).",
+        "type": "string"
+      },
+      "payTo": {
+        "description": "Address the payment settles to.",
+        "type": "string"
+      },
+      "usd": {
+        "description": "Price in US dollars.",
+        "type": "number"
+      }
+    },
+    "required": [
+      "atomic",
+      "usd",
+      "payTo",
+      "network"
+    ],
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedOutput schema / properties / price / description
      Previous value: -"Quote on Base USDC: atomic, usd, payTo, network."New value: +"The Base USDC quote. Present on QUOTE_ONLY and on PAID calls made by a local payer; null when the rail offered no Base USDC lane or the caller signed the payment."
    • changedOutput schema / properties / resource / description
      Previous value: -"The endpoint URL that was quoted or called."New value: +"QUOTE_ONLY: the full URL of the paid resource."
    • changedOutput schema / properties / result / description
      Previous value: -"The endpoint's response data."New value: +"PAID or FREE: the endpoint's JSON result."
    • changedOutput schema / properties / settlement / description
      Previous value: -"Decoded x402 settlement (tx hash, network, payer)."New value: +"PAID: decoded PAYMENT-RESPONSE settlement (transaction hash, network, payer), or null if the rail sent none."
    • changedOutput schema / properties / what_you_get / description
      Previous value: -"What the paid call returns."New value: +"QUOTE_ONLY: the rail's description of what the payment buys."
    • addedOutput schema / properties / what_you_get / type
      Added value: +"string"
    • addedOutput schema / required
      Added value: +[
+  "mode",
+  "paid"
+]
  2. Changed2 schema fields changed
    • addedInput schema / properties / domain / description
      Added value: +"Domain name, e.g. example.com."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "also_accepted_networks": {
+      "description": "Other payment networks this endpoint accepts.",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "how_to_pay": {
+      "description": "How to pay for this call.",
+      "type": "string"
+    },
+    "mode": {
+      "description": "QUOTE_ONLY when no payment was made; the quote is in price.",
+      "type": "string"
+    },
+    "paid": {
+      "description": "true or the paid quote when payment settled."
+    },
+    "payment_required_b64": {
+      "description": "The raw x402 PAYMENT-REQUIRED header, base64.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "price": {
+      "description": "Quote on Base USDC: atomic, usd, payTo, network."
+    },
+    "resource": {
+      "description": "The endpoint URL that was quoted or called.",
+      "type": "string"
+    },
+    "result": {
+      "description": "The endpoint's response data."
+    },
+    "settlement": {
+      "description": "Decoded x402 settlement (tx hash, network, payer)."
+    },
+    "what_you_get": {
+      "description": "What the paid call returns."
+    }
+  },
+  "type": "object"
+}
  3. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Discloses pricing ($0.003 USDC), the two-step payment/auth flow (call once without payment_signature for a quote, then again with the signed payment), and what is returned (registrar, dates, domain age, expiry, status, nameservers, DNSSEC). This is rich behavioral context well beyond the readOnlyHint/openWorldHint annotations, and the payment-settlement mechanic explains why readOnlyHint is false without contradicting anything.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core purpose, then usage, alternatives, return fields, and the payment flow. Every sentence earns its place — no redundancy, and the operational detail (payment) is placed after the routing guidance.

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?

Given a 2-param schema, full schema coverage, an output schema, and annotations, the description covers purpose, alternatives, return contents, and the non-obvious payment flow. Nothing an agent needs to invoke it 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 description coverage is 100%, so both parameters (domain and payment_signature) are already documented in the schema. The description reinforces the payment_signature usage flow but adds no syntax or format detail beyond what the schema provides; 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?

States a specific verb+resource+scope: 'Registry data for one domain via RDAP.' It clearly identifies what is being looked up and the data source, and the additional framing ('Young domains are a common phishing and fraud signal') explains the intent, distinguishing it from sibling tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Explicitly names when to use it ('Use to vet a website or counterparty domain') and routes to alternatives by condition: 'For mail setup (MX, SPF, DMARC) use genesis402_email_check; for page content use genesis402_web_extract.' Both the when and the when-not are covered.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Genesis402 by UnyKorn (x402 pay-per-call) toolsInspect
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