Skip to main content
Glama
janishkumar

po-guard-mcp

by janishkumar
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to po-guard-mcp

No user-submitted related servers found.

    Related Servers

    • p2p-finance

      sergio4848
      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

    • safe-cart-ai

      Jai-095
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to browse product catalogs and make purchases through a policy engine that enforces spending limits, requires human approval for certain amounts, and logs all actions to an audit trail.
      -

    • AchPay

      Anas-github-acc
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to securely search products, obtain signed quotes, create checkouts, and track orders without directly handling prices or payment amounts, enforcing spending policies and audit trails.
      1
      -
    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/5.0

    Scored across 14 tools

    Disambiguation5/5

    Each tool targets a distinct resource+action: get vs list are clearly scoped, and the approval-state transitions (submit, approve, reject, cancel, amend) are each explicitly delimited. The `preview` meta-tool is clearly distinguished as a dry-run gate for writes, including an enumerated action list.

    Naming Consistency4/5

    The dominant pattern is consistent verb_noun (get_purchase_order, list_purchase_orders, create/amend/submit/approve/reject/cancel_purchase_order, search_suppliers). Deviations are noun-only utility tools (budget_status, audit_log) and the generic `preview`/quirky `whoami`, but these remain readable and predictable.

    Tool Count5/5

    14 tools is well within a healthy range and each earns its place: a full PO lifecycle, plus supporting reads (search, budget, audit, whoami) and a safety-gate preview. Nothing appears redundant or padding.

    Completeness4/5

    Purchase-order coverage is strong: create, amend, submit, approve, reject, cancel, get, list, plus budget and audit context. The supplier surface is thin (only search and onboard, no get/update/deactivate), and there is no goods-receipt or invoice-matching operation, but core workflows are workable.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources