Skip to main content
Glama
Sign In
solanaprox-mcp

solanaprox-mcp

by solanaprox
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to solanaprox-mcp

No user-submitted related servers found.

    Related Servers

    • farebox-mcp

      fareboxfun
      A
      license
      Not graded
      quality
      C
      maintenance
      Crypto-native LLM gateway with OpenAI-compatible API and per-token USDC payments on Solana via the x402 protocol.
      9,415 npm
      MIT

    • lightningprox-mcp

      unixlamadev-spec
      A
      license
      A
      quality
      B
      maintenance
      Pay-per-request AI with Bitcoin Lightning: Claude, GPT, Gemini, DeepSeek, Mistral and more. Load a prepaid spend token, no account or provider API keys. You only pay for successful calls.
      5
      223 npm
      2
      MIT

    • farebox-mcp

      fareboxfun
      A
      license
      A
      quality
      C
      maintenance
      Connects Claude Desktop, Cursor, or any MCP-compatible client to 36+ frontier LLMs with automatic per-token payments in USDC on Solana.
      5
      17 npm
      MIT

    • obol

      halfkey
      A
      license
      A
      quality
      D
      maintenance
      Enables AI agents to access Solana wallet analytics, token data, and DeFi tools via pay-per-request USDC micropayments using the x402 protocol, without API keys or subscriptions.
      13
      62 npm
      MIT
    • PARANOID MCP

      PARANOID MCPofficial

      paranoiddotred
      A
      license
      A
      quality
      B
      maintenance
      Enables Claude Code, Cursor, or any MCP client to ask open and uncensored AI models questions privately, attaching a fresh zero-knowledge proof to each one so the gateway can verify it was paid for without learning who asked. Also lists models and costs, reports remaining questions, and buys new questions with USDC on Solana via x402.
      12
      4
      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 5 tools

    Disambiguation4/5

    Each tool has a clear primary purpose: catalog lookup (list_models), paid inference (ask_ai), account funds (check_balance), funding instructions (deposit_info), and history (get_activity). Minor overlap exists because check_balance also surfaces pending deposits and today's spend, which brushes against deposit_info and get_activity, but the boundaries remain understandable.

    Naming Consistency4/5

    Most names follow a verb_noun or verb_object pattern (list_models, ask_ai, check_balance, get_activity). The lone deviation is deposit_info, a noun phrase, and verb choice varies (list/get/check) for what are genuinely different resources, so the pattern is still readable.

    Tool Count5/5

    Five tools map cleanly onto the small surface of a paid inference proxy: discover models, call a model, check funds, fund the account, review activity. Nothing feels redundant or missing at this count.

    Completeness4/5

    The lifecycle of discover -> pay -> call -> verify balance/activity -> top up is fully covered, and withdrawals are explicitly out of scope. Minor gaps: no way to poll a deposit intent's status or manage/rotate the auth token, though users can work around these via check_balance and support.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources