presign-guard

Wallet sanctions screen ($0.01 via x402)

screen_wallet

Read-only

Paid ($0.01 via x402 in USDC on Base, Solana, Monad, Polygon, Arbitrum, Avalanche, Algorand or Stellar, in RLUSD on the XRP Ledger or in USD₮0 on X Layer): call this before your agent pays an address, or before accepting money from one. Send any chain's wallet address (EVM 0x..., Solana, Tron, Bitcoin, XRP Ledger, Algorand, or another currency OFAC lists). Get back green/orange/red: red SANCTIONED_ADDRESS with the SDN entry (name, programs, currency) when the address is on the OFAC SDN list, red or orange when GoPlus reports theft, phishing, laundering or mixer use (EVM). Never pay or accept funds on red. The answer carries a signed receipt (EIP-191, bound to your arguments) that proves later which verdict you got.

Input Schema

Name	Required	Description	Default
`address`	Yes	The wallet address to screen, any chain: EVM (0x...), Solana, Tron, Bitcoin, XRP Ledger, Algorand, or another currency OFAC lists

Output Schema

Name	Required	Description
`grade`	No
`accepts`	No	Only on an unpaid call: the x402 payment options
`reasons`	No
`receipt`	No
`verdict`	No	green: go ahead; orange: ask the user; red: do not sign or buy (absent on the payment requirement)
`version`	No
`one_liner`	No	One-line summary
`sanctions`	No	OFAC SDN result: listed, matches (name, programs, currency), published

Schema Changelog

Changes observed during successful MCP inspections.

Changed11 schema fields changedOct 29, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```
changedOutput schema / additionalProperties
```
Previous value: -trueNew value: +{}
```

changedOutput schema / properties / accepts / anyOf

Previous value: -[
-  {
-    "items": {
-      "additionalProperties": {},
-      "type": "object"
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "items": {
+      "additionalProperties": {},
+      "propertyNames": {
+        "type": "string"
+      },
+      "type": "object"
+    },
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]

addedOutput schema / properties / grade / anyOf

Added value: +[
+  {
+    "description": "SAFE, CAUTION, RISKY or AVOID",
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / properties / grade / description
```
Removed value: -"SAFE, CAUTION, RISKY or AVOID"
```
removedOutput schema / properties / grade / type
```
Removed value: -[
-  "string",
-  "null"
-]
```

changedOutput schema / properties / reasons / anyOf

Previous value: -[
-  {
-    "description": "Why the verdict is what it is",
-    "items": {
-      "additionalProperties": true,
-      "properties": {
-        "code": {
-          "description": "Reason code, e.g. SPENDER_FLAGGED, UNLIMITED_ALLOWANCE, TOKEN_HONEYPOT",
-          "type": "string"
-        },
-        "severity": {
-          "description": "info, warn or critical",
-          "type": "string"
-        },
-        "subject": {
-          "description": "The address or item the reason is about (null or absent when it is about the whole request)",
-          "type": [
-            "string",
-            "null"
-          ]
-        }
-      },
-      "required": [
-        "code"
-      ],
-      "type": "object"
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "description": "Why the verdict is what it is",
+    "items": {
+      "additionalProperties": {},
+      "properties": {
+        "code": {
+          "description": "Reason code, e.g. SPENDER_FLAGGED, UNLIMITED_ALLOWANCE, TOKEN_HONEYPOT",
+          "type": "string"
+        },
+        "severity": {
+          "description": "info, warn or critical",
+          "type": "string"
+        },
+        "subject": {
+          "description": "The address or item the reason is about (null or absent when it is about the whole request)",
+          "type": [
+            "string",
+            "null"
+          ]
+        }
+      },
+      "required": [
+        "code"
+      ],
+      "type": "object"
+    },
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / properties / reasons / description
```
Removed value: -"Why the verdict is what it is"
```

changedOutput schema / properties / receipt / anyOf

Previous value: -[
-  {
-    "additionalProperties": {},
-    "description": "Signed receipt (EIP-191) binding the verdict to your arguments",
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": {},
+    "description": "Signed receipt (EIP-191) binding the verdict to your arguments",
+    "propertyNames": {
+      "type": "string"
+    },
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / properties / receipt / description

Removed value: -"Signed receipt (EIP-191) binding the verdict to your arguments"

changedOutput schema / properties / sanctions / anyOf

Previous value: -[
-  {
-    "additionalProperties": {},
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": {},
+    "propertyNames": {
+      "type": "string"
+    },
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

Changed1 schema field changedOct 12, 2026

changedOutput schema / properties / reasons / anyOf

Previous value: -[
-  {
-    "description": "Why the verdict is what it is",
-    "items": {
-      "additionalProperties": true,
-      "properties": {
-        "code": {
-          "description": "Reason code, e.g. SPENDER_FLAGGED, UNLIMITED_ALLOWANCE, TOKEN_HONEYPOT",
-          "type": "string"
-        },
-        "severity": {
-          "description": "info, warn or critical",
-          "type": "string"
-        },
-        "subject": {
-          "description": "The address or item the reason is about",
-          "type": "string"
-        }
-      },
-      "required": [
-        "code"
-      ],
-      "type": "object"
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "description": "Why the verdict is what it is",
+    "items": {
+      "additionalProperties": true,
+      "properties": {
+        "code": {
+          "description": "Reason code, e.g. SPENDER_FLAGGED, UNLIMITED_ALLOWANCE, TOKEN_HONEYPOT",
+          "type": "string"
+        },
+        "severity": {
+          "description": "info, warn or critical",
+          "type": "string"
+        },
+        "subject": {
+          "description": "The address or item the reason is about (null or absent when it is about the whole request)",
+          "type": [
+            "string",
+            "null"
+          ]
+        }
+      },
+      "required": [
+        "code"
+      ],
+      "type": "object"
+    },
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]

AddedOct 11, 2026

TDQS

A4.1/5.0

Behavior5/5

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

Annotations only declare readOnly and openWorld; the description adds substantial behavior beyond that: a $0.01 x402 charge with the exact accepted assets and chains, the green/orange/red verdict semantics, what a red verdict contains (SDN entry with name, programs, currency), and an EIP-191 signed receipt bound to the arguments. These are material facts an agent cannot get from 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?

Dense but mostly front-loaded and information-bearing. The opening payment-rail parenthetical is long and sits ahead of the actual purpose, and the two chain lists (payment rails vs. screenable addresses) can momentarily blur together, but almost every clause earns its place.

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?

Covers payment mechanics, trigger conditions, output verdict tiers, red-flag semantics, and receipt provenance, and an output schema exists to carry the return structure. Nothing an agent needs to call this correctly is missing, even for an open-world paid tool.

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 coverage is 100% for the single 'address' parameter, so the schema already documents chain formats and length bounds. The description repeats the same chain enumeration without adding syntax, normalization, or format guidance beyond what the schema states, making the baseline 3 appropriate.

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?

States a specific verb and resource: screen a wallet address against OFAC SDN and GoPlus risk signals, returning green/orange/red. The purpose is unambiguous, but it never names or contrasts the sibling tools (wallet_approvals, token_verdict, presign_check), so the agent must infer why this is the right screen versus those.

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 an explicit trigger: 'call this before your agent pays an address, or before accepting money from one', plus the decision rule 'Never pay or accept funds on red'. That is clear when-to-use context, but there is no when-not guidance and no named alternative tool for adjacent checks.

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

All presign-guard 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.