mcpField
S
Shieldz

Shieldz

Remote
shieldz.cashFinance0Updated 10w ago

About Shieldz

Shieldz is an MCP server for AI agents and merchants to accept non-custodial crypto payments and sell digital products. It offers keyless payment tools, with API-key access for expanded invoice management.

Key features

  1. 01Create one-time payment links
  2. 02Create reusable tip jars
  3. 03Sell pay-to-unlock digital products
  4. 04Check account and settlement details
  5. 05Manage invoices with an API key

Use cases

  1. 01Accept a fixed-amount crypto payment
  2. 02Collect flexible-amount tips
  3. 03Deliver a file link, license key, or secret after payment
  4. 04Review invoices and settlement details

MCP support

Exposes payment, tip jar, digital unlock, account-status, and invoice-management tools to MCP clients. It can be used through the hosted remote endpoint or run locally over stdio.

Configuration

Remote servers need no local install. Pick your client, then copy the config or install in one click.

Endpointhttps://shieldz.cash/mcp
Copy install command
Claude CodeTerminal
Cursor.cursor/mcp.json
VS Code.vscode/mcp.json
Claude Desktopclaude_desktop_config.json
Windsurf~/.codeium/windsurf/mcp_config.json

Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.

Packages
npm@shieldz/mcp0.3.0

Tools

3
ParameterTypeRequiredDescription
addressstringYesDestination wallet; funds settle here. Shieldz never holds them.
amount_usdnumberYesAmount in USD, e.g. 49 for $49.00
chainenumNoDefaults to basebase | arbitrum | optimism | polygon | ethereum
assetenumNoDefaults to USDCUSDC | USDT
memostringNoDescription shown on the checkout
emailstringNoOptional, lets the owner claim a dashboard later

Details

From the project 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:

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

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.