MCP Buste Paga
Related Servers
Alternatives to MCP Buste Paga
No user-submitted related servers found.
Related Servers
- FlicenseAqualityDmaintenanceParses PDF receipts to extract grocery and shopping expenses, automatically categorizes items using smart rules and LLM fallback, and stores them in a local SQLite database for querying purchase history and spending patterns.3-
- AlicenseNot gradedqualityDmaintenanceEnables extraction of structured data from documents like invoices, receipts, and bank statements using local Vision AI (Ollama) or cloud providers (Gemini), with data stored in a local SQLite database.2 npmMIT
- AlicenseNot gradedqualityCmaintenanceBuilds searchable SQLite databases from PDFs, preserving inline image locations for AI agents to discover and caption visual content. Supports full-text search over text, image placeholders, and saved captions.1MIT
- AlicenseAqualityAmaintenanceEnables AI agents to work with Italian FatturaPA electronic invoices and the SDI exchange system: extracting invoice data, running structural XML checks, detecting anomalies, aggregating multi-invoice reports, looking up SDI error codes offline, and verifying Italian or EU VAT numbers via VIES. Installs in one line and runs locally with fail-closed file access so untrusted documents can be processed safely.7MIT
- AlicenseAqualityBmaintenanceIndexes local documents (PDF, Word, Markdown, text) into a SQLite database for AI agents to search and retrieve bounded, source-located passages. Runs fully locally with optional OCR, preserving privacy.5MIT
- FlicenseNot gradedqualityDmaintenanceParse and query investment statements from multiple institutions (Questrade, Interactive Brokers, Scotia) using natural language or structured queries. Supports semantic search for dividends, holdings, transactions, and account balances with hybrid SQLite and vector database storage.-
TDQS
Scored across 5 tools
Each tool targets a distinct operation: ingestion, employee profile, salary summary, payslip details, and keyword search. There is no apparent overlap; even the two 'get' tools serve clearly separate purposes (aggregate history vs. individual payslip detail).
Most names follow a verb_noun pattern, but two tools have the '_tool' suffix (get_salary_history_tool, get_payslip_details_tool) while others do not. This is a minor inconsistency that doesn't impede understanding, but it breaks the pattern slightly.
With exactly 5 tools, the set is well-scoped for a payslip management server. Each tool addresses a necessary step (ingestion, querying summaries, details, and search) without redundancy or bloat.
The server covers the core lifecycle: import payslips, view employee context, review salary history, inspect specific payslips, and search line items. Minor gaps exist (e.g., no list of all payslips as a lightweight endpoint, no update/delete), but the core functionality is complete for typical read-only and ingestion use cases.