Skip to main content
Glama
PayStage MCP Server

PayStage MCP Server

Related Servers

Alternatives to PayStage MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      Enables AI assistants and agents to vet a stablecoin or x402 payment before it is sent, returning an approve, hold, or reject decision from instant rule checks and an optional locally-run risk model. Fails closed, so malformed input or an unreachable model yields a hold rather than an approval.
      4
      840 PyPI
      1
      Apache 2.0
    • A
      license
      A
      quality
      D
      maintenance
      Enables no-payment triage of x402 payment surfaces, 402 Index health checks, and paid review handoff for authorized inspection.
      3
      48 npm
      1
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Deterministically evaluates whether a proposed agent spend action matches a supplied policy, returning ELIGIBLE, DENY, or STEP_UP with stable reason codes. Provides local policy evidence only, not payment authorization.
      1
      49 npm
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Enables agents to request payment authorization against signed human mandates, enforcing policy-as-code limits and returning a decision (authorize, challenge, or deny) without moving funds.
      1
      1
      Apache 2.0

    TDQS

    B3/5.0

    Scored across 5 tools

    Disambiguation3/5

    The four evaluate_* tools target distinct objects (authorizations, x402 payments, HIP-3 trades, velocity), but evaluate_outstanding_auths overlaps heavily with list_outstanding_auths, and evaluate_velocity is arguably a sub-check of evaluate_mcp_payment, so an agent may be unsure whether to call one or both. Descriptions mitigate but do not fully resolve these boundaries.

    Naming Consistency4/5

    All names use snake_case with a verb_noun structure (evaluate_*/list_*), which is predictable and readable. Minor deviation: evaluate_velocity has no target-object noun, but it is still interpretable.

    Tool Count5/5

    Five tools is well-scoped for a policy-evaluation server, with each tool covering a distinct decision surface (auths, payments, trades, velocity) plus the listing helper. Nothing feels padded or missing at the count level.

    Completeness3/5

    The server covers evaluation paths well, but there is no tool surface for managing or inspecting the policies themselves (create/update/read policy config), nor for retrieving past decisions or action history beyond velocity. Agents can evaluate but cannot administer or audit the policy layer, which is a notable gap.

    Maintenance

    ActivityMaintained
    ResponsivenessLimited data