io.github.ShieldZCash/mcp
NPM · @SHIELDZ/MCP · 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 from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 97 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 84 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability75
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 468 tokens (~156/item across 3 items; 3 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 Management93
- Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage98
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 93% 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 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 runs locally as an npm package, launched with npx -y @shieldz/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @shieldz/mcp
claude mcp add shieldzcash-mcp -- npx -y @shieldz/mcp
{
"mcpServers": {
"shieldzcash-mcp": {
"command": "npx",
"args": [
"-y",
"@shieldz/mcp"
]
}
}
} {
"servers": {
"shieldzcash-mcp": {
"command": "npx",
"args": [
"-y",
"@shieldz/mcp"
]
}
}
} codex mcp add shieldzcash-mcp -- npx -y @shieldz/mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"shieldzcash-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"@shieldz/mcp"
],
"enabled": true
}
}
} openclaw mcp add shieldzcash-mcp --command npx --arg -y --arg @shieldz/mcp
mcp_servers:
shieldzcash-mcp:
command: "npx"
args: ["-y", "@shieldz/mcp"] {
"McpServers": {
"shieldzcash-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@shieldz/mcp"
]
}
}
} assistant mcp add shieldzcash-mcp -t stdio -c npx -a -y @shieldz/mcp
{
"mcpServers": {
"shieldzcash-mcp": {
"command": "npx",
"args": [
"-y",
"@shieldz/mcp"
]
}
}
} 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.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 −3
- Stability: pass → 0.83 functional
- 16 Sept 26 +1
- Stability: 0.97 → pass security
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 −3
- Stability: pass → 0.80 functional
- 9 Sept 26 +1
- Stability: 0.97 → pass security
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 · Analysed npm/@shieldz/mcp@0.3.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 97 packages
| Packages resolved | 97 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 ~176
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. Optionally pass an email so the owner can claim a full dashboard later.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Destination wallet; funds settle here. Shieldz never holds them. |
| amount_usd | number | yes | Amount in USD, e.g. 49 for $49.00 |
| asset | string | – | Defaults to USDC |
| chain | string | – | Defaults to 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 ~217
Create a reusable 'pay what you want' tip jar with ZERO setup, no account, no API key. The payer chooses the amount. Returns a shareable /tip url, an embeddable button, and a manage_url. Idempotent per wallet address: calling again updates the same tip jar. Non-custodial: funds settle directly to the address you provide.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Destination wallet; funds settle here. Shieldz never holds them. |
| asset | string | – | Defaults to USDC |
| chain | string | – | Defaults to base |
| description | string | – | – |
| string | – | Optional, lets the owner claim a dashboard later | |
| slug | string | – | Optional custom URL slug; auto-generated if omitted |
| 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.
get_account_status ~75
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 full 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 npm package (@shieldz/mcp).
Is the io.github.ShieldZCash/mcp server safe to use?
io.github.ShieldZCash/mcp scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. 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 3 tools: create_payment_link, create_tip_jar, get_account_status. Their descriptions and schemas cost roughly 468 tokens of context every time the server is loaded.
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.
What licence is the io.github.ShieldZCash/mcp server under?
io.github.ShieldZCash/mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.