Skip to main content
Glama
hrishi0102

Payman AI MCP Server

by hrishi0102
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to Payman AI MCP Server

No user-submitted related servers found.

    Related Servers

    • ZBD MCP Server by zbdpay

      ZBD MCP Serverofficial

      zbdpay
      F
      license
      Not graded
      quality
      F
      maintenance
      A server that adds Bitcoin payment capabilities to LLMs, enabling sending/receiving payments, creating charges, managing wallets, and performing other Bitcoin Lightning Network operations.
      3
      -

    • @mogintel/mcp-jazzcash

      MogIntel
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server wrapping JazzCash payment provider APIs. Enables interaction with JazzCash services through natural language.
      MIT

    • 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

    • Interswitch MCP Server

      Dairus01
      A
      license
      C
      quality
      D
      maintenance
      An MCP server that enables AI assistants to interact with Interswitch APIs for payments, transfers, VAS, cardless paycodes, Transaction Search, Card 360, lending, payouts, agency banking, and fintech card-processing utilities.
      74
      36 npm
      1
      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

    C2.1/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose with no overlap: three tools create different types of payees (crypto, test rails, US ACH), while others handle balance retrieval, payee search, payment sending, and API key management. The naming makes the distinctions obvious even without descriptions.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern with hyphens (e.g., create-crypto-payee, get-balance, send-payment). The naming is uniform throughout, making it easy to predict and understand each tool's function.

    Tool Count5/5

    With 7 tools, this server is well-scoped for payment and payee management. The count is appropriate, covering core operations like payee creation, balance checking, searching, payments, and configuration without being overwhelming or insufficient.

    Completeness4/5

    The toolset covers key payment workflows: creating payees, retrieving balance, searching payees, sending payments, and setting API keys. A minor gap is the lack of update or delete operations for payees, but agents can likely work around this given the core functionality is present.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources