Skip to content
JevDirectory.orgTraffic count unavailable. View site traffic

Jev directory

CommunityJev Tools & CLIs

Jevscan

Typed onchain verdicts for EVM tokens: paste a contract address and get ape, watch or avoid with calibrated probabilities plus rug_risk, momentum, liquidity_health and fdv_stress scores. Ships as a library, a pipeline-friendly CLI and an MCP server.
See highlightsOpen github.com
Stars
3
Language
JavaScript
License
MIT
Reading time
2 min
Published by
Community
Author
jevbook
Last verified
Oct 2026

jevbook/jevscan

User repository on GitHub

View on GitHub

Typed onchain verdicts for EVM tokens: ape / watch /avoid with calibrated probabilities. CLI + library +MCP server. Robinhood Chain first.

Forks
0
Last pushed
Updated Sep 2026

Repo stats from the GitHub API, cached Oct 2026.

Tagscommunitycatalog-importlogicrwevmtokens
Works forJev for ScoringJev for ClassificationJev for Decision gating
Used inJev for Finance & Fintech
Languages
JavaScript
Platforms
CLIMCP
Capabilities
Open sourceRuns locally

Highlights

  • Three interfaces over one System One decision loop: a library, a CLI built for pipelines, and an MCP server with scan_token, compare_tokens and engine_info.
  • The default engine is deterministic and local with no API key; set JEV_API_KEY and the same questions go to the real jev endpoint with zero code changes.
  • Grep-style exit codes make gate scripts one-liners: 0 for ape or a passed --assert, 1 watch, 2 avoid, 3 no indexed liquidity, 4 bad input, 5 failed assert.
  • Robinhood Chain (4663) is first-class; Base and everything DexScreener indexes work as fallback, and --stdin --json emits one JSON line per address.
  • On any remote failure the local engine answers instead and decision.model says which answered; the output contract never changes between local and remote.

Quickstart

bash
git clone https://github.com/jevbook/jevscan
cd jevscan && npm install
npm link

Watch out

Grounded on the truncated README and GitHub metadata reviewed 2026-10-15; the output-contract JSON example is cut off mid-document. The local engine is the project's own heuristic, not Jev - the real endpoint kicks in only with a key - and the README publishes no accuracy figures for either engine.

Questions about this entry

Short answers drawn from the linked project or page.

From the Jev guides

Original write-ups on what this entry is for.

From the Jev AI model community

Posts from builders shipping with Jev right now.

Follow @typesafeai