Skip to main content
Glama
verifystack-x402-mcp

verifystack-x402-mcp

Official

verifystack_token_safety

Audit a token's contract security and DEX liquidity risk before trading by aggregating GoPlus checks, Honeypot.is simulation, and DexScreener liquidity data across supported chains.

Instructions

Paid x402 API ($0.008 USDC on Base): Pre-trade token security and DEX liquidity risk audit aggregating GoPlus Security, Honeypot.is simulation, and DexScreener liquidity.

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": {
      "chain": "<chain>",
      "address": "<address>"
    },
    "name": "verifystack_token_safety"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainYes
addressYesToken contract address (EVM 0x... or Solana Base58 mint)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose important behavior: this is a paid x402 endpoint costing $0.008 USDC on Base, and it performs simulation plus aggregation. It stops short of describing what the audit returns (verdict, score, findings) or any latency/caching behavior, leaving meaningful gaps for a no-annotation tool.

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 compact sentence with zero waste, front-loaded with cost and then the core capability. Efficient and readable, though the parenthetical pricing prefix slightly delays the primary action.

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 no output schema and no annotations, the description should say more about what comes back from the audit and how the x402 payment flow works. Naming the aggregated data sources partially compensates, but an agent cannot tell what the result looks like before calling.

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 50%: the chain enum self-documents allowed networks and the address field explains the EVM/Base58 formats. The description adds no additional meaning about either parameter, so it neither compensates for nor extends 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?

States a specific verb and resource: a 'pre-trade token security and DEX liquidity risk audit' and names the three aggregated data sources (GoPlus, Honeypot.is, DexScreener). Purpose is unmistakable and distinct from sibling concerns like URL cleaning or signature verification, though it doesn't explicitly contrast with them.

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

Usage Guidelines3/5

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

'Pre-trade' implies the timing of use (before trading a token), which is useful context. However, there are no explicit when-not-to-use conditions, no prerequisites (e.g., payment setup), and no named alternatives among siblings.

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