Skip to main content
Glama
verifystack-x402-mcp

verifystack-x402-mcp

Official

Smart Contract Firewall & EIP-1967 Proxy Inspector

verifystack_contract_intel
Read-onlyIdempotent

Inspect an EVM smart contract by address to detect EIP-1967 proxies, verify source code/ABI via Blockscout or Sourcify, and screen contract risks across five chains.

Instructions

Paid x402 API ($0.008 USDC on Base): Smart contract firewall & EIP-1967 proxy inspector via EVM RPC, Blockscout verification/ABI, and Sourcify across Base, Ethereum, Arbitrum, Optimism, and Polygon.

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>"
    },
    "name": "verifystack_contract_intel"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainNoTarget EVM chain (default: base)
addressYes0x EVM smart contract address to inspect

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.4.2
    • addedInput schema / additionalProperties
      Added value: +false
  2. Addedv0.4.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so the safety profile is covered. The description contributes the meaningful non-annotation fact that this is a paid x402 endpoint at $0.008 USDC on Base, which the agent must know before invoking. It stops short of describing what the inspection returns (proxy admin, implementation slot, verification status, risk verdict), leaving the core behavior opaque.

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?

A single dense sentence with no filler, though the pricing clause leads ahead of the actual purpose, which slightly buries the front-loaded value. Every element (cost, capability, data sources, chain coverage) carries information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With only two parameters, full schema coverage, and rich annotations, the input side is well covered. However, there is no output schema, and the description never indicates what a 'firewall' result looks like, so an agent cannot anticipate whether it receives a boolean verdict, a findings list, or raw proxy slots — a notable gap for a security-inspection 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 description coverage is 100%, so both parameters are already documented in structured form, and the description only restates the chain list and address nature. Baseline 3 applies since the description adds no syntax, format, or edge-case meaning beyond the schema.

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?

Names a specific resource and capability set: smart contract firewall checks plus EIP-1967 proxy inspection, backed by named data sources (EVM RPC, Blockscout, Sourcify). It does not explicitly distinguish itself from close siblings such as verifystack_token_safety or verifystack_decode_tx, so an agent must infer the boundary, but the purpose itself is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The only guidance offered is the pricing line ('$0.008 USDC on Base'), which is operational rather than selection guidance. It never says when to call this instead of token_safety, decode_tx, or wallet_profile, and gives no preconditions (e.g., that a verified source may be required for ABI-derived findings).

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