Skip to main content
Glama
tbadlov

Marqeta DiVA API MCP Server

by tbadlov

Related Servers

Alternatives to Marqeta DiVA API MCP Server

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to retrieve and analyze Dwolla payment platform data using natural language, with read-only access to accounts, transfers, customers, and compliance information.
      66 npm
      3
      -
    • A
      license
      B
      quality
      F
      maintenance
      Query bank accounts, credit cards, and transactions via Sophtron's financial data API. Works with Claude Desktop and any MCP-compatible client.
      10
      1
      Apache 2.0
    • A
      license
      A
      quality
      C
      maintenance
      Exposes NetSuite saved search exports as a structured query interface for Claude, enabling file discovery, column inspection, filtering, aggregation, memo categorization, and anomaly detection.
      7
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Provides financial audit reporting and ledger query tools for AI agents, enabling generation of compliance, risk, and transaction reports and querying of transaction data, balances, and summaries from an in-memory SQLite database via MCP.
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables secure interaction with Plaid's Transactions API to sync, search, and analyze financial transactions from linked bank accounts using natural language queries.
      -

    TDQS

    A3.7/5.0

    Scored across 20 tools

    Disambiguation5/5

    Each tool targets a distinct data type or aggregation level (authorizations, settlements, declines, balances, counts, etc.) with clear descriptions. Even related tools like get_chargebacks_detail and get_chargebacks_status serve clearly different purposes (detail vs status). No overlapping ambiguity.

    Naming Consistency4/5

    Most tools follow a 'get_' prefix with a noun describing the data (e.g., get_authorizations). Two exceptions: export_view_to_file and list_available_views use different verbs, but these are distinct actions (export vs list) and still clear. Overall pattern is consistent and readable.

    Tool Count5/5

    20 tools is well-scoped for a financial reporting API. Each tool corresponds to a specific endpoint or metric, and the count covers the full range of DiVA views without unnecessary duplication. It's not too heavy nor too thin.

    Completeness4/5

    The tool set covers the major reporting areas: authorizations, settlements, declines, chargebacks, balances, cards, users, counts, and export. Minor gaps exist (e.g., no refunds or dispute tools), but for a typical reporting use case, the coverage is thorough and no critical dead ends are apparent.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues