Skip to main content
Glama
forgesworn

402-mcp

by forgesworn
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to 402-mcp

No user-submitted related servers found.

    Related Servers

    • Lightning Enable MCP

      refined-element
      A
      license
      A
      quality
      C
      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
      D
      maintenance
      MCP server for the x402 protocol that lets AI agents discover and call payment-gated HTTP APIs automatically.
      144 npm
      Apache 2.0
    • Loop MCP DualRail by Loop-XXI

      Loop MCP DualRailofficial

      Loop-XXI
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to pay for MCP tool calls using either Bitcoin/Lightning (L402) or USDC (x402) rails, with unified settlement and a 21% discount for Bitcoin payments.
      32 npm
      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

    A3.9/5.0

    Scored across 14 tools

    Disambiguation3/5

    Most tools have concrete, well-scoped jobs, but several read-only/status tools overlap: l402-credentials, l402-balance, l402-config, and l402-wallet-dashboard all expose balances, credentials, or wallet state, and l402-discover overlaps with l402-fetch-preview for discovering pricing. The descriptions help, but an agent could easily call the wrong one.

    Naming Consistency3/5

    All names share the l402- prefix and lowercase kebab-case, but the grammatical pattern is mixed: verb-noun actions like l402-store-token and l402-buy-credits sit beside bare verbs like l402-pay and l402-fetch and nouns like l402-config and l402-credentials. This is readable but not a predictable verb_noun convention.

    Tool Count4/5

    14 tools is within a reasonable range for an L402 payment server, and most tools serve a distinct workflow step. The count is slightly high because the status/introspection surface could be consolidated and l402-service-directory is essentially a wrapper around l402-search.

    Completeness4/5

    The payment lifecycle is well covered: discover, preview, fetch, pay, store tokens, buy credits, redeem cashu, and reconcile uncertain payments. Minor gaps remain, such as no explicit credential deletion/revocation or payment history beyond cached balances, but agents can work around these for core flows.

    Maintenance

    ActivityActive
    ResponsivenessUnresponsive

    Resources