Skip to main content
Glama
thanhnv2210

finpay-mcp-server

by thanhnv2210

Related Servers

Alternatives to finpay-mcp-server

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      B
      maintenance
      MCP server that provides tools for retrieving transaction context and recording AI decisions or creating human reviews for payment risk exceptions. Enables LLM agents to handle exception transactions in a hybrid payment-decisioning workflow.
      -
    • F
      license
      Not graded
      quality
      B
      maintenance
      MCP server for payments analytics, enabling natural language queries on transaction data, merchant summaries, and chargeback anomaly detection with grounded, auditable answers.
      -
    • F
      license
      Not graded
      quality
      D
      maintenance
      A production-grade MCP server that exposes real-time banking data replicated via Oracle GoldenGate CDC as structured tools for AI agents, enabling read, score, and write operations on customer, account, transaction, and alert data.
      1
      -
    • F
      license
      A
      quality
      D
      maintenance
      MCP server for ExpenseLM, a GenAI powered expense management application. Enables AI agents to access expense data for recording, insights, and advice.
      10
      1
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for AgentPay — the payment gateway for autonomous AI agents. Fund a wallet once, give your agent the key, and it discovers, provisions, and pays for tool APIs on its own. One key, every tool.
      112 npm
      1
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      A local MCP server for Stripe payment operations with 52 tools across 8 domains, featuring built-in PII redaction and strict input validation for safe AI-assisted development workflows.
      52
      24 npm
      1
      MIT

    TDQS

    A4.4/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool has a clear, distinct purpose: list_* returns collections, get_* returns individual entities by ID, explain_service provides detailed service metadata, and search_docs handles documentation queries. No two tools overlap in function or target resource.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in snake_case. List tools use 'list_', retrieval tools use 'get_', plus 'explain_' and 'search_' which are also descriptive verbs. Naming is uniform and predictable.

    Tool Count5/5

    Eight tools is well within the ideal range for a payment platform query/monitoring server. Each tool covers a needed operation without redundancy or bloat.

    Completeness5/5

    The server provides complete read-only coverage for its domain: listing and getting hubs, services, and transactions, plus overall system health and documentation search. No obvious gaps for the intended use case; write operations are likely out of scope.

    Maintenance

    ActivityStale
    ResponsivenessNo issues