Marqeta DiVA API MCP Server
Related Servers
Alternatives to Marqeta DiVA API MCP Server
No user-submitted related servers found.
Related Servers
FlicenseNot gradedqualityBmaintenanceEnables 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 npm3-- FlicenseAqualityDmaintenanceProvides read-only access to Authorize.net transaction reporting APIs, enabling users to query settled batches, transaction details, customer payment history, and settlement statistics directly from AI assistants.7-
- AlicenseBqualityFmaintenanceQuery bank accounts, credit cards, and transactions via Sophtron's financial data API. Works with Claude Desktop and any MCP-compatible client.101Apache 2.0
- AlicenseAqualityCmaintenanceExposes NetSuite saved search exports as a structured query interface for Claude, enabling file discovery, column inspection, filtering, aggregation, memo categorization, and anomaly detection.7MIT
- AlicenseNot gradedqualityCmaintenanceProvides 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
- FlicenseNot gradedqualityDmaintenanceEnables secure interaction with Plaid's Transactions API to sync, search, and analyze financial transactions from linked bank accounts using natural language queries.-
TDQS
Scored across 20 tools
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.
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.
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.
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.