PayStage MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| evaluate_mcp_paymentC | Evaluate an x402 PaymentRequired payload against a PayStage spending policy before paying |
| list_outstanding_authsC | List outstanding token authorizations for a wallet |
| evaluate_outstanding_authsC | List and evaluate outstanding token authorizations against a policy |
| evaluate_hip3_tradeB | Evaluate a Hyperliquid HIP-3 (trade.xyz) order against a TradePolicy before an agent trades. Returns decision allow | review | do_not_trade. |
| evaluate_velocityC | Rolling-window rate and spend-pattern check for a proposed payment against recent action history and a policy.velocity config |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.