recite-mcp
Related Servers
Alternatives to recite-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceMCP server for Tersign, the evidence layer for agent commerce, enabling agents to issue, verify, and manage signed receipts, compliance records, refunds, and disputes on a counter-signed hash-chained ledger.9125 npm1MIT
- AlicenseNot gradedqualityBmaintenanceMCP server for Expense, a receipt tracker that lets AI assistants capture receipts, log mileage, answer spending questions, build reports, and reconcile bank statements from your expense data.2 npm6ISC

expenselm-mcp-serverofficial
FlicenseAqualityDmaintenanceMCP server for ExpenseLM, a GenAI powered expense management application. Enables AI agents to access expense data for recording, insights, and advice.101-- AlicenseNot gradedqualityDmaintenanceMCP server for agent ecosystem analytics. Provides real-time health snapshots including transaction velocity and dispute rates, predictive analysis with confidence scoring, and pattern detection across multi-agent networks.MIT
- AlicenseNot gradedqualityDmaintenanceMCP server for ReceiptConverter that allows AI assistants to parse any receipt or invoice image/PDF into structured JSON with a single tool call.5 npmMIT
- AlicenseNot gradedqualityDmaintenanceMCP server providing deterministic accounting tools for AI agents, including bank statement parsing, document classification, money math, and webhook verification.2Apache 2.0
TDQS
Scored across 57 tools
Many tools lack descriptions, forcing reliance on names alone. Overlapping operations like scan_receipt, process_receipt, submit_batch_scans, and get_batch_scan_results are difficult to differentiate, leading to potential misselection.
Tool names mostly follow a verb_noun pattern, but there is inconsistency in verb choice (e.g., 'get' vs 'list' for different entities) and some names are compound (e.g., 'process_receipts_batch'). Overall readable but not perfectly uniform.
With 57 tools, the server is overly broad, covering CRUD for many entities, scanning, batch processing, reconciliation, rules, webhooks, memory, and configuration. This bloat exceeds the typical well-scoped range and risks overwhelming agents.
Most entities have basic CRUD operations, but there are notable gaps like missing 'get_project' and 'get_vendor' (only list). The domain coverage is fairly extensive but not fully systematic, with some one-off tools like 'validate_setup'.