Skip to main content
Glama
forgemeshlabs

x402 Utility

by forgemeshlabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to x402 Utility

  • Anomaly Tracker MCP

    forgemeshlabs
    A
    license
    A
    quality
    B
    maintenance
    Blockchain event sequence anomaly detection MCP server using NASA-derived sequence mining, providing human-readable story labels and anomaly scores for financial event windows.
    16
    76 npm
    MIT

Related Servers

  • oom-x402-mcp by OrdersOfMagnitudeLLC

    oom-x402-mcpofficial

    OrdersOfMagnitudeLLC
    F
    license
    Not graded
    quality
    B
    maintenance
    MCP server exposing 1,000+ pay-per-call API endpoints across agent infrastructure (memory, coordination, secrets, verification), data, compute, finance, weather, geography, and reference categories — payments via x402 protocol in USDC on Base.
    -
  • opendexter by Dexter-DAO

    opendexterofficial

    Dexter-DAO
    A
    license
    Not graded
    quality
    C
    maintenance
    An MCP server that enables AI agents to search, pay for, and call paid APIs using the x402 protocol, with automatic USDC settlement.
    2
    MIT
  • x402-mcp by x402node

    x402-mcpofficial

    x402node
    A
    license
    C
    quality
    D
    maintenance
    MCP server bringing 100+ x402-paid APIs to AI agents (Claude, Cursor, MCP-aware clients). Auto-discovers tools from CDP Bazaar; handles USDC micropayments on Base.
    100
    33 npm
    1
    MIT
  • gatefareio/mcp-server by gatefareio

    gatefareio/mcp-serverofficial

    gatefareio
    A
    license
    A
    quality
    C
    maintenance
    Marketplace MCP for paid HTTP APIs. Pay per call in USDC on Base via the open x402 standard — non-custodial. 13 tools for discovery, buying, and publishing APIs.
    7
    25 npm
    2
    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.4/5.0

Scored across 6 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: list_capabilities for browsing the catalog, search_capabilities for keyword search, get_endpoint_spec for detailed specifications, call_endpoint for executing routes, daily_402 for a curated daily pick, and agent_service_directory for service-level metadata. There is no ambiguity between them, and the descriptions reinforce their unique roles.

Naming Consistency4/5

The first four tools follow a consistent verb_noun pattern (list_capabilities, search_capabilities, get_endpoint_spec, call_endpoint), but daily_402 and agent_service_directory abandon the verb prefix, creating a minor inconsistency. All names use snake_case and are otherwise readable, so the deviation is not jarring.

Tool Count5/5

With 6 tools, the server is well-scoped for its purpose as a gateway to a large endpoint catalog. The count is within the ideal range and each tool covers a necessary step in the discovery-to-execution workflow, with no redundancy or obvious bloat.

Completeness5/5

The tool set fully covers the core lifecycle: browse (list_capabilities), find (search_capabilities), inspect (get_endpoint_spec), and execute (call_endpoint). Additional tools for daily highlights and service directory add value without leaving any critical gaps for the intended use case.

Maintenance

ActivityMaintained
ResponsivenessNo issues

Resources