Skip to main content
Glama
dexstandard

FinCobra MCP

by dexstandard
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to FinCobra MCP

No user-submitted related servers found.

    Related Servers

    • Yolfi MCP Server

      emre08189
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables AI coding agents to add stablecoin checkout, payment links, payment status checks, webhook verification, and webhook-based entitlement logic to applications. It also provides tools for workspace registration, settlement and webhook configuration, paylink creation, and crypto payment status checks.
      -
    • Conekta MCP Server by conekta

      Conekta MCP Serverofficial

      conekta
      F
      license
      A
      quality
      D
      maintenance
      Enables interaction with the Conekta payment API to manage orders, customers, subscriptions, and financial transactions. It provides a comprehensive suite of tools for core payment operations like processing refunds, creating checkouts, and monitoring account balances.
      32
      2
      -

    • coinpay-onboard

      profullstack
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables agents to set up CoinPay crypto payments in one idempotent pass: provisioning payout addresses, a business, payout wallets, webhooks, and supported coins. It also supports creating, checking, and verifying payments through the CoinPay API.
      269 npm
      MIT

    • Yolfi MCP Server

      anh71
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables AI coding agents to integrate stablecoin checkout, payment links, payment status checks, webhook verification, and webhook-based entitlement logic into applications.
      -
    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.3/5.0

    Scored across 5 tools

    Disambiguation5/5

    All five tools have clearly distinct responsibilities: invoice lookup/creation are separate, and net-worth/source actions are separate. get_source and list_sources follow the standard item-vs-collection pattern. There is no meaningful overlap.

    Naming Consistency5/5

    Names consistently follow a verb_noun pattern: get_invoice, create_invoice, list_sources, get_source, and get_net_worth. The convention is uniform and predictable across both subdomains.

    Tool Count5/5

    Five tools is a compact, appropriate size for a server covering Checkout invoices and Watchlist reads. Each tool serves a distinct need without redundancy.

    Completeness3/5

    The invoice side covers create and lookup but not list, cancel, or update operations, and the Watchlist side is read-only with no way to add or edit sources. These are notable lifecycle gaps, though the core read and checkout workflows are present.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources