boo-x402-mcp

Overview Schema Source Related Servers Discussions Admin

Contract safety scan

contract_safety

Scan a smart contract for dangerous patterns like proxy upgrades, owner privileges, and unverified source code before approving or interacting with it.

Instructions

Scans a smart contract for dangerous patterns: proxy/upgradeable, owner privileges, unverified source. Use before approving or interacting with an unknown contract.

PAID TOOL: up to $0.01 USDC per call (x402 on Base). Paid automatically from your configured wallet.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "address": "<address>",
      "chain": "<chain>"
    },
    "name": "contract_safety"
  }
}

Input Schema

Name	Required	Description	Default
`chain`	Yes	Chain: eth, bnb, base.
`address`	Yes	Contract address.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 11, 2026

TDQS

A4.3/5.0

Behavior4/5

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

No annotations provided, so description carries full burden. It discloses that it is a paid tool (up to $0.01 per call, automated payment), which is critical behavioral context. It does not mention whether mutations occur (assumed read-only), but the core behavior is well described.

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

Conciseness5/5

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

Two concise sentences plus a cost line, front-loaded with action and use case. No unnecessary words; every sentence adds value.

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 simple 2-param tool with no output schema, the description covers purpose, usage, and cost. It is fully adequate for an agent to understand and invoke correctly.

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%, so baseline is 3. The description does not add extra meaning beyond what the schema already provides for 'chain' and 'address'. It merely recontextualizes them in the scanning action.

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 clearly states it scans a smart contract for dangerous patterns (proxy/upgradeable, owner privileges, unverified source), with a specific use case 'before approving or interacting with an unknown contract'. This differentiates it from siblings like token_rugcheck or wallet_risk.

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 explicitly says when to use ('before approving or interacting with an unknown contract'), but does not mention when not to use or provide alternatives among sibling tools. Context is clear but exclusions are missing.

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