StealthPay 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 |
|---|---|
| get-my-profile | Show your own wallet address, all ENS names you own, and stealth payment profile. Reads SENDER_PRIVATE_KEY from environment — the key itself is never exposed. |
| generate-wallet | Generate a new wallet keypair and save it to .env. The private key never leaves the Node.js process — only the address is returned. Will NOT overwrite an existing SENDER_PRIVATE_KEY. |
| get-balances | Check your wallet balances: native ETH and known tokens on a given chain. Uses SENDER_PRIVATE_KEY from environment — the key is never exposed. |
| register-ens-nameA | Register a new .eth ENS name. Checks availability, computes cost, and completes the commit-wait-register flow. Takes ~65 seconds due to the commitment waiting period. Uses SENDER_PRIVATE_KEY from environment. |
| register-stealth-keys | Generate spending and viewing keypairs, then set the stealth-meta-address text record on an ENS name. The caller must own/manage the ENS name. Private keys are saved directly to the .env file — they are never returned to the AI. |
| set-profile | Set payment preferences on your ENS name: preferred chain, token, stealth policy, and note preferences. Writes to both namespaced (stealthpay.v1.*) and legacy ENS text records for compatibility. |
| set-primary-nameA | Set the primary ENS name (reverse record) for your wallet. After this, your address resolves to the given ENS name. |
| get-payment-profileA | Resolve an ENS name and fetch the recipient's payment profile: address, avatar, preferred chain/token, and stealth meta-address. |
| generate-stealth-addressB | Generate a one-time stealth address for a recipient using their ENS name. The resulting address can only be controlled by the recipient, but cannot be linked to their public identity. |
| send-stealth-paymentA | Send a private payment to an ENS name using a stealth address. Supports native ETH, known stablecoins (USDC, USDT, DAI), or any ERC-20 by contract address. Generates a one-time address, sends the funds, and announces via ERC-5564. |
| create-payment-linkA | Generate a shareable payment link for an ENS name. The link resolves to a stealth address at payment time, ensuring privacy. |
| scan-announcements | Scan ERC-5564 announcements to discover stealth payments for a recipient. Uses RECIPIENT_VIEWING_PRIVATE_KEY and RECIPIENT_SPENDING_PUBLIC_KEY from environment — keys never pass through AI. |
| claim-stealth-paymentA | Derive the stealth private key and withdraw funds in one step. Uses RECIPIENT_SPENDING_PRIVATE_KEY and RECIPIENT_VIEWING_PRIVATE_KEY from environment — private keys never pass through AI. Only the ephemeral public key (from scan-announcements) and destination address are needed. |
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 and clear purpose, covering separate actions like generating addresses, sending payments, managing ENS names, resolving profiles, creating payment links, and claiming funds. There is no overlap or ambiguity.
All tool names follow a consistent verb-noun pattern with hyphens (e.g., generate-stealth-address, send-stealth-payment). The naming is predictable and uniform throughout the set.
With 7 tools, the server is well-scoped for its privacy-focused payment domain. Each tool is essential and covers key operations without unnecessary bloat or missing core functionality.
The tool surface covers most of the stealth payment workflow, but a critical tool for scanning announcements (as referenced in claim-stealth-payment) is missing, creating a dependency on external inputs. Additionally, no tools for balance checks or transaction history are provided.