@arispay/payagent-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ARISPAY_URL | No | ArisPay API base URL | https://api.arispay.app |
| PAYAGENT_WALLET | No | Wallet address (for check_wallet tool output) | |
| ARISPAY_AGENT_KEY | Yes | Agent-scoped API key from payagent.arispay.app |
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 |
|---|---|
| setupA | Creates or recovers an ArisPay account for delegated custody and provisions a USDC payer wallet in one call (side effects: registers the email, creates a Coinbase CDP-managed wallet, writes credentials to ~/.payagent/config.json on this machine). Moves no money — it does NOT spend funds. Idempotent: re-running with the same email recovers the existing account and its wallets. Not needed in self-custody mode: if PAYAGENT_PRIVATE_KEY is set, skip setup entirely — pay works with the local key alone. |
| discoverA | Searches the ArisPay marketplace for paid APIs by capability or plain-language intent, optionally budget-bounded (integer cents). Read-only — spends no money, needs no API key. Returns ranked candidates with endpoint URL, price in cents, health and verification flags. Select this to FIND an endpoint; then inspect to price a specific URL, then pay to call it. |
| inspectA | Fetches an x402-protected URL WITHOUT paying and reports its price, asset, network, and payment requirements. Read-only — spends no money, sends no payment header, needs no API key or account. Always safe. Select this before pay to know exactly what a resource costs. |
| payA | SPENDS REAL MONEY — on-chain and irreversible. The complete machine payment path: makes the HTTP request, and if the server answers 402, selects the supported asset/network variant (USDC on Base/Ethereum/Polygon; delegated mode also settles Solana and BNB Chain variants), validates policy, pays, retries the request, and returns the response plus a structured machine-readable receipt. Requires an idempotencyKey: re-calling with a key that already paid returns the cached receipt and does NOT pay again. Mode selection: PAYAGENT_PRIVATE_KEY set → signs locally (self-custody; wallet balance is the only cap); otherwise pays through the stored ArisPay agent whose per-tx/daily/monthly mandate is enforced server-side BEFORE signing. Use inspect first to see the price. Do not use for ordinary unpaid HTTP requests. |
| balanceA | Read-only: shows where the money is — the active payment identity (the stored ArisPay agent, delegated, or the PAYAGENT_PRIVATE_KEY-derived address, self-custody) with its USDC deposit address, on-chain balance and (delegated) spend-mandate limits, plus the account holder's own bank accounts (vIBANs) with their balances and pay-in details. Spends no money, never pays. Select this to tell the human where their money is and how to add more, to confirm a deposit landed, or when a payment fails. |
| historyA | Read-only: lists recent payments — the server-side activity feed in delegated mode (newest first), or locally recorded receipts in self-custody mode. Spends no money. Select this to reconcile what was paid, retrieve a past receipt, or audit an agent's spending. |
| check_payment_signalA | SPENDS REAL MONEY — 1¢ (USDC, Base mainnet) per UNCACHED call; a still-valid cached artifact returns WITHOUT spending, and an unknown resource is answered free. Buys ArisPay Signal: recent signed probe evidence about an x402 resource (did a real paid probe settle and deliver?) as an arispay.signal.v1 artifact, verified against the published JWKS. Use it BEFORE a material first payment to an unfamiliar resource, or after cached evidence expires. The decision denominator is CUMULATIVE exposure before the artifact expires — planned spend across all intended calls, or the expected cost of one failure, whichever is larger — not the price of the next call: an agent planning 100 calls to a 1¢ endpoint should check; an agent making a single 1¢ call should not. Skip it when cumulative exposure is at or below the 1¢ check price. Returns signed observational evidence with explicit freshness — NOT a guarantee, insurance, or endorsement. Network side effect: one HTTPS request to the Signal endpoint; payment side effect: the 1¢ x402 purchase on uncached calls. |
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 7 tools
Each tool has a distinct function: discover finds endpoints, inspect prices one, pay executes, balance locates funds, history audits past payments, check_payment_signal buys probe evidence, and setup provisions an account. The only mild overlap is between the two pre-payment diagnostics (inspect vs check_payment_signal), but the descriptions clearly separate pricing from buying evidence.
Most names are single words but mix nouns (balance, history) with bare verbs (inspect, discover, pay, setup), and one tool breaks the pattern with snake_case multi-word 'check_payment_signal'. It remains readable and predictable in intent, but there is no consistent verb_noun convention.
Seven tools is well-scoped for a payment agent, with each earning its place across the discover→inspect→pay→history→balance workflow plus account setup and a safety-verification step. No filler or redundant tools.
The surface covers the full agent-payment lifecycle: provisioning, discovery, price inspection, paying, spending audit, balance lookup, and pre-payment signal verification. Minor gaps exist (no explicit tool to modify spend mandates or manage/withdraw vIBAN funds), but core workflows are fully covered.