Skip to main content
Glama
theluckystrike

mcp-purchase-requisition

by theluckystrike
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Related Servers

Alternatives to mcp-purchase-requisition

No user-submitted related servers found.

    Related Servers

    • BrowserSpend Guard MCP by clauxel

      BrowserSpend Guard MCPofficial

      clauxel
      F
      license
      Not graded
      quality
      D
      maintenance
      Approval receipts for AI browser purchases. Enables purchase evaluation, approval recording, budget alerts, and receipt export.
      -

    • ProcureGuard MCP

      lxpjamboo
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables automated forensic auditing of public procurement tenders by parsing RFQ specifications, detecting price drift against market baselines, flagging bidder collusion risks, and enforcing human officer approval before any decision is recorded.
      8,511 npm
      MIT

    • 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

    • 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 16 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action: template creation, item management, run lifecycle, and license management are clearly separated. Even similar-sounding tools like run_show and run_report are differentiated by purpose (interactive view vs. printable text export).

    Naming Consistency4/5

    Names mostly follow a predictable resource_action pattern, such as purchase-requisition_create, run_start, and license_activate. The pattern is slightly weakened by noun-like actions like run_status and license_status, where status means "change status" in one case and "report status" in the other.

    Tool Count4/5

    At 16 tools, the set is slightly above the ideal 3-15 range but still well-scoped for the domain: 6 template tools, 8 run tools, and 2 license tools. Each tool covers a recognizable operation, so the count feels reasonable rather than bloated.

    Completeness4/5

    The core lifecycle is well covered: create/show/list/delete requisitions, add/remove items, start/check/show/list/sign off/delete runs, and license management. Missing update operations for requisition metadata and item details are notable gaps, though they can be worked around by recreating or removing and re-adding items.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources