Skip to main content
Glama
rivradev

recite-mcp

by rivradev

Related Servers

Alternatives to recite-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      A
      maintenance
      MCP 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.
      9
      125 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      MCP 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 npm
      6
      ISC
    • F
      license
      A
      quality
      D
      maintenance
      MCP server for ExpenseLM, a GenAI powered expense management application. Enables AI agents to access expense data for recording, insights, and advice.
      10
      1
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      MCP 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
    • A
      license
      Not graded
      quality
      D
      maintenance
      MCP server providing deterministic accounting tools for AI agents, including bank statement parsing, document classification, money math, and webhook verification.
      2
      Apache 2.0

    TDQS

    D1.7/5.0

    Scored across 57 tools

    Disambiguation2/5

    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.

    Naming Consistency3/5

    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.

    Tool Count2/5

    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.

    Completeness3/5

    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'.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues