Skip to main content
Glama
LeviEdwards

mcp-l402-directory

by LeviEdwards
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to mcp-l402-directory

No user-submitted related servers found.

    Related Servers

    • Lightning Enable MCP

      refined-element
      A
      license
      A
      quality
      B
      maintenance
      MCP server that enables AI agents to make autonomous Bitcoin Lightning Network payments using the L402 protocol. Agents can pay for API access, purchase resources, and complete transactions without human intervention — invoice comes in, sats go out, done.
      17
      9
      MIT

    • x402-mcp

      merkleworks
      A
      license
      Not graded
      quality
      F
      maintenance
      MCP server for the x402 protocol that lets AI agents discover and call payment-gated HTTP APIs automatically.
      82 npm
      Apache 2.0
    • mpp32-mcp-server by MPP32

      mpp32-mcp-serverofficial

      MPP32
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server that allows AI agents to discover and pay for thousands of APIs (x402 on Solana/Base) using a single key, with automatic payment handling and a federated catalog of machine-payable endpoints.
      234
      MIT

    • xpay

      xona-labs
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server for agentic commerce, enabling AI agents to discover services, make x402 payments with USDC across multiple chains, and manage crypto wallets and token swaps.
      119 npm
      1
      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/5.0

    Scored across 6 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes: search, category listing, recent additions, verified services, and descriptor retrieval. The only mild overlap is between get_l402_service and get_service_descriptor, but their descriptions clarify human-readable details vs. machine-readable metadata.

    Naming Consistency5/5

    All tool names follow a consistent snake_case verb_noun pattern, with verbs like search, list, and get. The naming style is uniform and predictable across the entire set.

    Tool Count5/5

    Six tools is an appropriate scope for a read-only directory server covering search, filtering, and detail retrieval. Each tool serves a clear purpose without redundancy or bloat.

    Completeness5/5

    The tool surface covers the full directory workflow: searching, listing by category, retrieving service details, browsing recent additions, filtering verified services, and fetching machine-readable descriptors. No obvious gaps exist for this read-only directory use case.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources