io.github.ShieldZCash/mcp

Official registry Finance and payments

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

What can you do with io.github.ShieldZCash/mcp?

  • 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...
  • get_account_status — look up settlement details, tip jars, totals, and invoices by manage_token.

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

Remote (streamable-http)
Claude Code
claude mcp add --transport http io-github-shieldzcash-mcp 'https://shieldz.cash/mcp'
JSON configuration (Claude Desktop, Cursor, VS Code)
{
    "mcpServers": {
        "io-github-shieldzcash-mcp": {
            "type": "http",
            "url": "https://shieldz.cash/mcp"
        }
    }
}
NPM package @shieldz/mcp
Claude Code
claude mcp add io-github-shieldzcash-mcp -e 'SHIELDZ_API_KEY=<your shieldz_api_key>' -- npx -y @shieldz/mcp@0.3.0
JSON configuration (Claude Desktop, Cursor, VS Code)
{
    "mcpServers": {
        "io-github-shieldzcash-mcp": {
            "command": "npx",
            "args": [
                "-y",
                "@shieldz/mcp@0.3.0"
            ],
            "env": {
                "SHIELDZ_API_KEY": "<your shieldz_api_key>"
            }
        }
    }
}

Environment variables

  • SHIELDZ_API_KEY secret Optional. Set a sk_live_/sk_test_ key to additionally enable full invoice management tools. Omit for keyless mode.

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. @shieldz/mcp
  2. Keyless tools (no account, no API key)
  3. API-key tools (full merchant account)
  4. License

@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:

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

Local (stdio) — run via npx:

{
  "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.

{
  "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

Frequently asked questions

What is io.github.ShieldZCash/mcp?

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

How do I install io.github.ShieldZCash/mcp?

It runs as a remote server. In Claude Code: claude mcp add --transport http io-github-shieldzcash-mcp 'https://shieldz.cash/mcp'. For other clients, paste the JSON configuration from this page into their MCP settings.

Does io.github.ShieldZCash/mcp need an API key?

Yes. It expects SHIELDZ_API_KEY, which you set in its configuration.

Is io.github.ShieldZCash/mcp open source?

Yes. Its code is on GitHub under the MIT license.

Who maintains io.github.ShieldZCash/mcp?

It is published by ShieldZCash. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.