onchain-risk-mcp

scan_onchain_address_risk

Read-onlyIdempotent

Audits any Base EVM 0x contract or Solana SPL Mint for proxy patterns, GoPlus honeypot flags, and freeze authority. WHEN TO USE: Call scan_onchain_address_risk when your task requires deterministic onchain-risk analysis for address; use get_agent_wallet_status to check your remaining free trial quota or prepaid balance. WHEN NOT TO USE: Do not use for unrelated domains or binary media. PARAMETER INTERACTIONS: Pass the target address as a non-empty string; omit agent_id and tx_hash during your 5 free trial calls, or supply agent_id (agd_pass_...) / tx_hash for paid execution. Read-only and idempotent; results are cached for 1 hour (<5ms cache hit). $0.01 per call. Pricing: the first 5 calls per agent_id are free and failed calls are never charged. After 5 calls, the tool returns a payment-required quote (not a fatal error) with a $2 Stripe top-up link and Base/Solana USDC addresses; complete payment, then retry with your agd_pass_ key in agent_id or pass tx_hash. Example: scan_onchain_address_risk(address='example')

Input Schema

Name	Required	Description
`address`	Yes	0x EVM contract/wallet address on Base or Solana Base58 SPL Mint address.
`tx_hash`	No	Optional on-chain Base Mainnet (0x...) or Solana SPL USDC transaction hash. Omit unless settling an individual call directly on-chain instead of using an agd_pass_ key in agent_id.
`agent_id`	No	Optional agent identifier or prepaid agd_pass_ session key. Omit during your 5 free trial calls to use an ID automatically derived from your client IP, or pass your agd_pass_ key after topping up.

Output Schema

Name	Required	Description
`data`	No	Structured tool output payload.
`status`	Yes	Execution status ('ok' or 'payment_required').
`roi_proof`	No	Token compression and cost-savings verification metrics.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 19, 2026
- addedInput schema / examples
```
Added value: +[
+  {
+    "address": "example"
+  }
+]
```

Changed8 schema fields changedOct 19, 2026

changedInput schema / additionalProperties
```
Previous value: -trueNew value: +false
```

changedInput schema / properties / agent_id / description

Previous value: -"Your agent ID, or the agd_pass_ key you got from a payment. It tracks your free calls and credit, so treat it like a password. Omit it to use an ID derived from your IP and client."New value: +"Optional agent identifier or prepaid agd_pass_ session key. Omit during your 5 free trial calls to use an ID automatically derived from your client IP, or pass your agd_pass_ key after topping up."

addedInput schema / properties / agent_id / maxLength
```
Added value: +256
```
addedInput schema / properties / agent_id / minLength
```
Added value: +1
```

changedInput schema / properties / tx_hash / description

Previous value: -"Use only after paying on-chain: the Base (0x...) or Solana USDC transfer hash. It is verified on-chain before the call runs, and any overpayment is returned as an agd_pass_ credit key."New value: +"Optional on-chain Base Mainnet (0x...) or Solana SPL USDC transaction hash. Omit unless settling an individual call directly on-chain instead of using an agd_pass_ key in agent_id."

addedInput schema / properties / tx_hash / maxLength
```
Added value: +256
```
addedInput schema / properties / tx_hash / minLength
```
Added value: +10
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "data": {
+      "description": "Structured tool output payload.",
+      "type": "object"
+    },
+    "roi_proof": {
+      "description": "Token compression and cost-savings verification metrics.",
+      "type": "object"
+    },
+    "status": {
+      "description": "Execution status ('ok' or 'payment_required').",
+      "type": "string"
+    }
+  },
+  "required": [
+    "status"
+  ],
+  "type": "object"
+}

Changed3 schema fields changedOct 16, 2026

changedInput schema / properties / address / description

Previous value: -"0x EVM contract/wallet address on Base or Solana Base58 SPL Mint address"New value: +"0x EVM contract/wallet address on Base or Solana Base58 SPL Mint address."

changedInput schema / properties / agent_id / description

Previous value: -"Optional Agent ID or Session Pass (agd_pass_...)"New value: +"Your agent ID, or the agd_pass_ key you got from a payment. It tracks your free calls and credit, so treat it like a password. Omit it to use an ID derived from your IP and client."

changedInput schema / properties / tx_hash / description

Previous value: -"Optional Base (0x...) or Solana USDC tx hash"New value: +"Use only after paying on-chain: the Base (0x...) or Solana USDC transfer hash. It is verified on-chain before the call runs, and any overpayment is returned as an agd_pass_ credit key."

Changed3 schema fields changedOct 16, 2026

changedInput schema / additionalProperties
```
Previous value: -falseNew value: +true
```

addedInput schema / properties / agent_id

Added value: +{
+  "description": "Optional Agent ID or Session Pass (agd_pass_...)",
+  "type": "string"
+}

addedInput schema / properties / tx_hash

Added value: +{
+  "description": "Optional Base (0x...) or Solana USDC tx hash",
+  "type": "string"
+}

Changed3 schema fields changedOct 15, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
- addedInput schema / properties / address / maxLength
```
Added value: +99999
```
- addedInput schema / properties / address / minLength
```
Added value: +1
```

Changed1 schema field changedOct 14, 2026

changedInput schema / properties / address / description

Previous value: -"0x EVM wallet or smart contract address on Base/Ethereum to scan for rug/security risks"New value: +"0x EVM contract/wallet address on Base or Solana Base58 SPL Mint address"

First observedOct 13, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, so the bar is lower; the description still adds substantial operational context: 1-hour result caching with <5ms cache hits, deterministic analysis, and a full pricing/trial model (5 free calls, failed calls never charged, payment-required quote rather than fatal error). It is dense but genuinely informative beyond the 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?

Front-loaded with what the tool does before the usage and payment detail, and every section is labeled. It is on the long side and restates the payment/trial flow twice, which costs it a point.

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?

With an output schema present, return values need not be explained, and safety/idempotency are covered by annotations. The description completes the picture with the pricing gate, retry path, and parameter conditions an agent needs to invoke successfully.

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 schema already defines each parameter, but the description adds conditional routing logic the schema only hints at: omit `agent_id`/`tx_hash` during the 5 free trial calls, and supply `agent_id` (`agd_pass_...`) or `tx_hash` for paid execution via on-chain settlement.

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 ('Audits any Base EVM 0x contract or Solana SPL Mint') and enumerates exactly what is checked (proxy patterns, GoPlus honeypot flags, freeze authority). It also names the sibling tool for a different need, so the agent can tell them apart without opening schemas.

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?

Explicit WHEN TO USE and WHEN NOT TO USE sections, plus a direct routing rule: use `get_agent_wallet_status` to check quota or prepaid balance. Exclusions ('unrelated domains or binary media') are stated rather than inferred.

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

All onchain-risk-mcp 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?