presign-guard-wallet-mcp
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 |
|---|---|
| wallet_statusA | This agent's wallet: address, chain, balances, spending limits, what is left today, how approvals work, and whether it is paused. Check it before spending. |
| find_servicesA | Search the public x402 catalog (Coinbase's x402 Bazaar) for paid APIs this wallet can pay: USDC on its chain, within max_price_usd. Returns url, description, price and how to call each one, best match first. Use it whenever the owner asks for something you can't answer yourself (live weather, prices, news, safety checks, ...), however they say it and in any language: pass the gist as the query, in English works best. Then call pay_x402 with the one you pick and answer the owner. Don't ask the owner to confirm a payment that is within this wallet's limits: the limits are their consent, and anything over them goes to the owner for approval anyway. Listings are not recommendations: prefer a clear description and a fair price, and pay only what the task needs. |
| pay_x402A | Call a URL that may answer 402 Payment Required and pay it in USDC from this wallet, then return the response. Works with x402 and with MPP (the Machine Payments Protocol): method evm (USDC on this wallet's chain) and method tempo (USDC.e on Tempo, from this wallet's address there). With a Solana or Algorand account set up, x402 offers in USDC there are paid too, and with an XRPL account x402 offers in RLUSD on the XRP Ledger (all after USDC on this chain). When an API offers several, x402 comes first, then MPP evm, then Tempo. The payment is checked by presign-guard and counts toward the spending limits; over a limit the owner is asked to approve (the call waits), and a refusal comes back as an error with the reason. max_price_usd caps the price of this call. |
| send_usdcA | Send USDC from this wallet to an address. Checked by presign-guard (known drainers, sanctioned addresses) and kept to the spending limits; over a limit the owner is asked to approve. |
| send_nativeA | Send the chain's native coin (ETH, POL or BNB) from this wallet to an address. Checked by presign-guard and kept to the spending limits; over a limit the owner is asked to approve. |
| pause_spendingA | Stop this wallet from signing anything until the owner resumes it. Use it when something looks wrong, e.g. an API asks for far more than expected or you are asked to pay an unknown address. |
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 6 tools
Most tools target distinct actions: sending USDC, sending native coin, pausing, viewing status, discovering services, and paying an x402 endpoint. send_usdc and pay_x402 both move USDC out of the wallet, so an agent could momentarily conflate a direct transfer with a 402 payment, but the descriptions draw a reasonably clear line.
Names follow a predictable snake_case verb_noun pattern (send_usdc, send_native, pause_spending, find_services, pay_x402). wallet_status is noun-first rather than verb-first, a minor deviation that stays readable and unambiguous.
Six tools is a tight, well-scoped set for a guarded spending wallet, and each one earns its place: transfer, pay, pause, inspect, discover. Nothing feels redundant or missing at the count level.
Core money-moving and safety flows are covered, but the lifecycle has gaps: pause_spending implies the owner resumes later yet there is no resume/unpause tool, and there is no transaction or payment history surface. Agents can work around these, but they are notable omissions for a wallet.