Skip to main content
Glama
Sign In
smartflow-verify-mcp

smartflow-verify-mcp

by smartflowproai-lang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to smartflow-verify-mcp

No user-submitted related servers found.

    Related Servers

    • automaton-onchain-tools

      povrouyre-wq
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to access pay-per-call onchain and URL safety APIs over MCP, covering transaction explanations, token approval checks, address inspection, contract risk heuristics, URL safety, gas snapshots, ENS resolution, calldata decoding, and wallet portfolio data. Payments are handled per call in USDC on Base via x402, with no signup or API key required.
      1
      MIT

    • a2a-x402-mcp-services

      Disseveru
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables agents to access production-grade paid MCP tools with real on-chain x402 v2 settlement, including EVM wallet risk scoring, payload normalization, and facilitator discovery, all discoverable via Bazaar-compatible metadata.
      MIT

    • x402farm-mcp

      laurenthalbrun
      A
      license
      Not graded
      quality
      F
      maintenance
      MCP server that provides AI agents with pay-per-call access to a suite of tools (honeypot check, token market, DeFi yields, etc.) via USDC on Base using the x402 protocol.
      5 npm
      MIT

    • app.vercel.baselens

      elevatedesign
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to query Base on-chain data such as balances, token metadata, transactions, gas, names, prices, transfers, and contract details through paid MCP tools using x402 payments.
      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.7/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: creating a payable audit order, polling that order's status, and retrieving network decomposition data. The descriptions reinforce the boundaries with explicit sequencing instructions, leaving no realistic chance of misselection.

    Naming Consistency5/5

    All three names follow a predictable verb_noun pattern: get_audit_order_status, get_network_decomposition, and order_endpoint_audit. The verbs differ naturally by action, but there is no mixing of casing or naming styles.

    Tool Count5/5

    Three tools is well-scoped for a focused verification-and-ordering server. Each tool earns its place: one read for decomposition, one order creation, and one status poll for the audit lifecycle.

    Completeness4/5

    The audit-order lifecycle is covered through creation and status polling, and decomposition data is separately available. Minor gaps exist, such as no order listing, cancellation, or direct report retrieval, but expiry and email delivery provide reasonable workarounds.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources