Skip to main content
Glama
floreskemec

latamfx-mcp

by floreskemec

Related Servers

Alternatives to latamfx-mcp

No user-submitted related servers found.

    Related Servers

    • F
      license
      A
      quality
      C
      maintenance
      Verified Latin American data for autonomous AI agents via x402 micropayments. Sanctions screening (OFAC SDN + SARLAFT + CNBV + COAF + UAF) with EU AI Act Art.12/13 compliant hash-chain audit trail, entity enrichment (RUES/CNPJ/RFC), and real-time LATAM central bank rates including Argentina dólar blue. $0.02–$0.10 USDC per call on Base and Solana. No API key required.
      4
      1
      -
    • F
      license
      A
      quality
      B
      maintenance
      MCP server providing verified Latin American data via x402 micropayments. 4 MCP tools: vera_rates (central bank rates CO/MX/BR/CL/PE), vera_sanctions (OFAC+SARLAFT+CNBV+COAF+UAF screening, EU AI Act Art.13), vera_entity (RUES/CNPJ/RFC enrichment), vera_context (AI market intelligence). $0.02–$0.10 USDC per call.
      4
      -
    • A
      license
      A
      quality
      B
      maintenance
      Enables LLMs to retrieve the official Colombian TRM (USD/COP exchange rate) with its validity window, perform currency conversions, and analyze rate series, all with auditable provenance.
      4
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Validates LatAm banking and tax IDs (Mexican CLABE, Brazilian CNPJ/CPF checksums) and performs BrasilAPI company, CEP, and bank lookups, enabling AI agents to verify financial and tax information in Latin America.
      3 npm
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Provides real-time foreign-exchange rates, historical data, and multi-currency lookups to MCP-compatible AI coding assistants like Claude Code and Cursor.
      4
      53 npm
      MIT

    TDQS

    A3.5/5.0

    Scored across 6 tools

    Disambiguation4/5

    Most tools have distinct purposes (conversion, quotes, stats, timeseries, source listing). However, 'reconcile' introduces a separate domain (ledger reconciliation) which could be confusing but does not overlap with FX tools.

    Naming Consistency3/5

    Naming conventions are mixed: 'convert' and 'reconcile' are bare verbs, while others use 'get_fx_*' or 'list_fx_*' pattern. This inconsistency could be confusing.

    Tool Count4/5

    6 tools is a reasonable number for an FX-focused server plus a reconciliation tool. It feels slightly heavy but still manageable.

    Completeness4/5

    Core FX operations (list sources, get quote, timeseries, stats, convert) are covered. The inclusion of reconciliation is a bonus but not part of the expected surface, so minor gap.

    Maintenance

    ActivityStale
    ResponsivenessNo issues