io.github.ShieldZCash/mcp
NPM · @SHIELDZ/MCP · 2 COMPONENTS · SCANNED AUG 3
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 →
Supply Chain Security87
- No malware found by supply-chain analysis.Pass
- Only part of the dependency tree could be resolved (96 of 100), so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Only part of the dependency tree could be resolved (96 of 100), so this covers what we could see, not the whole tree. 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 36 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability73
- 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 Management27
- Stability observed for 8 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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · @shieldz/mcp
claude mcp add shieldzcash-mcp -- npx -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": {
"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.
- 3 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Aug 26 +63
- Provenance: unverified → fail ▼ security
- Known CVEs: unverified → partial ▲ security
- Install scripts: unverified → pass ▲ security
- Malware scan: unverified → pass ▲ security
- License: unverified → pass ▲ functional
- Dependency health: unverified → partial ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Maintenance: unverified → pass ▲ functional
- Schema quality: unverified → excellent ▲ functional
- Stability: unverified → 0.23 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Licence: MIT functional
- 1 Aug 26 −15
- Tool coverage: 100 → unverified ▼ functional
- 31 Jul 26 −4
- 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 −21
- Tool coverage: 100 → unverified ▼ functional
- 28 Jul 26 +21
- Tool coverage: unverified → 100 ▲ functional
- First check of Schema quality: fail functional
- First check of Schema quality: unverified functional
- First check of Schema quality: fail functional
- First check of Tool coverage: 93 functional
- 27 Jul 26 24
First indexed and scored.
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 3 Aug 2026 · Analysed npm/@shieldz/[email protected]
Provenance none
Ecosystem: npm · Outcome: none
Dependencies 96 packages
96 packages in the resolved dependency tree · 95 deprecated · 29 stale.
The dependency tree was only partially resolved, so these counts may be incomplete.
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.
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.