Skip to main content
Glama
Modexia

Modexia

Official
by Modexia
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to Modexia

No user-submitted related servers found.

    Related Servers

    • pay-mcp

      MonadWorks
      A
      license
      A
      quality
      D
      maintenance
      An MCP server for USDC payments on Base, enabling AI agents to check balances, send payments, generate payment requests, and view transaction history.
      4
      1
      MIT
    • ShieldZ Crypto Payments by ShieldZCash

      ShieldZ Crypto Paymentsofficial

      ShieldZCash
      A
      license
      A
      quality
      B
      maintenance
      Keyless crypto payments for AI agents. One MCP call turns any wallet address into a non-custodial crypto payment link or tip jar, no API key and no account, with funds settling straight to your wallet at a 0% platform fee (USDC/USDT, BTC, LTC, DASH, DOGE, ZCASH).
      3
      28 npm
      MIT

    • remit.md MCP Server

      pay-skill
      A
      license
      Not graded
      quality
      F
      maintenance
      Enables AI agents to perform financial transactions such as direct payments, escrows, and bounty management using natural language with zero code integration. It provides a comprehensive suite of tools for fund streaming, subscriptions, and reputation tracking to facilitate secure agent-to-agent commerce.
      8 npm
      MIT

    • maxia-mcp

      majorelalexis-stack
      A
      license
      Not graded
      quality
      C
      maintenance
      AI-to-AI marketplace MCP server with 46 tools — swap 65+ crypto tokens on 7 chains, rent GPUs, trade 25 tokenized stocks, on-chain escrow (Solana + Base), DeFi yields, sentiment analysis, wallet monitoring, and image generation. Supports USDC payments across 14 blockchains.
      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.5/5.0

    Scored across 18 tools

    Disambiguation4/5

    Tools are largely distinct, covering different payment mechanisms (standard transfers, cross-chain, channels, intents, nanopayments). Some overlap exists between transfer and submit_intent, and between smart_fetch and nanopay, but descriptions clarify their different triggers and protocols.

    Naming Consistency4/5

    Most tools follow a consistent verb_noun or resource-specific pattern (get_*, list_*, *channel, nanopay_*). Minor deviations like 'smart_fetch' and standalone 'nanopay' break the convention slightly, but overall naming is predictable and readable.

    Tool Count4/5

    At 18 tools, the server is slightly on the heavier side of the ideal 3-15 range, but each tool addresses a distinct payment capability (standard, cross-chain, channels, intents, nanopayments), so the count feels justified for the scope.

    Completeness4/5

    The tool surface covers the full payment lifecycle for multiple payment methods: balances, transfers, history, channel open/consume/settle, intents, and nanopay management. Minor gaps exist (no cancel for regular transfers, no single-transfer detail retrieval), but these are not critical for core workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources