ShieldZCash

io.github.ShieldZCashPublished by GitHub account ShieldZCashv0.3.0Updated Oct 24, 2026

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

VerifiedStreamable HTTPWeb executableFinanceBusiness & Commerce

Overview

AI-generated overview

Shieldz MCP server lets an AI assistant create non-custodial crypto payment links, tip jars and pay-to-unlock pages that settle to a wallet address you supply.

What you can do
  • Create one-time crypto payment links with a shareable URL, embeddable button and QR
  • Create reusable pay-what-you-want tip jars, idempotent per wallet address
  • Create pay-to-unlock pages that reveal a file link, license key or secret text after the buyer's crypto payment is confirmed
  • Look up settlement details, tip jars, totals and invoices by manage token
  • With an API key, create, fetch and list merchant invoices
When to use it
Useful when an assistant needs to let someone pay in crypto with minimal setup — charging for a digital product, collecting tips, or issuing a payment link — without holding funds or keys. The keyless tools work with no account; the invoice tools suit merchants who already have a Shieldz account.
Requirements
Runs as a hosted remote endpoint or locally via npx (Node.js). Keyless tools need only a destination wallet address. Invoice tools need SHIELDZ_API_KEY (sk_live_ or sk_test_); SHIELDZ_BASE_URL is optional. Network access to the Shieldz service is required.
Before you install
The server creates live payment pages and pay-to-unlock products that take real crypto payments, so amounts and destination wallet addresses should be checked before use. A manage token returned at creation grants access to account status, so treat it as a secret. The optional SHIELDZ_API_KEY is a merchant credential. Payment and buyer data are sent to the Shieldz service.

Installation

In SourceWeft

  1. Open ShieldZCash in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.ShieldZCash%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "shieldzcash": {
      "type": "http",
      "url": "https://shieldz.cash/mcp"
    }
  }
}

README

@shieldz/mcp

[npm]

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.

License

MIT © Deniz Yanbollu / Shieldz

Source: README.md at commit f135060

Tools

4

create_tip_jar

Create a reusable 'pay what you want' tip jar with ZERO setup. The payer chooses the amount. Returns a shareable /tip url, an embeddable button, and a manage_url. Idempotent per wallet address. Non-custodial.

Parametersslugassetchainemailtitleaddressrequireddescriptionsuggested_amounts_usd

create_unlock

Create a keyless pay-to-unlock page: sell a file link, license key, or secret text (up to 100,000 chars). The buyer pays the set USD price in crypto straight to the given wallet, then the payload is revealed on their paid confirmation, never before. To deliver an actual file (PDF/zip/etc, 10 MB) use the multipart HTTP API at /api/v1/unlocks instead. Non-custodial, no account, no API key. IMPORTANT: the acceptable-use policy forbids adult, illegal, or non-consensual content; confirm this with your principal and pass aup_accepted=true, otherwise the call fails.

Parametersassetchainemailtitleaddressrequiredpayloadrequiredprice_usdrequireddescriptionaup_acceptedrequired

get_account_status

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 invoice list as structured JSON.

Parametersmanage_tokenrequired

Version history

1
  1. v0.3.0LatestSep 16, 2026

Score

100% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts