ChainHelix for Machines

screened_payer

Read-only

A signed statement on whether a wallet is clear of sanctions lists, the same screen every payer here passes before a settle: the OFAC SDN address list and the on-chain sanctions oracle. Send an EVM address; get the result, both sources, the time of the screen, its expiry after 24 hours, the statement text and its signature from a ChainHelix key that holds no funds. A seller agent checks the signature and the expiry before it negotiates. clear: on neither list; listed: on at least one; partial: one source could not be read. Price: 6 cents per call.

Input Schema

Name	Required	Description	Default
`address`	Yes	EVM address, 0x and 40 hex characters. Example: 0x000000000000000000000000000000000000dead
`network`	No	CAIP-2 network id written into the statement, up to 40 characters, default eip155:56. Example: eip155:8453

Output Schema

Name	Required	Description	Default
`error`	No
`payer`	No
`result`	No
`signer`	No
`message`	No
`network`	No
`sources`	No
`version`	No
`expiresAt`	No
`signature`	No
`screenedAt`	No
`howToVerify`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 25, 2026

addedInput schema / properties / address / description

Added value: +"EVM address, 0x and 40 hex characters. Example: 0x000000000000000000000000000000000000dead"

addedInput schema / properties / network / description

Added value: +"CAIP-2 network id written into the statement, up to 40 characters, default eip155:56. Example: eip155:8453"

Changed1 schema field changedOct 16, 2026

changedInput schema / x-lexicon / bundleSha256

Previous value: -"670f7504e3de5031beccee25a2d24e4515f68b893295f6d5b0d3a0665498b2c9"New value: +"25cc80db6d8e9eac73d47a50f7ad6333a21f1972d008a8fed0159de8bfb4b519"

Changed2 schema fields changedOct 16, 2026

changedInput schema / x-lexicon / bundleSha256

Previous value: -"e5b4290024a229f2bdf97f8fc6a0079c3fe13b77267f41fdcffeb8b26aa1c41e"New value: +"670f7504e3de5031beccee25a2d24e4515f68b893295f6d5b0d3a0665498b2c9"

changedInput schema / x-lexicon / version

Previous value: -"0.1.0"New value: +"0.2.0"

Changed3 schema fields changedOct 15, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

removedOutput schema / properties / meta

Removed value: -{
-  "additionalProperties": false,
-  "properties": {
-    "contentHash": {
-      "type": "string"
-    },
-    "generated": {
-      "type": "number"
-    },
-    "priceUsd": {
-      "type": "number"
-    },
-    "validUntil": {
-      "type": "number"
-    }
-  },
-  "type": "object"
-}

removedOutput schema / properties / receipt

Removed value: -{
-  "additionalProperties": false,
-  "properties": {
-    "bytes": {
-      "type": "number"
-    },
-    "covers": {
-      "type": "string"
-    },
-    "issuedAt": {
-      "type": "number"
-    },
-    "lookup": {
-      "type": "string"
-    },
-    "network": {
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "nonce": {
-      "type": "string"
-    },
-    "seq": {
-      "type": "number"
-    },
-    "settleTx": {
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "sha256": {
-      "type": "string"
-    },
-    "tool": {
-      "type": [
-        "string",
-        "null"
-      ]
-    }
-  },
-  "type": "object"
-}

Changed1 schema field changedSep 21, 2026

changedInput schema / x-lexicon / bundleSha256

Previous value: -"a1c2e10fd3177d6b4d59ca78693e8fb36880165cf0f735f680dd86a510411178"New value: +"e5b4290024a229f2bdf97f8fc6a0079c3fe13b77267f41fdcffeb8b26aa1c41e"

Changed1 schema field changedSep 19, 2026

changedInput schema / x-lexicon / bundleSha256

Previous value: -"1eeb782ee15fe69fc80776948e0556fa6b795e210e6305935b2c97b73d955cda"New value: +"a1c2e10fd3177d6b4d59ca78693e8fb36880165cf0f735f680dd86a510411178"

Changed1 schema field changedSep 19, 2026

changedInput schema / x-lexicon / bundleSha256

Previous value: -"c014292cad7497ce9fd68c33345ac32cb42b672c8e77d6c749c26e162cc207e4"New value: +"1eeb782ee15fe69fc80776948e0556fa6b795e210e6305935b2c97b73d955cda"

Changed3 schema fields changedSep 19, 2026

addedInput schema / x-aliases

Added value: +{
+  "address": [
+    "Address"
+  ],
+  "network": [
+    "Network"
+  ]
+}

addedInput schema / x-lexicon

Added value: +{
+  "bundleSha256": "c014292cad7497ce9fd68c33345ac32cb42b672c8e77d6c749c26e162cc207e4",
+  "name": "ChainHelix Agentic Lexicon",
+  "resolve": "lexicon_resolve",
+  "spec": "lexicon_spec",
+  "version": "0.1.0"
+}

addedInput schema / x-vocab

Added value: +{
+  "address": "onchain.addressApi",
+  "network": "payment.network"
+}

AddedSep 8, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Beyond readOnlyHint, it discloses the 24-hour expiry, that the signing key holds no funds, the three result states with the meaning of 'partial' (a source could not be read), and the price of 6 cents per call. This is exactly the operational context annotations 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?

Front-loaded with the core purpose, then response contents, result semantics, and price in a logical order. It is a dense single paragraph with a little overlap between the opening clause and the later list of returned fields.

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?

Combined with an existing output schema and readOnlyHint, the description covers the remaining gaps an agent needs: cost, freshness/expiry, signature provenance, degenerate-case semantics, and how consumers validate the result.

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% and both parameters are documented there (EVM address format, CAIP-2 network id with default). The description says to send an EVM address but adds no format guidance and never mentions the network parameter, so it does not exceed the schema baseline.

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 deliverable: a signed statement on whether a wallet is clear of sanctions lists, naming both sources (OFAC SDN address list and on-chain sanctions oracle). It is easy to distinguish from siblings like wallet_risk or cleared_buyer because it specifies the signed, expiring artifact rather than a risk score.

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?

Gives clear usage context: 'the same screen every payer here passes before a settle' and 'A seller agent checks the signature and the expiry before it negotiates,' plus the instruction to 'Send an EVM address.' It does not name explicit alternatives or when-not conditions, so not a 5.

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

All ChainHelix for Machines 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?