fintaro-mcp
OfficialRelated Servers
Alternatives to fintaro-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables MCP-compatible agents to securely access an Invoice4U account for searching documents and customers and creating receipts linked to paid invoices, with read-only behavior by default.1MIT
- AlicenseBqualityCmaintenanceEnables MCP clients to read Fortnox invoices and customers, validate receipts, and optionally perform approved write operations with strict safety controls.3MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to manage API keys and child keys with budgets and spending caps, set plans and model routing, handle wallet payments and top-ups, and verify signed receipts through MCP tools.317 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables MCP-aware agents to initiate M-Pesa B2C/B2B payouts, query transaction status, validate phone numbers, and reconcile M-Pesa statements against ledger CSVs to surface discrepancies, plus structured lookups for county public data and KRA tax helpers. It runs in sandbox mode by default, uses idempotency keys for safe retries, and stays read-only for reconciliation and lookups.MIT
- AlicenseAqualityBmaintenanceEnables managing Kontur.Elba data through the official Public API, including organizations, bank accounts, counterparties, products, documents, invoices, and public links via MCP tools.44 npmMIT
- FlicenseNot gradedqualityBmaintenanceEnables MCP-capable LLMs to securely autofill and save invoices on Digital Invoicing Software on behalf of tenants, with multi-tenant authentication and session management.-
TDQS
Scored across 6 tools
Each tool has a unique, well-defined purpose. get_invoice and list_invoices are clearly distinct, list_transactions and list_unmatched are differentiated by filter criteria, and whoami is a standalone identity check.
All tool names follow a consistent verb_noun pattern with lowercase underscores (e.g., get_invoice, list_transactions). whoami is a minor exception but common in practice, not causing confusion.
With 6 tools, the set covers core financial operations (invoices, transactions, identity) without being bloated or too sparse, fitting the domain well.
The tool surface covers invoice retrieval, listing, upload, transaction listing, and unmatched transaction listing. Missing update/delete for invoices is a minor gap, but the core workflow is intact.