io.github.kaito3636/x402-presign-guard
NPM · X402-PRESIGN-GUARD
Pre-sign EVM tx/approval safety for AI agents: decode calldata, flag drainers, return GO/HOLD/BLOCK.
Available components
+5 this week
65 65 Trust /100
Last scanned (2 hours ago)
Scores higher than 33% of npm servers
Category Security
Trust breakdown (7 categories)
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 Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects hono 4.6.14, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 94 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 11 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability61
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 164 tokens (~82/item across 2 items; 2 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management40
- Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 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
Changelog
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.
- 5 Nov 26 0
- CVE-2026-56764 affects this package: high ▼ security
- CVE-2026-56763 affects this package: high ▼ security
- CVE-2026-44459 affects this package: high ▼ security
- CVE-2026-24771 affects this package: high ▼ security
- CVE-2026-29086 affects this package: high ▼ security
- CVE-2026-29045 affects this package: high ▼ security
- CVE-2026-24398 affects this package: high ▼ security
- CVE-2026-39407 affects this package: high ▼ security
- CVE-2026-71850 affects this package: high ▼ security
- CVE-2025-59139 affects this package: high ▼ security
- CVE-2026-54286 affects this package: high ▼ security
- CVE-2026-47674 affects this package: high ▼ security
- CVE-2026-39410 affects this package: high ▼ security
- CVE-2026-54287 affects this package: high ▼ security
- CVE-2026-56762 affects this package: high ▼ security
- CVE-2026-29085 affects this package: high ▼ security
- CVE-2026-44458 affects this package: high ▼ security
- CVE-2026-54288 affects this package: high ▼ security
- CVE-2026-69207 affects this package: high ▼ security
- CVE-2026-44456 affects this package: high ▼ security
- CVE-2026-39408 affects this package: high ▼ security
- CVE-2026-54290 affects this package: high ▼ security
- CVE-2026-44455 affects this package: high ▼ security
- CVE-2026-44457 affects this package: high ▼ security
- CVE-2026-22817 affects this package: high ▼ security
- CVE-2026-84364 affects this package: high ▼ security
- CVE-2026-84363 affects this package: high ▼ security
- CVE-2026-56761 affects this package: high ▼ security
- CVE-2026-39409 affects this package: high ▼ security
- CVE-2026-54289 affects this package: high ▼ security
- CVE-2026-47675 affects this package: high ▼ security
- CVE-2026-24472 affects this package: high ▼ security
- CVE-2026-47676 affects this package: high ▼ security
- CVE-2026-24473 affects this package: high ▼ security
- CVE-2026-59897 affects this package: high ▼ security
- CVE-2026-93981 affects this package: high ▼ security
- CVE-2025-71381 affects this package: high ▼ security
- CVE-2026-59895 affects this package: high ▼ security
- CVE-2026-47673 affects this package: high ▼ security
- CVE-2025-62610 affects this package: high ▼ security
- CVE-2026-118663 affects this package: high ▼ security
- CVE-2026-22818 affects this package: high ▼ security
- CVE-2026-84365 affects this package: high ▼ security
- 4 Nov 26 +5
- CVE-2026-56764 affects this package: high ▼ security
- CVE-2026-56763 affects this package: high ▼ security
- CVE-2026-44459 affects this package: high ▼ security
- CVE-2026-24771 affects this package: high ▼ security
- CVE-2026-29086 affects this package: high ▼ security
- CVE-2026-29045 affects this package: high ▼ security
- CVE-2026-24398 affects this package: high ▼ security
- CVE-2026-39407 affects this package: high ▼ security
- CVE-2026-71850 affects this package: high ▼ security
- CVE-2025-59139 affects this package: high ▼ security
- CVE-2026-54286 affects this package: high ▼ security
- CVE-2026-47674 affects this package: high ▼ security
- CVE-2026-39410 affects this package: high ▼ security
- CVE-2026-54287 affects this package: high ▼ security
- CVE-2026-56762 affects this package: high ▼ security
- CVE-2026-29085 affects this package: high ▼ security
- CVE-2026-44458 affects this package: high ▼ security
- CVE-2026-54288 affects this package: high ▼ security
- CVE-2026-69207 affects this package: high ▼ security
- CVE-2026-44456 affects this package: high ▼ security
- CVE-2026-39408 affects this package: high ▼ security
- CVE-2026-54290 affects this package: high ▼ security
- CVE-2026-44455 affects this package: high ▼ security
- CVE-2026-44457 affects this package: high ▼ security
- CVE-2026-22817 affects this package: high ▼ security
- CVE-2026-84364 affects this package: high ▼ security
- CVE-2026-84363 affects this package: high ▼ security
- CVE-2026-56761 affects this package: high ▼ security
- CVE-2026-39409 affects this package: high ▼ security
- CVE-2026-54289 affects this package: high ▼ security
- CVE-2026-47675 affects this package: high ▼ security
- CVE-2026-24472 affects this package: high ▼ security
- CVE-2026-47676 affects this package: high ▼ security
- CVE-2026-24473 affects this package: high ▼ security
- CVE-2026-59897 affects this package: high ▼ security
- CVE-2026-93981 affects this package: high ▼ security
- CVE-2025-71381 affects this package: high ▼ security
- CVE-2026-59895 affects this package: high ▼ security
- CVE-2026-47673 affects this package: high ▼ security
- CVE-2025-62610 affects this package: high ▼ security
- CVE-2026-118663 affects this package: high ▼ security
- CVE-2026-22818 affects this package: high ▼ security
- CVE-2026-84365 affects this package: high ▼ security
- Stability: unverified → 0.37 ▲ functional
- 3 Nov 26 0
- CVE-2026-56764 affects this package: high ▼ security
- CVE-2026-56763 affects this package: high ▼ security
- CVE-2026-44459 affects this package: high ▼ security
- CVE-2026-24771 affects this package: high ▼ security
- CVE-2026-29086 affects this package: high ▼ security
- CVE-2026-29045 affects this package: high ▼ security
- CVE-2026-24398 affects this package: high ▼ security
- CVE-2026-39407 affects this package: high ▼ security
- CVE-2026-71850 affects this package: high ▼ security
- CVE-2025-59139 affects this package: high ▼ security
- CVE-2026-54286 affects this package: high ▼ security
- CVE-2026-47674 affects this package: high ▼ security
- CVE-2026-39410 affects this package: high ▼ security
- CVE-2026-54287 affects this package: high ▼ security
- CVE-2026-56762 affects this package: high ▼ security
- CVE-2026-29085 affects this package: high ▼ security
- CVE-2026-44458 affects this package: high ▼ security
- CVE-2026-54288 affects this package: high ▼ security
- CVE-2026-69207 affects this package: high ▼ security
- CVE-2026-44456 affects this package: high ▼ security
- CVE-2026-39408 affects this package: high ▼ security
- CVE-2026-54290 affects this package: high ▼ security
- CVE-2026-44455 affects this package: high ▼ security
- CVE-2026-44457 affects this package: high ▼ security
- CVE-2026-22817 affects this package: high ▼ security
- CVE-2026-84364 affects this package: high ▼ security
- CVE-2026-84363 affects this package: high ▼ security
- CVE-2026-56761 affects this package: high ▼ security
- CVE-2026-39409 affects this package: high ▼ security
- CVE-2026-54289 affects this package: high ▼ security
- CVE-2026-47675 affects this package: high ▼ security
- CVE-2026-24472 affects this package: high ▼ security
- CVE-2026-47676 affects this package: high ▼ security
- CVE-2026-24473 affects this package: high ▼ security
- CVE-2026-59897 affects this package: high ▼ security
- CVE-2026-93981 affects this package: high ▼ security
- CVE-2025-71381 affects this package: high ▼ security
- CVE-2026-59895 affects this package: high ▼ security
- CVE-2026-47673 affects this package: high ▼ security
- CVE-2025-62610 affects this package: high ▼ security
- CVE-2026-118663 affects this package: high ▼ security
- CVE-2026-22818 affects this package: high ▼ security
- CVE-2026-84365 affects this package: high ▼ security
- 2 Nov 26 0
- CVE-2026-56764 affects this package: high ▼ security
- CVE-2026-56763 affects this package: high ▼ security
- CVE-2026-44459 affects this package: high ▼ security
- CVE-2026-24771 affects this package: high ▼ security
- CVE-2026-29086 affects this package: high ▼ security
- CVE-2026-29045 affects this package: high ▼ security
- CVE-2026-24398 affects this package: high ▼ security
- CVE-2026-39407 affects this package: high ▼ security
- CVE-2026-71850 affects this package: high ▼ security
- CVE-2025-59139 affects this package: high ▼ security
- CVE-2026-54286 affects this package: high ▼ security
- CVE-2026-47674 affects this package: high ▼ security
- CVE-2026-39410 affects this package: high ▼ security
- CVE-2026-54287 affects this package: high ▼ security
- CVE-2026-56762 affects this package: high ▼ security
- CVE-2026-29085 affects this package: high ▼ security
- CVE-2026-44458 affects this package: high ▼ security
- CVE-2026-54288 affects this package: high ▼ security
- CVE-2026-69207 affects this package: high ▼ security
- CVE-2026-44456 affects this package: high ▼ security
- CVE-2026-39408 affects this package: high ▼ security
- CVE-2026-54290 affects this package: high ▼ security
- CVE-2026-44455 affects this package: high ▼ security
- CVE-2026-44457 affects this package: high ▼ security
- CVE-2026-22817 affects this package: high ▼ security
- CVE-2026-84364 affects this package: high ▼ security
- CVE-2026-84363 affects this package: high ▼ security
- CVE-2026-56761 affects this package: high ▼ security
- CVE-2026-39409 affects this package: high ▼ security
- CVE-2026-54289 affects this package: high ▼ security
- CVE-2026-47675 affects this package: high ▼ security
- CVE-2026-24472 affects this package: high ▼ security
- CVE-2026-47676 affects this package: high ▼ security
- CVE-2026-24473 affects this package: high ▼ security
- CVE-2026-59897 affects this package: high ▼ security
- CVE-2026-93981 affects this package: high ▼ security
- CVE-2025-71381 affects this package: high ▼ security
- CVE-2026-59895 affects this package: high ▼ security
- CVE-2026-47673 affects this package: high ▼ security
- CVE-2025-62610 affects this package: high ▼ security
- CVE-2026-118663 affects this package: high ▼ security
- CVE-2026-22818 affects this package: high ▼ security
- CVE-2026-84365 affects this package: high ▼ security
- 1 Nov 26 0
We did not load change detail this far back for this component, so this day may have recorded more than is shown.
- CVE-2026-56764 affects this package: high ▼ security
- CVE-2026-56763 affects this package: high ▼ security
- CVE-2026-44459 affects this package: high ▼ security
- CVE-2026-24771 affects this package: high ▼ security
- CVE-2026-29086 affects this package: high ▼ security
- CVE-2026-29045 affects this package: high ▼ security
- CVE-2026-24398 affects this package: high ▼ security
- CVE-2026-39407 affects this package: high ▼ security
- CVE-2026-71850 affects this package: high ▼ security
- CVE-2025-59139 affects this package: high ▼ security
- CVE-2026-54286 affects this package: high ▼ security
- CVE-2026-47674 affects this package: high ▼ security
- CVE-2026-39410 affects this package: high ▼ security
- CVE-2026-54287 affects this package: high ▼ security
- CVE-2026-56762 affects this package: high ▼ security
- CVE-2026-29085 affects this package: high ▼ security
- CVE-2026-44458 affects this package: high ▼ security
- CVE-2026-54288 affects this package: high ▼ security
- CVE-2026-69207 affects this package: high ▼ security
- CVE-2026-44456 affects this package: high ▼ security
- CVE-2026-39408 affects this package: high ▼ security
- CVE-2026-54290 affects this package: high ▼ security
- CVE-2026-44455 affects this package: high ▼ security
- CVE-2026-44457 affects this package: high ▼ security
- CVE-2026-22817 affects this package: high ▼ security
- CVE-2026-84364 affects this package: high ▼ security
- 25 Oct 26 +15
We did not load change detail this far back for this component, so this day may have recorded more than is shown.
- 24 Oct 26 45
First indexed and scored.
Diagnostics
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 5 Nov 2026 · Analysed npm/x402-presign-guard@0.1.1
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 →
Vulnerabilities 43 findings
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-rmxm-3fg6-px4f | CVE-2026-118663 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N | yes |
| GHSA-26pp-8wgv-hjvm | CVE-2026-56762 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L | yes |
| GHSA-2gcr-mfcq-wcc3 | CVE-2026-47676 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N | yes |
| GHSA-3hrh-pfw6-9m5x | CVE-2026-47675 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N | yes |
| GHSA-3vhc-576x-3qv4 | CVE-2026-22818 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N | yes |
| GHSA-458j-xx4x-4375 | CVE-2026-56761 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N | yes |
| GHSA-5pq2-9x2x-5p6w | CVE-2026-29086 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N | yes |
| GHSA-69xw-7hcm-h432 | CVE-2026-44455 | medium | CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:L/A:N | yes |
| GHSA-6wqw-2p9w-4vw4 | CVE-2026-24472 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N | yes |
| GHSA-88fw-hqm2-52qc | CVE-2026-54290 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:N | yes |
| GHSA-8j4g-w8fx-2239 | CVE-2026-69207 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L | yes |
| GHSA-92vj-g62v-jqhh | CVE-2025-59139 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L | yes |
| GHSA-9r54-q6cx-xmh5 | CVE-2026-24771 | medium | CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:L/A:N | yes |
| GHSA-9vqf-7f2p-gf9v | CVE-2026-44456 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N | yes |
| GHSA-crvj-82cr-hjcx | CVE-2026-84363 | medium | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N | yes |
| GHSA-f23p-vx2j-j53r | CVE-2026-71850 | medium | CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:N/A:N | yes |
| GHSA-f577-qrjj-4474 | CVE-2026-47673 | medium | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N | yes |
| GHSA-f67f-6cw9-8mq4 | CVE-2026-22817 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N | yes |
| GHSA-g6gw-c38x-mqfc | CVE-2026-84364 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L | yes |
| GHSA-gq3j-xvxp-8hrf | CVE-2026-56764 | low | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N | yes |
| GHSA-gqvv-2mrq-wpjv | CVE-2026-84365 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N | yes |
| GHSA-hm8q-7f3q-5f36 | CVE-2026-44459 | low | CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:N | yes |
| GHSA-hxh3-vqpv-xpqv | CVE-2026-93981 | medium | CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:L/A:N | yes |
| GHSA-j6c9-x7qj-28xf | CVE-2026-54287 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N | yes |
| GHSA-m732-5p4w-x69g | CVE-2025-62610 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N | yes |
| GHSA-p6xx-57qc-3wxr | CVE-2026-29085 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N | yes |
| GHSA-p77w-8qqv-26rm | CVE-2026-44457 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N | yes |
| GHSA-q5qw-h33p-qvwr | CVE-2026-29045 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N | yes |
| GHSA-q7jf-gf43-6x6p | CVE-2025-71381 | medium | CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:N | yes |
| GHSA-qp7p-654g-cw7p | CVE-2026-44458 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N | yes |
| GHSA-r354-f388-2fhh | CVE-2026-24398 | medium | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N | yes |
| GHSA-r5rp-j6wh-rvv4 | CVE-2026-39410 | medium | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N | yes |
| GHSA-rv63-4mwf-qqc2 | CVE-2026-54288 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N | yes |
| GHSA-v8w9-8mx6-g223 | CVE-2026-56763 | medium | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N | yes |
| GHSA-w332-q679-j88p | CVE-2026-24473 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N | yes |
| GHSA-w62v-xxxg-mg59 | CVE-2026-59895 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N | yes |
| GHSA-wgpf-jwqj-8h8p | CVE-2026-54289 | medium | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N | yes |
| GHSA-wmmm-f939-6g9c | CVE-2026-39407 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N | yes |
| GHSA-wwfh-h76j-fc44 | CVE-2026-54286 | medium | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N | yes |
| GHSA-xf4j-xp2r-rqqx | CVE-2026-39408 | medium | yes | |
| GHSA-xgm2-5f3f-mvvc | CVE-2026-59897 | medium | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N | yes |
| GHSA-xpcf-pg52-r92g | CVE-2026-39409 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N | yes |
| GHSA-xrhx-7g5j-rcj5 | CVE-2026-47674 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 94 packages
| Packages resolved | 94 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
MCP tools
· 2 exposed
· ~164 tokens
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 →
Tool
Tokens
presign_guard_approval ~68
Check whether a token approval is safe to sign. Flags unlimited allowances and approvals to known-malicious spenders. Returns GO / HOLD / BLOCK.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | string | – | – |
| chain | string | – | – |
| spender | string | yes | – |
| token | string | yes | – |
No output schema declared.
No examples provided.
presign_guard_tx ~96
Check whether an EVM transaction is safe to sign BEFORE signing it. Decodes the calldata, flags wallet-drainer patterns (unlimited approvals, setApprovalForAll, gasless permits, transfers/approvals to known-malicious addresses) and returns a GO / HOLD / BLOCK verdict.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | – | – |
| data | string | – | – |
| to | string | – | – |
| value | string | – | – |
No output schema declared.
No examples provided.
Install
How do I install the io.github.kaito3636/x402-presign-guard MCP server?
io.github.kaito3636/x402-presign-guard runs locally as an npm package, launched with npx -y x402-presign-guard. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · x402-presign-guard
# add to Claude Code
claude mcp add kaito3636-x402-presign-guard -- npx -y x402-presign-guard
Common questions
What is the io.github.kaito3636/x402-presign-guard MCP server?
io.github.kaito3636/x402-presign-guard is an MCP server listed in the public MCP registry as io.github.kaito3636/x402-presign-guard. Pre-sign EVM tx/approval safety for AI agents: decode calldata, flag drainers, return GO/HOLD/BLOCK. This page covers its npm package (x402-presign-guard).
Is the io.github.kaito3636/x402-presign-guard MCP server safe to use?
io.github.kaito3636/x402-presign-guard scores 65 out of 100 on VerifyMCP. We recorded 43 known advisories against it as of 5 November 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.kaito3636/x402-presign-guard MCP server expose?
io.github.kaito3636/x402-presign-guard exposes 2 tools: presign_guard_tx, presign_guard_approval. Their descriptions and schemas cost roughly 164 tokens of context every time the server is loaded.
Is the io.github.kaito3636/x402-presign-guard MCP server still maintained?
io.github.kaito3636/x402-presign-guard is still listed as active in the MCP registry. We last reached this channel on 5 November 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.kaito3636/x402-presign-guard MCP server under?
io.github.kaito3636/x402-presign-guard declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.