ShieldZ Crypto Payments
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SHIELDZ_API_KEY | No | API key for full merchant account. Enables invoice tools. If omitted, only keyless tools are available. | |
| SHIELDZ_BASE_URL | No | Base URL for Shieldz API. Defaults to https://shieldz.cash |
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 |
|---|---|
| create_payment_linkA | Create a one-time crypto payment link with ZERO setup, no account, no API key. Give a destination wallet address and an amount; get back a shareable pay_url, an embeddable button, and a manage_url. Non-custodial: funds settle directly to the address you provide. Optionally pass an email so the owner can claim a full dashboard later. |
| create_tip_jarA | Create a reusable 'pay what you want' tip jar with ZERO setup, no account, no API key. The payer chooses the amount. Returns a shareable /tip url, an embeddable button, and a manage_url. Idempotent per wallet address: calling again updates the same tip jar. Non-custodial: funds settle directly to the address you provide. |
| get_account_statusA | Look up a keyless Shieldz account by its manage_token (returned when you create a payment link or tip jar). Returns settlement details, tip jars, totals (paid/pending), and the full invoice list as structured JSON. |
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 3 tools
Each tool has a clearly distinct purpose: fixed-amount payment link, flexible tip jar, and account status. There is no overlap or ambiguity.
All tools follow a consistent verb_noun snake_case pattern (create_payment_link, create_tip_jar, get_account_status), making it easy to infer function from name.
With 3 tools, the server is tightly scoped to its 'zero setup' philosophy, covering the essential operations without unnecessary bloat.
The server covers creation of two payment types and status retrieval, but lacks update/delete capabilities for payment links or tip jars, which slightly limits agent workflows.