io.github.ShieldZCash/mcp
REMOTE · SHIELDZ.CASH · 2 COMPONENTS · SCANNED SEP 20
Keyless non-custodial crypto payments for AI agents: payment links and tip jars, no API key.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security60
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability66
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 835 tokens (~208/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage99
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 96% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.ShieldZCash/mcp server?
io.github.ShieldZCash/mcp is a hosted endpoint at https://shieldz.cash/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · shieldz.cash
claude mcp add --transport http shieldzcash-mcp 'https://shieldz.cash/mcp'
{
"mcpServers": {
"shieldzcash-mcp": {
"url": "https://shieldz.cash/mcp"
}
}
} {
"servers": {
"shieldzcash-mcp": {
"type": "http",
"url": "https://shieldz.cash/mcp"
}
}
} [mcp_servers.shieldzcash-mcp] url = "https://shieldz.cash/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"shieldzcash-mcp": {
"type": "remote",
"url": "https://shieldz.cash/mcp",
"enabled": true
}
}
} openclaw mcp add shieldzcash-mcp --url 'https://shieldz.cash/mcp' --transport streamable-http
mcp_servers:
shieldzcash-mcp:
url: "https://shieldz.cash/mcp" {
"McpServers": {
"shieldzcash-mcp": {
"Transport": "http",
"Url": "https://shieldz.cash/mcp"
}
}
} assistant mcp add shieldzcash-mcp -t streamable-http -u 'https://shieldz.cash/mcp'
{
"mcpServers": {
"shieldzcash-mcp": {
"type": "http",
"url": "https://shieldz.cash/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 26 Aug 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 24 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Aug 26 0
- Tool “create_unlock” rewrote its description, which is the text the model reads security
- Schema quality: good → excellent functional
- “create_unlock” reworded the description of “payload” cosmetic
- 17 Aug 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 154 → 199 ▼ functional
- Server version: 0.3.0 → 0.4.0 functional
- New tool “create_unlock” functional
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://shieldz.cash/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=shieldz.cash | CN=WE1,O=Google Trust Services,C=US | 1 Aug 2026 | 30 Oct 2026 | ECDSA 256 | ECDSA-SHA256 | 85f15bd33e473edc13945e392b555e26 |
| SANs: shieldz.cash, *.shieldz.cash | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of shieldz.cash. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| cash. | present | 38860 | 8 | Verified |
| shieldz.cash. | present | 2371 | 13 | Verified |
| shieldz.cash. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | same-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://shieldz.cash/mcp | Verified | 200 | |
| http (plaintext) | http://shieldz.cash/mcp | HTTPS enforced | 301 | https://shieldz.cash/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
create_payment_link ~165
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.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Destination wallet (0x EVM address); funds settle here. |
| amount_usd | number | yes | Amount in USD, e.g. 49 for $49.00 |
| asset | string | – | Stablecoin (default USDC) |
| chain | string | – | Settlement chain (default base) |
| string | – | Optional, lets the owner claim a dashboard later | |
| memo | string | – | Description shown on the checkout |
No output schema declared.
No examples provided.
create_tip_jar ~192
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.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Destination wallet (0x EVM address); funds settle here. |
| asset | string | – | Stablecoin (default USDC) |
| chain | string | – | Settlement chain (default base) |
| description | string | – | – |
| string | – | Optional, lets the owner claim a dashboard later | |
| slug | string | – | Optional custom URL slug |
| suggested_amounts_usd | array | – | Preset amount buttons in USD, e.g. [3, 5, 10] |
| title | string | – | Heading shown on the tip page, e.g. 'Buy me a coffee' |
No output schema declared.
No examples provided.
create_unlock ~333
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.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Destination wallet (0x EVM address); funds settle here. |
| asset | string | – | Stablecoin (default USDC) |
| aup_accepted | boolean | yes | Must be true: asserts the content complies with the acceptable-use policy (no adult, illegal, or non-consensual content). |
| chain | string | – | Settlement chain (default base) |
| description | string | – | Short pitch shown on the paywall |
| string | – | Optional, lets the owner claim a dashboard later | |
| payload | string | yes | The secret to reveal after payment: a URL or text, max 100000 chars. Never shown before payment. |
| price_usd | number | yes | Unlock price in USD, $1 to $100,000, e.g. 5 for $5.00 |
| title | string | – | What the buyer is purchasing, shown on the paywall |
No output schema declared.
No examples provided.
get_account_status ~74
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.
| Name | Type | Req | Description |
|---|---|---|---|
| manage_token | string | yes | The manage_token from create_payment_link / create_tip_jar |
No output schema declared.
No examples provided.
What is the io.github.ShieldZCash/mcp server?
io.github.ShieldZCash/mcp is listed in the public MCP registry as io.github.ShieldZCash/mcp. Keyless non-custodial crypto payments for AI agents: payment links and tip jars, no API key. This page covers its hosted endpoint (https://shieldz.cash/mcp).
Is the io.github.ShieldZCash/mcp server safe to use?
io.github.ShieldZCash/mcp scores 78 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.ShieldZCash/mcp server expose?
io.github.ShieldZCash/mcp exposes 4 tools: create_payment_link, create_tip_jar, create_unlock, get_account_status. Their descriptions and schemas cost roughly 764 tokens of context every time the server is loaded.
Does the io.github.ShieldZCash/mcp server require authentication?
No. We connected to io.github.ShieldZCash/mcp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.ShieldZCash/mcp server still maintained?
io.github.ShieldZCash/mcp is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.