io.github.onchainvanguard/scytheradar-mcp
NPM · SCYTHERADAR-MCP
Read-only bilingual screening, blacklist, fund tracing, rug-pull forensics. TRON dirty-USDT + EVM.
Available components
Last scanned (7 hours ago)
Scores higher than 33% of npm servers
Category Crypto and Web3
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 zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 93 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 3 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability70
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 689 tokens (~229/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 Management13
- Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
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
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 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 64
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 5 Nov 2026 · Analysed npm/scytheradar-mcp@0.1.2
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 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 30 |
| 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 →
check_blacklist ~242
Check whether an address or transaction hash matches a blacklist (Tether freezes / OFAC sanctions / phishing scams). Returns match type, source, and evidence. TRON coverage includes 9,000+ Tether freeze addresses plus a multi-chain OFAC list. Use to judge whether funds are tainted or safe to receive. 中文：检测地址或交易哈希是否命中黑名单（Tether 冻结 / OFAC 制裁 / 钓鱼诈骗），返回命中类型、来源与证据。TRON 覆盖 9000+ Tether 冻结地址 + OFAC 多链制裁。用于判断资金是否涉黑、能否安全接收。
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | Address to check (0x- or T-prefixed). Use either this or txhash |
| chain | string | – | Chain. Defaults to auto-detect. Options: bsc / ethereum / base / arbitrum / tron. 中文：链，默认 auto 自动识别，可选 bsc / ethereum / base / arbitrum / tron |
| txhash | string | – | Transaction hash. Use either this or address |
No output schema declared.
No examples provided.
screen_address ~231
Screen a wallet address for on-chain risk. Returns a 0-100 risk score, risk level, verdict, and matched risk flags (honeypot / mintable / owner-not-renounced / blacklist, etc). Supports EVM (0x...) and TRON (T...) addresses. Use before receiving funds, interacting with a contract, or investing. 中文：筛查链上地址风险，返回 0-100 风险分、风险等级、判定结论与命中的风险标记（蜜罐/可增发/Owner未放弃/黑名单等）。支持 EVM(0x…) 与 TRON(T…) 地址。收款、交互、投资前使用。
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Address to screen, 0x-prefixed (EVM) or T-prefixed (TRON) |
| chain | string | – | Chain. Defaults to auto-detect. Options: bsc / ethereum / base / arbitrum / tron. 中文：链，默认 auto 自动识别，可选 bsc / ethereum / base / arbitrum / tron |
No output schema declared.
No examples provided.
trace_funds ~216
Trace the flow of funds from an address or transaction, layer by layer. Returns fund exposure, hop addresses, final aggregation, and suspected laundering paths. Supports deep mode (slower but more complete). Use for tracing stolen funds or checking whether an incoming deposit passed through a mixer or sanctioned address. 中文：逐层溯源资金流向，返回资金暴露面、跳板地址、最终归集与疑似洗钱路径。支持 deep 深度模式。用于追赃、判断入账是否经过混币器或制裁地址。
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | Source address or transaction hash |
| chain | string | – | Chain. Defaults to auto-detect. Options: bsc / ethereum / base / arbitrum / tron. 中文：链，默认 auto 自动识别，可选 bsc / ethereum / base / arbitrum / tron |
| deep | boolean | – | Deep trace, default false |
| target | string | – | Trace target address (equivalent to address, use either) |
No output schema declared.
No examples provided.
How do I install the io.github.onchainvanguard/scytheradar-mcp server?
io.github.onchainvanguard/scytheradar-mcp runs locally as an npm package, launched with npx -y scytheradar-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 · scytheradar-mcp
claude mcp add onchainvanguard-scytheradar-mcp -- npx -y scytheradar-mcp
What is the io.github.onchainvanguard/scytheradar-mcp server?
io.github.onchainvanguard/scytheradar-mcp is listed in the public MCP registry as io.github.onchainvanguard/scytheradar-mcp. Read-only bilingual screening, blacklist, fund tracing, rug-pull forensics. TRON dirty-USDT + EVM. This page covers its npm package (scytheradar-mcp).
Is the io.github.onchainvanguard/scytheradar-mcp server safe to use?
io.github.onchainvanguard/scytheradar-mcp scores 66 out of 100 on VerifyMCP. We recorded 1 known advisory 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.onchainvanguard/scytheradar-mcp server expose?
io.github.onchainvanguard/scytheradar-mcp exposes 3 tools: screen_address, check_blacklist, trace_funds. Their descriptions and schemas cost roughly 689 tokens of context every time the server is loaded.
Is the io.github.onchainvanguard/scytheradar-mcp server still maintained?
io.github.onchainvanguard/scytheradar-mcp 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.onchainvanguard/scytheradar-mcp server under?
io.github.onchainvanguard/scytheradar-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.