presign-guard

Wallet approval audit ($0.02 via x402)

wallet_approvals

Read-only

Paid ($0.02 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): audit the open token approvals of a wallet on an EVM chain (base, ethereum, arbitrum, optimism, polygon, bsc) or on Solana, for example your agent's own wallet as a periodic check. Get back green/orange/red, a grade, a one-line summary and every approval with its spender. EVM, every ERC-20 allowance: flagged malicious (red), a plain wallet, on a doubt list, an unverified contract or an unlimited allowance to a spender not on the GoPlus trust list (orange), with a revoke.cash link. Solana, every SPL token delegation (Approve): a delegate on the OFAC SDN list (red), a delegate that is a plain wallet or an unlimited delegation (orange), with the token account to revoke on; Token-2022 tokens with a permanent delegate are listed too. NFT approvals are not covered. Same as GET /v1/approvals. 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
`chain`	Yes	Chain to audit: an EVM chain (ERC-20 allowances) or solana (SPL token delegations)
`address`	Yes	Wallet address (0x... on EVM, base58 on Solana)

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
`approvals`	No	Every open ERC-20 allowance (EVM) or SPL token delegation (Solana) with its spender
`one_liner`	No	One-line summary
`revokeUrl`	No	revoke.cash link for this wallet (EVM; null on Solana)

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

changedOutput schema / properties / approvals / 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"

Changed5 schema fields changedOct 15, 2026

changedInput schema / properties / address / description

Previous value: -"Wallet address (0x...)"New value: +"Wallet address (0x... on EVM, base58 on Solana)"

changedInput schema / properties / chain / description

Previous value: -"EVM chain to audit"New value: +"Chain to audit: an EVM chain (ERC-20 allowances) or solana (SPL token delegations)"

changedInput schema / properties / chain / enum

Previous value: -[
-  "base",
-  "ethereum",
-  "arbitrum",
-  "optimism",
-  "polygon",
-  "bsc"
-]New value: +[
+  "base",
+  "ethereum",
+  "arbitrum",
+  "optimism",
+  "polygon",
+  "bsc",
+  "solana"
+]

changedOutput schema / properties / approvals / description

Previous value: -"Every open ERC-20 allowance with its spender"New value: +"Every open ERC-20 allowance (EVM) or SPL token delegation (Solana) with its spender"

changedOutput schema / properties / revokeUrl / description

Previous value: -"revoke.cash link for this wallet"New value: +"revoke.cash link for this wallet (EVM; null on Solana)"

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

Changed1 schema field changedOct 9, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": true,
+  "properties": {
+    "accepts": {
+      "anyOf": [
+        {
+          "items": {
+            "additionalProperties": {},
+            "type": "object"
+          },
+          "type": "array"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Only on an unpaid call: the x402 payment options"
+    },
+    "approvals": {
+      "anyOf": [
+        {
+          "items": {
+            "additionalProperties": {},
+            "type": "object"
+          },
+          "type": "array"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Every open ERC-20 allowance with its spender"
+    },
+    "grade": {
+      "description": "SAFE, CAUTION, RISKY or AVOID",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "one_liner": {
+      "description": "One-line summary",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "reasons": {
+      "anyOf": [
+        {
+          "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"
+        }
+      ],
+      "description": "Why the verdict is what it is"
+    },
+    "receipt": {
+      "anyOf": [
+        {
+          "additionalProperties": {},
+          "description": "Signed receipt (EIP-191) binding the verdict to your arguments",
+          "type": "object"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Signed receipt (EIP-191) binding the verdict to your arguments"
+    },
+    "revokeUrl": {
+      "description": "revoke.cash link for this wallet",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "verdict": {
+      "anyOf": [
+        {
+          "description": "green: go ahead; orange: ask the user; red: do not sign or buy",
+          "enum": [
+            "green",
+            "orange",
+            "red"
+          ],
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "green: go ahead; orange: ask the user; red: do not sign or buy (absent on the payment requirement)"
+    },
+    "version": {
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "type": "object"
+}

AddedSep 26, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Despite readOnlyHint/openWorldHint annotations, it adds substantial context: a paid operation with a stated price and payment rails, the exact verdict model (green/orange/red), the specific red and orange criteria per chain family, the inclusion of revoke.cash links and Token-2022 permanent delegates, and an EIP-191 signed receipt bound to the arguments.

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

Conciseness3/5

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

Information density is high, but the purpose is deferred behind a long enumeration of payment chains and currencies, which pushes the verb far from the front. The single dense block would be more scannable with the core action stated first and the payment rails compressed.

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?

For a two-parameter read-only tool with an output schema, this covers everything an agent needs: cost and payment path, supported chains, what each verdict color means, what is excluded, and what accompanies the response. The color-criteria detail goes beyond the output schema rather than duplicating it.

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 documented with their enum values and address formats. The description reinforces that the chain choice determines ERC-20 allowance vs SPL delegation semantics but adds little beyond what the schema properties already say, matching the baseline 3.

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?

The description opens with a specific verb+resource combination ("audit the open token approvals of a wallet") and scopes it to EVM chains or Solana. It is clearly distinguishable from siblings like screen_wallet and token_verdict, which target wallets and tokens rather than approval allowances.

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?

It gives a concrete usage scenario ("for example your agent's own wallet as a periodic check") and states an explicit exclusion ("NFT approvals are not covered"), plus equivalence to GET /v1/approvals. It stops short of naming a sibling as the alternative for adjacent jobs, so routing is implied rather than prescribed.

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.