Is the Shieldzcash MCP server down?

mcp-registry/io.github.shieldzcash/mcp · v0.4.0

Also listed as awesome/shieldzcash/shieldz-mcp, glama/shieldzcash/shieldz-crypto-payments

healthy
Last checked 2026-10-26 22:33 UTC · handshake 644ms

As of 2026-10-26 22:33 UTC, the Shieldzcash MCP server is up with a Glimind reliability score of 93/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 8 outages in 90 days, with a median recovery of 7 minutes.

uptime (30d checks)
100%
checks observed
4,936
outages (90d)
8
tools
4

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

Point your MCP client at this streamable-http endpoint: https://shieldz.cash/mcp

Agent-readiness: C (75/100)

C (75/100): 0 error(s), 3 warning(s) across 4 tool(s); ~1,143 tokens of tool definitions.
Scores higher than 10% of 15,781 MCP servers Glimind has audited.
Its tool list costs an agent ~1,143 tokens per session — lighter than 75% of servers.
74 → 75 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions73
Safety hints0
Token cost100
Client compatibility70
Protocol100
Reliability100
Stability100

What to fix (4)

4 of 4 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →

Tools: create_payment_link, create_tip_jar, create_unlock, get_account_status

3 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.

Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →

Tools: create_payment_link, create_tip_jar, create_unlock

1 parameter(s) across 1 tool(s) have no description.

Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →

Tools: create_tip_jar

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →

Auto-fix: 4 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 1 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.shieldzcash%2Fmcp/fixes

create_payment_link 1 change
{
  "name": "create_payment_link",
  "description": "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.",
  "inputSchema": {
    "type": "object",
    "required": [
      "address",
      "amount_usd"
    ],
    "properties": {
      "memo": {
        "type": "string",
        "description": "Description shown on the checkout"
      },
      "asset": {
        "enum": [
          "USDC",
          "USDT"
        ],
        "type": "string",
        "description": "Stablecoin (default USDC)"
      },
      "chain": {
        "enum": [
          "base",
          "arbitrum",
          "optimism",
          "polygon",
          "ethereum"
        ],
        "type": "string",
        "description": "Settlement chain (default base)"
      },
      "email": {
        "type": "string",
        "description": "Optional, lets the owner claim a dashboard later"
      },
      "address": {
        "type": "string",
        "description": "Destination wallet (0x EVM address); funds settle here."
      },
      "amount_usd": {
        "type": "number",
        "description": "Amount in USD, e.g. 49 for $49.00"
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  }
}
create_tip_jar 1 change
{
  "name": "create_tip_jar",
  "description": "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.",
  "inputSchema": {
    "type": "object",
    "required": [
      "address"
    ],
    "properties": {
      "slug": {
        "type": "string",
        "description": "Optional custom URL slug"
      },
      "asset": {
        "enum": [
          "USDC",
          "USDT"
        ],
        "type": "string",
        "description": "Stablecoin (default USDC)"
      },
      "chain": {
        "enum": [
          "base",
          "arbitrum",
          "optimism",
          "polygon",
          "ethereum"
        ],
        "type": "string",
        "description": "Settlement chain (default base)"
      },
      "email": {
        "type": "string",
        "description": "Optional, lets the owner claim a dashboard later"
      },
      "title": {
        "type": "string",
        "description": "Heading shown on the tip page, e.g. 'Buy me a coffee'"
      },
      "address": {
        "type": "string",
        "description": "Destination wallet (0x EVM address); funds settle here."
      },
      "description": {
        "type": "string"
      },
      "suggested_amounts_usd": {
        "type": "array",
        "items": {
          "type": "number"
        },
        "description": "Preset amount buttons in USD, e.g. [3, 5, 10]"
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  }
}
create_unlock 1 change
{
  "name": "create_unlock",
  "description": "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 you",
  "inputSchema": {
    "type": "object",
    "required": [
      "address",
      "price_usd",
      "payload",
      "aup_accepted"
    ],
    "properties": {
      "asset": {
        "enum": [
          "USDC",
          "USDT"
        ],
        "type": "string",
        "description": "Stablecoin (default USDC)"
      },
      "chain": {
        "enum": [
          "base",
          "arbitrum",
          "optimism",
          "polygon",
          "ethereum"
        ],
        "type": "string",
        "description": "Settlement chain (default base)"
      },
      "email": {
        "type": "string",
        "description": "Optional, lets the owner claim a dashboard later"
      },
      "title": {
        "type": "string",
        "description": "What the buyer is purchasing, shown on the paywall"
      },
      "address": {
        "type": "string",
        "description": "Destination wallet (0x EVM address); funds settle here."
      },
      "payload": {
        "type": "string",
        "description": "The secret to reveal after payment: a URL or text, max 100000 chars. Never shown before payment."
      },
      "price_usd": {
        "type": "number",
        "description": "Unlock price in USD, $1 to $100,000, e.g. 5 for $5.00"
      },
      "description": {
        "type": "string",
        "description": "Short pitch shown on the paywall"
      },
      "aup_accepted": {
        "type": "boolean",
        "description": "Must be true: asserts the content complies with the acceptable-use policy (no adult, illegal, or non-consensual content)."
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  }
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.shieldzcash/mcp"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/io.github.shieldzcash/mcp"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

Markdown
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.shieldzcash%2Fmcp.svg)](https://glimind.com/server/mcp-registry%2Fio.github.shieldzcash%2Fmcp?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fio.github.shieldzcash%2Fmcp?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.shieldzcash%2Fmcp.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.shieldzcash%2Fmcp.svg
   :target: https://glimind.com/server/mcp-registry%2Fio.github.shieldzcash%2Fmcp?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:05c25daa4c2e4818…, first seen 2026-10-17, included at leaf 14268 of 75,845. Version history · verify what your client received.

Tools (4)

Compare: most reliable payments servers · most reliable finance servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Shieldzcash MCP server down right now?

As of 2026-10-26 22:33 UTC, the Shieldzcash MCP server is up with a Glimind reliability score of 93/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 8 outages in 90 days, with a median recovery of 7 minutes.

How many tools does Shieldzcash MCP server provide?

Shieldzcash MCP server advertises 4 tools, including create_payment_link, create_tip_jar, create_unlock, get_account_status.

How do I install Shieldzcash MCP server?

Point your MCP client at this streamable-http endpoint: https://shieldz.cash/mcp

Is the Shieldzcash MCP server safe to connect to an AI agent?

Glimind scanned all 4 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Shieldzcash MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.

Feedback
Help us improve