Skip to main content
Glama

Related Servers

Alternatives to Countersign

No user-submitted related servers found.

    Related Servers

    • F
      license
      A
      quality
      C
      maintenance
      Enables an AI agent to handle accounts payable tasks against a mock ERP, including reading and writing bills and vendors, checking duplicates, matching invoices, recommending approvals, and queuing payment releases, with configurable profiles that limit available tools.
      11
      -
    • A
      license
      A
      quality
      C
      maintenance
      Enables LLM agents to query and reconcile an accounts-payable ledger through safe read-only SQL, deterministic invoice-to-payment matching, and exception explanations for underpayments, duplicates, currency mismatches, and overdue invoices. Ships with a synthetic ledger, golden-set evals, and a month-end review workflow so quality can be measured in CI.
      4
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to list and process supplier invoices, run validation and fraud checks, review anomalies, summarize suppliers, and query an invoice DuckDB store through seven read-only MCP tools.
      MIT
    • A
      license
      B
      quality
      B
      maintenance
      Enables AI models to three-way-match supplier invoices against purchase orders and goods received, returning deterministic approval, hold, or review decisions with human-readable reasons. It exposes tools to check invoices, list open purchase orders, and quote a plain-language matching policy, while never posting or paying anything.
      2
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables natural-language-driven purchase-to-pay workflows against mock procurement and payment APIs, including invoice matching, exception handling, human approvals, and idempotent payment scheduling with a tamper-evident audit log.
      MIT

    TDQS

    B3/5.0

    Scored across 20 tools

    Disambiguation5/5

    Each tool targets a distinct resource or workflow action: email, invoice, vendor, purchase order, approval, payment, or time progression. The potentially closest pairs, such as pay_invoice vs manual_wire and end_day vs close_period, are clearly separated by their descriptions.

    Naming Consistency4/5

    Nearly all tools follow a consistent snake_case verb_noun pattern: get_policy, list_invoices, pay_invoice, close_period, etc. manual_wire is a minor exception because it is not phrased as a verb_noun action.

    Tool Count4/5

    Twenty tools is somewhat heavy, but the accounts-payable simulation covers several distinct subdomains: email, invoices, vendors, purchase orders, approvals, payments, and time. Most tools appear to earn their place rather than duplicating one another.

    Completeness4/5

    The surface covers the core AP lifecycle well: reading policy, handling inbox mail, inspecting invoices/vendors/POs, requesting approval, linking POs, updating bank data, paying or rejecting invoices, and advancing/closing the period. Minor gaps exist around browsing all vendors and explicitly checking approval status, but they are unlikely to block normal workflows.