Skip to main content
Glama
verifystack-x402-mcp

verifystack-x402-mcp

Official

verifystack_verify_signature

Verify EVM EIP-191, EIP-712, ERC-1271 smart-wallet, and Ed25519 Solana signatures to confirm signer identity and validate signed messages or typed data.

Instructions

Paid x402 API ($0.005 USDC on Base): Deterministic cryptographic signature verifier for EVM EIP-191 personal_sign, EIP-712 typed data, ERC-1271 on-chain smart wallets, and Ed25519 (Solana).

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": {
      "scheme": "<scheme>",
      "signature": "<signature>"
    },
    "name": "verifystack_verify_signature"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainNo
schemeYes
messageNo
publicKeyNo
signatureYes
typedDataNo
expectedAddressNo
messageEncodingNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose genuinely useful behavior: this is a paid x402 endpoint at $0.005 USDC on Base, and it is deterministic. However, it never says what happens on an invalid signature (boolean result vs. error), whether ERC-1271 triggers an on-chain RPC lookup and thus added latency, or what payment/authorization flow the caller must complete before invoking.

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 well-packed sentence that front-loads cost and then the capability and scheme coverage. No filler or repetition; the only mild weakness is that cost precedes purpose, which is arguably the less important detail for selection.

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

Completeness2/5

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

For a tool with 8 parameters, a nested typedData object, no annotations, and no output schema, the description is thin. It omits which parameters each scheme requires, the meaning of the messageEncoding and chain options, and what the response looks like (valid/invalid, recovered address, error shapes) — all information the agent cannot get elsewhere.

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 0% across 8 parameters, so the description must compensate. It partially does by naming the four schemes, which implicitly map to parameter subsets (message/expectedAddress for personal_sign, typedData for EIP-712, expectedAddress for ERC-1271, publicKey for Ed25519), but it never states these mappings, nor explains messageEncoding, chain, or the nested typedData object.

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+resource ("Deterministic cryptographic signature verifier") and enumerates the exact supported schemes: EIP-191 personal_sign, EIP-712, ERC-1271, and Ed25519. An agent immediately knows this validates signatures rather than producing them, and the sibling tools (URL cleaning, token safety, liquidation sim) are unrelated enough that no explicit differentiation is needed.

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?

There is no guidance on when to choose this tool, when not to, or what alternatives exist for signature-adjacent tasks. The description only conveys pricing and scope; an agent must infer the use case entirely from the name and scheme list.

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