Skip to main content
Glama
fintaro-ai

fintaro-mcp

Official
by fintaro-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
FINTARO_API_KEYYesThe ftk_ API key for authentication
FINTARO_BASE_URLNoThe base URL of the Fintaro API (must be https://)https://api.fintaro.ai/api/v1

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
whoamiA

Show which organization and scopes the configured API key is bound to.

upload_invoiceA

Upload a local receipt file (PDF/PNG/JPEG/WebP) to Fintaro for processing.

get_invoiceA

Return a narrow, PII-free summary of a single invoice.

list_invoicesA

List one page of the organization's invoices as narrow, PII-free summaries.

Newest-first. One call returns one page; if hasMore is true, call again with offset advanced by limit (clamped to 100). total is unknown (the gateway list endpoint returns no count).

Returns {"invoices", "total", "offset", "limit", "returned", "hasMore"}.

list_transactionsA

List one page of the organization's bank transactions as narrow summaries.

One call returns one page; if hasMore is true, call again with offset advanced by limit (clamped to 200). Narrow the window with date_from / date_to (ISO dates, e.g. "2026-06-01") to cover a period without paging all history.

Returns {"transactions", "total", "offset", "limit", "returned", "hasMore"}.

list_unmatchedA

List one page of transactions that still need a matching receipt.

Same paging/filtering contract as list_transactions: one page per call, advance offset by limit while hasMore, optionally bound by date_from / date_to. For a month-end close, pass the period's bounds.

Returns {"transactions", "total", "offset", "limit", "returned", "hasMore"}.

Prompts

Interactive templates invoked by user choice

NameDescription
monatsabschluss_checkGuided pre-close review: find transactions still missing a receipt.

Resources

Contextual data attached and managed by the client

NameDescription

No resources

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.1/5.0

Scored across 6 tools

Disambiguation5/5

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.

Naming Consistency5/5

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.

Tool Count5/5

With 6 tools, the set covers core financial operations (invoices, transactions, identity) without being bloated or too sparse, fitting the domain well.

Completeness4/5

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.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources