Skip to main content
Glama
Sign In
clear-signing-mcp

clear-signing-mcp

Official
by B3Pay
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to clear-signing-mcp

No user-submitted related servers found.

    Related Servers

    • Web3MCP

      Team-Managed
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to discover the tools EVM protocols publish under their own ENS names, read their contracts, and simulate writes shown with exact balance changes — leaving signing to the user's own wallet. No per-protocol server and no key ever held by the agent.
      Apache 2.0

    • CryptoMCP

      RMAAPK
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to query multichain balances, inspect smart contracts, and draft DeFi interactions while enforcing anti-drainer protections such as approval blocking, destination whitelisting, spend caps, and human approval gates.
      11 npm
      MIT

    • Lucent

      beepboop2025
      A
      license
      A
      quality
      A
      maintenance
      MCP server that enables AI signing agents to pre-flight transactions by checking ERC-7730 descriptor safety, explaining function semantics, and scanning contracts for danger primitives.
      2
      4
      MIT

    • WETH

      ayushkumar2601
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to analyze Ethereum wallets, simulate transactions, and draft transfers with deterministic policy and risk scoring, requiring human approval before on-chain execution.
      12 npm
      ISC

    • Read Before Sign

      shelbygrayman
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to turn raw calldata, transaction objects, JSON-RPC requests, EIP-712 typed data and personal_sign messages into short plain-English briefings covering what a request asks for, which risky allowances or permissions need attention, and what could not be verified. Runs entirely offline with no RPC, wallet, API key or safety verdict, using three read-only tools exposed to any MCP client.
      MIT
    Deploy Server
    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

    TDQS

    A4.3/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool targets a clearly distinct aspect of clear-signing preflight: contract-level descriptor/attestation status, transaction explanation, EIP-712 signature explanation, and state simulation. Although clear_signing_status and explain_transaction both mention attestation status, their scopes are different enough that an agent can select correctly.

    Naming Consistency4/5

    All tool names use snake_case and are readable and predictable. Three follow a verb_noun pattern (explain_transaction, explain_signature, simulate_transaction), while clear_signing_status is a noun phrase, which is a minor deviation but not confusing.

    Tool Count5/5

    Four tools is well-scoped for a focused read-only clear-signing preflight server. Each tool earns its place by covering a distinct step: status checking, transaction explanation, signature explanation, and simulation.

    Completeness5/5

    The surface covers the core lifecycle: check descriptor/attestation/source status, explain transactions including EIP-5792 batches, explain EIP-712 signatures, and simulate calls against current state. No obvious operational gap remains for the stated read-only clear-signing purpose.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources