Skip to main content
Glama
Kishore-MK

AI42-MCP X402 Payment Server

by Kishore-MK
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to AI42-MCP X402 Payment Server

No user-submitted related servers found.

    Related Servers

    • SmartFetch

      Friezaaaa
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to reliably fetch public web URLs and extract clean, agent-ready text, Markdown, links, and metadata, with automatic browser fallback and optional x402 payment support.
      -
    • x1-baas-mcp by MicrostormHK

      x1-baas-mcpofficial

      MicrostormHK
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to scrape any URL through a stealth browser with anti-bot bypass, returning clean Markdown, and optionally pay per request via x402 micropayments.
      1
      MIT
    • @bridgenode/mcp by bridgenode-ai

      @bridgenode/mcpofficial

      bridgenode-ai
      A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to make pay-as-you-go AI inference requests through x402 with automatic Solana USDC payments, no API keys or registration, while enforcing configurable spending limits.
      3
      61 npm
      1
      MIT No Attribution

    • x402-md-mcp

      Bigabou007-dev
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables extracting clean Markdown from any webpage by paying $0.005 USDC per call via the x402 protocol, with automatic wallet-based payment settlement.
      2 npm
      MIT

    • mcp-x402

      Diogoup26
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables per-request paid AI analysis of public URLs, condition verification, and AI consultation via x402 micropayments on Base, with no account or subscription.
      1 npm
      -
    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

    B3.4/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose with no ambiguity: fetch-with-payment handles data retrieval with payment automation, get-balance checks wallet balance, get-payment-history views session payments, and set-payment-limit configures spending limits. The descriptions clearly differentiate their functions, making misselection unlikely.

    Naming Consistency4/5

    The tool names follow a mostly consistent verb_noun pattern (e.g., fetch-with-payment, get-balance, get-payment-history, set-payment-limit), with all using hyphens for separation. However, fetch-with-payment uses a compound verb (fetch-with) that slightly deviates from the simpler verb forms in the others, but overall the naming is predictable and readable.

    Tool Count5/5

    With 4 tools, the count is well-scoped for a payment server focused on data fetching and wallet management. Each tool earns its place by covering essential operations: data retrieval, balance checking, payment tracking, and limit setting, without being overly complex or sparse.

    Completeness4/5

    The tool surface covers core payment and wallet management workflows effectively, including data fetching with payment handling, balance inquiries, payment history, and limit configuration. A minor gap exists in lacking a tool for direct payment initiation or refunds, but agents can work around this using the existing tools for most scenarios.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources