Keyless non-custodial crypto payments for AI agents: payment links and tip jars, no API key.

The MCP server enables AI agents to accept non-custodial crypto payments. Funds settle directly to a provided wallet address, with Shieldz never holding keys.
No accounts or API keys required; one-call setup to create payment tools such as links and buttons.
Topics include ai, crypto-payments, mcp, model-context-protocol, non-custodial.

🛠️ Key Features

Keyless tools: no account, no API key required.
Create payment links and embedable components (URL, button, QR) in a single call.
Funds settle directly to your wallet address; client controls the keys.

🚀 Use Cases

AI agents (e.g., Claude) accepting non-custodial crypto payments.
Tip jars and payments integrated into agent workflows.
Quick deployment of crypto payment acceptance without key management.

⚡ Developer Benefits

Simple integration with a single call to start accepting crypto.
Clear non-custodial security model: Shieldz does not hold keys.
Lightweight, no-account workflow suitable for agents and apps.

⚠️ Limitations

Readme excerpt indicates payment creation tools; ensure wallet address validity and network compatibility before use.

@shieldz/mcp

Model Context Protocol (MCP) server for Shieldz. Lets an AI agent (Claude, etc.) accept non-custodial crypto payments and sell digital products.

Funds always settle to the wallet address you provide. Shieldz never holds your keys.

Keyless tools (no account, no API key)

Give a destination wallet address and start accepting crypto in one call:

create_payment_link — a one-time payment link (shareable URL + embeddable button + QR). Args: address, amount_usd, optional chain (default base), asset (default USDC), memo, email.
create_tip_jar — a reusable "pay what you want" page; the payer chooses the amount. Args: address, optional chain, asset, title, suggested_amounts_usd, slug, email.
create_unlock — sell a digital product: a pay-to-unlock page for a file link, license key, or secret text (up to 100k chars). The buyer pays and the payload is revealed on their paid confirmation, automatically. Args: address, price_usd, payload, aup_accepted, optional title, description, chain, asset, email. (To deliver an uploaded file up to 10 MB, post multipart to /api/v1/unlocks.)
get_account_status — look up settlement details, tip jars, totals, and invoices by manage_token.

These work with zero configuration. Pass an optional email so the owner can claim a full dashboard later via magic link.

Remote (no install) — point any MCP client at the hosted server:

json

{ "mcpServers": { "shieldz": { "url": "https://shieldz.cash/mcp" } } }

Local (stdio) — run via npx:

json

{
  "mcpServers": {
    "shieldz": {
      "command": "npx",
      "args": ["-y", "@shieldz/mcp"]
    }
  }
}

API-key tools (full merchant account)

Set SHIELDZ_API_KEY to additionally enable richer invoice management: create_invoice, get_invoice, list_invoices.

json

{
  "mcpServers": {
    "shieldz": {
      "command": "npx",
      "args": ["-y", "@shieldz/mcp"],
      "env": { "SHIELDZ_API_KEY": "sk_live_…" }
    }
  }
}

Get an API key from your merchant dashboard → Developers.

Environment

SHIELDZ_API_KEY (optional) — enables the invoice tools. Omit for keyless mode.
SHIELDZ_BASE_URL (optional) — defaults to https://shieldz.cash.

io.github.ShieldZCash/mcp

🛠️ Key Features

🚀 Use Cases

⚡ Developer Benefits

⚠️ Limitations

Topics

create_payment_link

create_tip_jar

get_account_status

@shieldz/mcp

Keyless tools (no account, no API key)

API-key tools (full merchant account)

Environment

License

Install

Configuration

Related servers

address	string	required	Destination wallet (0x EVM address); funds settle here.
amount_usd	number	required	Amount in USD, e.g. 49 for $49.00
chain	string	optional	Settlement chain (default base)
asset	string	optional	Stablecoin (default USDC)
memo	string	optional	Description shown on the checkout
email	string	optional	Optional, lets the owner claim a dashboard later