PayStage MCP Server
Related Servers
Alternatives to PayStage MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceEnables agents and developers to check x402 endpoints, assess scores and wallet risks, authorize payments with spending rules, and report outcomes before an agent pays.62MIT
- FlicenseNot gradedqualityDmaintenanceProvides a pre-signature payment-risk verdict (GO/HOLD/STOP) for x402 payments based on counterparty reputation, price anomaly, and OFAC sanctions.-
- AlicenseAqualityBmaintenanceEnables 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.4840 PyPI1Apache 2.0
- AlicenseAqualityDmaintenanceEnables no-payment triage of x402 payment surfaces, 402 Index health checks, and paid review handoff for authorized inspection.348 npm1MIT
- AlicenseAqualityDmaintenanceDeterministically 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.149 npmMIT
- AlicenseAqualityDmaintenanceEnables 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.11Apache 2.0
TDQS
Scored across 5 tools
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.
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.
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.
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.