Loading the registry…
Production-ready MCP server for crypto trading automation with AI decision support
We found this by crawling public sources and nobody has attested to it. That is how most of the registry gets here, and it is not a mark against the artifact — it only means no authenticated act of publication is on record. An artifact can be the vendor's own and still appear here.
3 critical findings reported by osv-scanner. The composite score alone does not reflect this — read the per-scanner reports below.
Choose your runtime: the CLI writes the mcpServers config entry for that target.
nerlo install --target claude-code -- mcp-crypto-bot
Install respects the composite badge: Clean proceeds, Caution prompts for confirmation, and Flagged is refused. Write operations require an API token.
5 of 11 scanners examined this package. The rest do not apply to it — language, ecosystem and packaging decide which analyzers can say anything, and a scanner that cannot examine an artifact reports nothing rather than passing it.
v2.0.11
7 findings · 7.0s
v0.3.74
4 findings · 0.9s
v0.1.0
0 findings · 2.6s
v0.1.0
0 findings · 2.6s
v2.3.8
79 findings · 1.4s
v1.4.0
None of the entry points this scanner reads were found in this artifact. What each scanner covers
0 findings · 0.2s
vv0.3.2
No Go packages were found in this artifact. What each scanner covers
0 findings · 0.1s
v0.1.0
This scanner found nothing in this artifact that it assesses. What each scanner covers
0 findings · 1.6s
v0.71.0
No dependency manifest or lockfile was found in this artifact. What each scanner covers
0 findings · 0.2s
v0.71.0
No container image was published for this artifact. What each scanner covers
0 findings · 0.0s
vv1.6.0
No Go modules were found in this artifact. What each scanner covers
0 findings · 0.1s
1 scan on record. Every scan's full results are retained immutably for 24 months.
| Completed | Composite | Change | Scanners | Status |
|---|---|---|---|---|
| Aug 20, 2026 | Flagged43 | — | agentshield ·n/a: not applicablecisco-skill-scanner: completeagent-audit-kit: completenerlo-behavioral: completenerlo-install-instruction: completecapslock ·n/a: not applicablenerlo-multi-source ·n/a: not applicabletrivy ·n/a: not applicableosv-scanner: completetrivy_image ·n/a: not applicablegovulncheck ·n/a: not applicable | completed |
Findings in files this artifact installs stand as reported; a model re-read the rest and said which ones it believes are false positives. This is a second opinion published beside the evidence, not a correction to it: the per-scanner reports above are unchanged, every dismissed finding is still listed there at its original severity, and the score and the Flagged badge are computed from those raw severities alone. Nothing below moved them.
Out of 90 findings across every scanner that examined this package. None of the 3 findings rated critical by their scanner were dismissed.
Not reviewed is not the same as clean. Those 4 findings stand exactly as their scanners reported them, at full severity, as they would have without this review.
Two keys had to turn. The model had to name a reason from a fixed list of six, and a deterministic check of ours — over which files this artifact actually installs — had to independently agree. Anything it could not corroborate is in “not reviewed” above, at full severity.
1 Test or fixture file — The match is in a test or fixture. Our own check confirmed the file is not part of what gets installed.
Rules: FILE_MAGIC_MISMATCH · Files: /repo/tests/__init__.py · reported by cisco-skill-scanner
The model could have called any of these a false positive and did not.
4 FILE_MAGIC_MISMATCH
Files: /repo/src/__init__.py, /repo/src/solana/__init__.py, /repo/src/wallets/__init__.py and 1 more · reported by cisco-skill-scanner
2 AAK-MCP-SDK-CVE-2026-52869-001
Files: pyproject.toml, requirements.txt · reported by agent-audit-kit
1 AAK-SUPPLY-004
Files: pyproject.toml · reported by agent-audit-kit
1 GHSA-537c-gmf6-5ccf
Files: /repo/requirements.txt · reported by osv-scanner
1 GHSA-c2jp-c369-7pvx
Files: /repo/requirements.txt · reported by osv-scanner
1 GHSA-fj7x-q9j7-g6q6
Files: /repo/requirements.txt · reported by osv-scanner
1 GHSA-h4gh-qq45-vh27
Files: /repo/requirements.txt · reported by osv-scanner
1 GHSA-jm77-qphf-c4w8
Files: /repo/requirements.txt · reported by osv-scanner
1 GHSA-pjjw-qhg8-p2p9
Files: /repo/requirements.txt · reported by osv-scanner
1 GHSA-rcfx-77hg-w2wv
Files: /repo/requirements.txt · reported by osv-scanner
1 GHSA-v8gr-m533-ghj9
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2023-112
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2023-120
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2023-246
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2023-250
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2023-251
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2023-254
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2024-225
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2024-24
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2024-26
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-1097
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-1098
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-1099
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-1100
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-1101
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-1102
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-1103
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-1104
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-1105
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-1106
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-1107
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-1109
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-1283
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-1285
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-1364
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-1365
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-1616
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-1617
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-1618
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-1812
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-1845
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-1872
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-1873
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-2094
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-2095
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-2096
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-2097
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-2098
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-2099
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-2100
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-2101
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-2102
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-2103
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-2104
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-2105
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-2106
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-2107
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-2108
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-2109
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-2110
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-2111
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-2112
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-2113
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-2120
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-2121
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-2141
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-2270
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-2275
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-237
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-2475
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-2476
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-338
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-3414
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-3482
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-3483
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-35
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-3545
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-3546
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-3547
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-3553
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-3554
Files: /repo/requirements.txt · reported by osv-scanner
3 The model called these false positives and our own check did not agree, so the dismissal was refused.
Rules: AAK-SEC-MD-001, SOCIAL_ENG_VAGUE_DESCRIPTION, MANIFEST_MISSING_LICENSE · Files: SECURITY.md, /repo/SKILL.md · reported by agent-audit-kit, cisco-skill-scanner
1 The model did not answer for these findings.
Rules: PYSEC-2026-2474 · Files: /repo/requirements.txt · reported by osv-scanner
Critical vulnerabilities in artifact dependencies.
The artifact contains multiple critical and high severity vulnerabilities within its declared dependencies. These findings, located in `requirements.txt` and `pyproject.toml`, indicate potential for system compromise or data exposure. Addressing these dependency issues is crucial to mitigate risks.
Concern level assessed by the review: Critical. This is the review's scale, not the registry badge.
Showing 25 of 41; the rest are in the per-scanner reports above.
Reviewed by gemini-2.5-flash. The model sees the findings, not your code, and cannot change a score.