402-mcp
Related Servers
Alternatives to 402-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceMCP 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.179MIT
- AlicenseNot gradedqualityDmaintenanceMCP server for the x402 protocol that lets AI agents discover and call payment-gated HTTP APIs automatically.344 npmApache 2.0
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to discover, call, and pay for existing HTTP APIs over MCP with x402 paywalls, non-custodial settlement, and no code changes to the backend.328 npm66Apache 2.0
- AlicenseAqualityCmaintenanceEnables AI agents to discover and pay for x402-gated HTTP APIs, handling 402 Payment Required flows with local signing. Supports EVM and Solana with non-custodial wallet management.364 npmMIT

Loop MCP DualRailofficial
AlicenseNot gradedqualityBmaintenanceEnables 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 npmMIT- FlicenseAqualityBmaintenanceMCP server for a live x402 payment gateway on Base (USDC). Lets AI agents discover, preview for free, then pay per call — with prepaid gasless payments, signed receipts, and delta delivery.7-
TDQS
Scored across 14 tools
Several tools overlap: l402-discover and l402-fetch-preview both probe a URL for cost without paying, l402-balance/is a subset of l402-credentials and l402-wallet-dashboard, and l402-service-directory explicitly wraps l402-search. Descriptions do help differentiate (cached balance vs. credential list vs. dashboard, endpoint probe vs. URL preview), but an agent can still hesitate between the near-synonymous probing and balance tools.
All 14 tools share a clean l402- prefix and kebab-case, giving a highly predictable family. Deviations are minor: some names are verbs (fetch, pay, search) while others are nouns (config, credentials, balance, service-directory), so the pattern is consistent in style but not strictly verb_noun.
14 tools is well within the ideal range and each maps to a distinct payment-lifecycle step: introspect, discover, preview, pay, fetch, reconcile, store token, redeem cashu, buy credits, and browse. No tool feels like filler for the apparent L402 wallet/payment scope.
The surface covers the full pay flow end to end (discover/preview, pay/fetch, reconcile, credential and balance management, credit purchase, Cashu redemption). Minor gaps exist, such as no explicit tool to delete or revoke stored credentials or to clear/reset spend limits, but core workflows are fully supported.