DevX Token Snapshot
NPM · DEVX-TOKEN-SNAPSHOT · 2 COMPONENTS
ERC-20 price, liquidity, pools, holder hints, risk flags on 7 EVM chains. Paid 0.003 USDC via x402.
Available components
Last scanned (3 hours ago)
Scores higher than 31% 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 112 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 5 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability67
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 846 tokens (~282/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 Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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
- Structured output schemas are declared (67% of tools); any adoption earns full credit.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 4 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
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
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.
- 31 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 30 Oct 26 48
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/devx-token-snapshot@2.1.0
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 112 packages
| Packages resolved | 112 |
|---|---|
| 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 →
token_basics Free ERC-20 token basics ~223
Free: identifies an ERC-20 contract by returning its name, symbol, decimals and total supply, whether it has an owner() and whether it is an EIP-1967 proxy. Use it to confirm which token a contract address really is (for example before trading or listing it) or to get decimals for amount math. For price, liquidity and risk flags use token_snapshot. Read-only. The address is sent to the hosted DevX API, which reads the contract over public RPC at the latest block. No key, no payment. Returns: ok, chain, chain_id, block, token {address, name, symbol, decimals, total_supply as a decimal string}, has_owner, is_eip1967_proxy and full (URL of the paid snapshot). Errors if the address is not an ERC-20 on that chain.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | – | Chain the contract is deployed on. Default: base. |
| token | string | yes | ERC-20 contract address: 0x followed by 40 hex characters (not a symbol or name). |
| Name | Type | Req | Description |
|---|---|---|---|
| block | number | – | – |
| chain | string | yes | – |
| chain_id | number | yes | – |
| free_tier | string | – | – |
| full | string | – | – |
| has_owner | boolean | – | – |
| is_eip1967_proxy | boolean | – | – |
| ok | boolean | – | – |
| token | object | yes | – |
No examples provided.
token_snapshot Token price, liquidity and risk snapshot (paid, 0.003 USDC) ~365
Returns an on-chain market and risk snapshot of an ERC-20: USD price from its deepest DEX pool against wrapped native or stablecoins, FDV, total DEX liquidity, the top pools across Uniswap V2/V3, Aerodrome, Velodrome, PancakeSwap, Sushi, Camelot, QuickSwap, Trader Joe and Pangolin, holder-concentration hints (supply held in pools, burn address, the contract and the owner), and risk flags (proxy, owner, mint, blacklist, fee, pause or trading-switch functions in the bytecode, thin liquidity, price divergence between pools). Use it before buying, accepting or listing an unfamiliar token, or when an agent needs a price without a market-data API key. Data comes from contract reads only, so tokens with no DEX pool on the chosen chain have no price. Cost and side effects: this calls the hosted paid endpoint and costs 0.003 USDC per call via x402 on Base. It pays only if X402_PRIVATE_KEY (or EVM_PRIVATE_KEY) is set in this server's environment. It checks that the quote is USDC on Base, goes to the DevX wallet and is at most 0.01 USDC before signing. Without a key it pays nothing and returns {payment_required: true, url, quote, how_to_pay}. Risk flags are bytecode and liquidity heuristics, not an audit.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | – | Chain the contract is deployed on. Default: base. |
| pools | integer | – | How many top pools to include, 1-10. Default 5. |
| token | string | yes | ERC-20 contract address: 0x followed by 40 hex characters (not a symbol or name). |
No output schema declared.
No examples provided.
token_snapshot_info Price and payment details of the paid call ~99
Returns the URL template, HTTP methods, price (0.003 USDC), protocol (x402 exact, USDC on Base), supported chains, payee address and docs link of the paid token_snapshot endpoint, so an agent with its own x402 client can call it directly. Makes no network request and does not pay. Returns: url, method, price_usdc, protocol, chains, payTo, docs, pay_with_this_package.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| chains | array | yes | – |
| docs | string | yes | – |
| method | string | yes | – |
| payTo | string | yes | – |
| pay_with_this_package | string | yes | – |
| price_usdc | number | yes | – |
| protocol | string | yes | – |
| url | string | yes | – |
No examples provided.
How do I install the DevX Token Snapshot MCP server?
DevX Token Snapshot runs locally as an npm package, launched with npx -y devx-token-snapshot. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · devx-token-snapshot
claude mcp add devx-agent-token-snapshot -- npx -y devx-token-snapshot
What is the DevX Token Snapshot MCP server?
DevX Token Snapshot is an MCP server listed in the public MCP registry as io.github.devx-agent/token-snapshot. ERC-20 price, liquidity, pools, holder hints, risk flags on 7 EVM chains. Paid 0.003 USDC via x402. This page covers its npm package (devx-token-snapshot).
Is the DevX Token Snapshot MCP server safe to use?
DevX Token Snapshot scores 63 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 DevX Token Snapshot MCP server expose?
DevX Token Snapshot exposes 3 tools: token_basics, token_snapshot, token_snapshot_info. Their descriptions and schemas cost roughly 687 tokens of context every time the server is loaded.
Is the DevX Token Snapshot MCP server still maintained?
DevX Token Snapshot 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 DevX Token Snapshot MCP server under?
DevX Token Snapshot declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.