Skip to main content
Glama
vera-agent-dev

x402-tools

by vera-agent-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to x402-tools

No user-submitted related servers found.

    Related Servers

    • dyoe-agent-tools-mcp

      bjyoe2016
      A
      license
      A
      quality
      B
      maintenance
      Trust layer for AI agents: 22 pay-per-call x402 tools for scam and fraud checks, payment pre-flight, wallet screening, policy approvals, contact extraction and company research. Free preview with no wallet; paid calls settle in USDC on Base.
      22
      MIT

    • Money Reactor

      makar52nn-crypto
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents and bots to buy per-call data and intelligence — token safety verdicts, prices, news, weather, web-to-text, and research dossiers — without signup or API keys, since each call is authenticated by an on-chain USDC payment on Base via the x402 protocol. Clients hit any paid endpoint, receive an HTTP 402 challenge, sign an EIP-3009 transfer authorization, and retry to get the data.
      1
      MIT

    • x402 MCP Payment

      motok2031
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to access paid content by integrating cryptocurrency payments through the x402 protocol, allowing LLMs to verify payments and retrieve paid resources automatically.
      1
      -
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    A3.8/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool addresses a completely distinct task: fetching product catalog, checking package trust, and predicting PR merges. There is zero functional overlap, so an agent would never confuse which tool to select.

    Naming Consistency3/5

    Naming mixes conventions: 'list_products' follows verb_noun, while 'package_trust_check' and 'repo_merge_lookup' are noun_verb (object+verb). All use underscores, but the verb placement is inconsistent, which slightly reduces predictability.

    Tool Count4/5

    With only 3 tools, the server is lean and each tool serves a clear, standalone purpose. The count is appropriate for a specialized utility server, though it borders on minimal.

    Completeness4/5

    The tools are independent utilities, not part of a lifecycle workflow, so there are no obvious missing CRUD operations. Each tool appears self-contained, though the domain is broad and could potentially support additional related functions (e.g., package details, repo history), but nothing critical is missing.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources