Veriql Risk
NPM · VERIQL-MCP
Rug, honeypot and wallet-approval risk checks on Solana and EVM, with every penalty driver shown.
Available components
Last scanned (8 hours ago)
Scores higher than 37% 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 Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: no source repository is declared. See how to fix → View diagnostics → Fail
- 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 6 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability76
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 244 tokens (~81/item across 3 items; 3 tools + 0 resources), lean.Pass
- 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
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
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.
- 14 Oct 26 +32
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- First check of Schema quality: fail functional
- First check of Destructive annotations: pass functional
- First check of Schema quality: pass functional
- First check of Schema quality: good functional
- First check of Tool coverage: 100 functional
- 12 Oct 26 33
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 17 Oct 2026 · Analysed npm/veriql-mcp@1.0.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 →
Dependencies 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 31 |
| 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 →
veriql_launch Veriql launch-safety score ~81
A transparent 0-100 launch-safety score for a token/mint with itemised penalty drivers and full metrics. EVM chains + Tron + Solana.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Token contract / mint address |
| chainId | string | – | Chain id or key (e.g. 1, base, solana); defaults to Ethereum |
No output schema declared.
No examples provided.
veriql_scan Veriql wallet scan ~81
Scan a public wallet address for risky token approvals across 5 EVM chains (Ethereum, BNB Chain, Polygon, Arbitrum, Base). Returns a 0-100 Security Score with itemised drivers, every risky approval, and a best-effort USD value-at-risk.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Public EVM address, 0x… |
No output schema declared.
No examples provided.
veriql_token Veriql token check ~82
Check a token contract for honeypot, punishing taxes, mintable supply, hidden owner and proxy risks, each surfaced as a plain-English flag. EVM chains + Tron.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Token contract address |
| chainId | string | – | Chain id or key (e.g. 1, base, tron); defaults to Ethereum |
No output schema declared.
No examples provided.
How do I install the Veriql Risk MCP server?
Veriql Risk runs locally as an npm package, launched with npx -y veriql-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 · veriql-mcp
claude mcp add app-veriql-veriql-mcp -- npx -y veriql-mcp
What is the Veriql Risk MCP server?
Veriql Risk is an MCP server listed in the public MCP registry as app.veriql/veriql-mcp. Rug, honeypot and wallet-approval risk checks on Solana and EVM, with every penalty driver shown. This page covers its npm package (veriql-mcp).
Is the Veriql Risk MCP server safe to use?
Veriql Risk scores 65 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 17 October 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 Veriql Risk MCP server expose?
Veriql Risk exposes 3 tools: veriql_scan, veriql_token, veriql_launch. Their descriptions and schemas cost roughly 244 tokens of context every time the server is loaded.
Is the Veriql Risk MCP server still maintained?
Veriql Risk is still listed as active in the MCP registry. We last reached this channel on 17 October 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 Veriql Risk MCP server under?
Veriql Risk declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.