Genesis402 by UnyKorn (x402 pay-per-call)

Scan address across 10 EVM chains

genesis402_multi_chain_scan

Paid ($0.008 USDC). Sweeps one address across 10 EVM chains at once and reports where it is actually active. Use to find which networks an address uses before drilling into one chain. No risk scoring or sanctions check: for that use genesis402_wallet_brief. Returns, per chain, the native balance, the number of transactions sent and whether contract bytecode is deployed; chains whose RPC did not answer are listed separately, never counted as inactive. Activity is inferred from nonce, balance and code, so an address that only ever received tokens can show a zero nonce; check its balance field. Public on-chain data with sources and an evidence hash. 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

Name	Required	Description	Default
`address`	Yes	The EVM address to scan, 0x followed by 40 hex characters. Checksum case is optional.
`payment_signature`	No	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.

Output Schema

TableJSON Schema

Name	Required	Description
`mode`	Yes	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.
`paid`	Yes	true only when a payment was settled for this call.
`price`	No	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.
`result`	No	PAID or FREE: the endpoint's JSON result.
`resource`	No	QUOTE_ONLY: the full URL of the paid resource.
`how_to_pay`	No	QUOTE_ONLY: how to sign and resend the call.
`settlement`	No	PAID: decoded PAYMENT-RESPONSE settlement (transaction hash, network, payer), or null if the rail sent none.
`what_you_get`	No	QUOTE_ONLY: the rail's description of what the payment buys.
`payment_required_b64`	No	QUOTE_ONLY: the raw base64 PAYMENT-REQUIRED header, to sign with any x402 v2 client.
`also_accepted_networks`	No	QUOTE_ONLY: every network the 402 challenge accepts.

Schema Changelog

Changes observed during successful MCP inspections.

Changed17 schema fields changedSep 29, 2026

changedInput schema / properties / address / description

Previous value: -"EVM address, 0x followed by 40 hex characters."New value: +"The EVM address to scan, 0x followed by 40 hex characters. Checksum case is optional."

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"
+]
```

Changed2 schema fields changedSep 26, 2026

addedInput schema / properties / address / description

Added value: +"EVM address, 0x followed by 40 hex characters."

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"
+}

First observedSep 25, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Goes well beyond the annotations by disclosing the price ($0.008 USDC) and the full x402 flow (call once for a free quote, call again with the signed payment). It also pre-empts failure modes an agent would otherwise misread: unavailable RPCs are listed separately and never counted as inactive, and receive-only addresses can legitimately show a zero nonce. This is exactly the kind of behavioral context structured fields cannot carry.

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?

It is long, but front-loaded with the paid price and the one-line purpose before details. Nearly every sentence carries a distinct fact (scope, exclusions, return shape, caveats, payment protocol), though the caveat cluster in the middle could be tightened slightly.

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, yet the description still summarizes the per-chain return shape (native balance, tx count, bytecode presence) plus the partial-failure list, which is what an agent needs to reason about incomplete results. Payment mechanics, scope, alternatives and caveats are all covered for a paid, open-world read tool.

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 genuine meaning beyond the schema: it explains why payment_signature exists (the two-call quote-then-pay cycle) and how to interpret the address's results, since activity is inferred from nonce, balance and code. It clarifies the semantics of the output fields rather than the parameter syntax, which is a modest but real value-add.

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 and resource ('Sweeps one address across 10 EVM chains at once and reports where it is actually active') with the exact scope of the sweep. It explicitly distinguishes itself from siblings by naming what it does NOT do ('No risk scoring or sanctions check') and naming the sibling that does it. An agent can route without opening any schema.

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?

Gives a concrete when-to-use ('find which networks an address uses before drilling into one chain') and an explicit alternative with its condition ('for that use genesis402_wallet_brief'). The two-step payment protocol is also spelled out as a usage instruction, not left to inference.

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) 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.