Skip to main content
Glama
zackscriven

lemma-banking-mcp

by zackscriven
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to lemma-banking-mcp

No user-submitted related servers found.

    Related Servers

    • Griffin MCP server by griffinbank

      Griffin MCP serverofficial

      griffinbank
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to interact with the Griffin API for banking operations like opening accounts, creating payments, and managing legal persons.
      12 npm
      14
      MIT

    • fineye-mcp

      mktpavlenko
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to securely access and manage your FinEye personal-finance data—accounts, transactions, budgets, categories, tags, holdings, and spending analytics—with read-only, write, and delete operations controlled by explicit safety gates.
      MIT

    • Salt Edge MCP Server

      7BlockLabs
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to access banking data APIs and list customers, connections, accounts, and posted transactions, with metering tied to the caller’s own API key.
      MIT

    • BankSync MCP Server

      banksynchq
      A
      license
      Not graded
      quality
      C
      maintenance
      Connect AI agents to real bank accounts across 15,000+ financial institutions for transactions, balances, investments, and loans.
      2
      MIT

    • Procfy

      mcp-dir
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables financial management through the Procfy API, allowing AI agents to manage transactions, bank accounts, contacts, and more via natural language.
      1
      MIT

    • paygentic

      FoxRick
      F
      license
      A
      quality
      D
      maintenance
      Enables AI agents to manage financial operations including balance checks, money transfers, invoicing, spending policies, and audit logs through the PayGent API.
      13
      -
    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.7/5.0

    Scored across 27 tools

    Disambiguation4/5

    For the most part every tool targets a distinct resource (entities, bank accounts, cards, ACH, check deposits, remittances), and get/list pairs are clear. However, lemma_get_ach_transfer and lemma_get_inbound_ach_transfer differ only by one word in the tool name, and the generic 'ach_transfer' name hides that it is the outbound variant; list_transactions also overlaps conceptually with the resource-specific list tools.

    Naming Consistency4/5

    All tools share the lemma_ prefix and mostly follow lemma_<verb>_<noun>, with get/list/create/delete/move verbs. Minor deviations exist: lemma_get_ach_transfer does not mark outbound while its inbound counterpart does, and lemma_get_account_settlement_instructions breaks the concise noun pattern.

    Tool Count4/5

    27 tools is above the typical 3-15 range, but the server covers a genuinely broad banking domain: entities, accounts, transactions, cards, transfers, check deposits, remittances, lockbox mail, and external recipients. Each tool maps to a distinct endpoint or resource and none are duplicates, so the size feels justified rather than bloated.

    Completeness3/5

    Core banking operations are covered well: list/get accounts and transactions, create external accounts, move money internally/externally, and create/delete cards. However, there is no way to list cards or update card spending limits, and outbound ACH/book transfers have get-by-ID but no list endpoint, which are notable lifecycle gaps for a banking surface.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources