Skip to main content
Glama
dponcedeleonf

demo-app-mcp-prestamo

by dponcedeleonf
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

Related Servers

Alternatives to demo-app-mcp-prestamo

No user-submitted related servers found.

    Related Servers

    • Banorte One

      noriega1308
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables an AI agent to generate and reconfigure real-time banking interfaces by exposing MCP tools that return UI schemas and personalized financial components based on customer context and situation. It supports dynamic situation detection, security rules, and demo profiles for adaptive dashboards.
      67 npm
      -

    • Rabobank Demo MCP Server

      RemseyMailjard
      F
      license
      Not graded
      quality
      D
      maintenance
      Demonstrates how to expose approved internal banking tools to AI assistants via MCP, enabling secure lookups of account balances, customer names, branch details, and live exchange rate conversions.
      -

    • mcp-colombia

      manuelariasfz
      A
      license
      A
      quality
      F
      maintenance
      This MCP server connects AI agents with Colombian e-commerce, travel, and financial services, allowing users to search MercadoLibre, find hotels, and compare banking products like CDTs and loans. It enables seamless integration with local services in pesos colombianos through specialized tools for shopping, travel planning, and financial simulation.
      8
      13 npm
      2
      MIT

    • acel-toy-server

      Purav-Kanda
      A
      license
      Not graded
      quality
      B
      maintenance
      Demo MCP server for ACEL, a runtime verification middleware that blocks a rule-violating tool call before it executes. 5 tools (authenticate, read/validate/delete records, send payment) showing ACEL enforcing call ordering and state preconditions live via the official MCP SDK's middleware hook.
      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.2/5.0

    Scored across 9 tools

    Disambiguation3/5

    The main flow tools are distinct, but the inclusion of internal widget tools (autorizar_con_clave, capturar_cuenta_destino, estado_prestamo) creates potential ambiguity, especially between estado_prestamo and consultar_estado_solicitud. Descriptions help clarify, but the agent must be careful to avoid invoking internal tools.

    Naming Consistency4/5

    Most tool names follow a verb_noun pattern in Spanish snake_case (e.g., iniciar_solicitud_prestamo, capturar_monto_y_fecha, elegir_plan_pago). The main deviation is estado_prestamo, which is a noun phrase, and a couple of names use 'con' (autorizar_con_clave, capturar_cuenta_destino). Overall the convention is consistent.

    Tool Count4/5

    Nine tools is within the typical range, but three are internal widget tools that the agent should never call, inflating the count and adding noise. The effective public tool count is six, which is well-scoped for the loan application flow.

    Completeness5/5

    The loan request flow is fully covered from initiation through capture, plan selection, confirmation, reset, and status query. PIN and destination account steps are handled internally by the widget, so no public tools are needed for those. No obvious gaps in the agent-facing surface.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources