ZendIQ
NPM · @ZENDIQ/MCP
Solana swap safety for agents: free token screen, $0.01 swap verdict, $0.02 built swap via x402.
Available components
Last scanned (7 hours ago)
Scores higher than 68% 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 Security91
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, reached via @x402/core > zod. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 0 of 94 dependencies flagged as unhealthy. View diagnostics → Pass
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 23 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 784 tokens (~261/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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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 (100% 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 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.
- 3 Nov 26 0
- Security disclosure: unverified → fail ▼ functional
- 2 Nov 26 +1
- Stability: 0.97 → pass security
- 1 Nov 26 0
- Security disclosure: fail → unverified ▼ functional
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 24 Oct 26 −2
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
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/@zendiq/mcp@1.0.5
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 94 packages
| Packages resolved | 94 |
|---|---|
| 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 →
zendiq_optimize_swap Build an optimized Solana swap ~425
Call once you have decided to trade and need the transaction. Returns an unsigned swap transaction (the Jupiter route, or a direct venue or Jito bundle that beats it after every cost), the plan to verify it against, submit instructions, a simulation, itemised netBenefit, and the same verdict as zendiq_triage_swap. A Refuse is still built: read verdict before signing. You sign and submit it. $0.02 USDC via x402 on Solana mainnet; a failed build is free. taker must hold the input and SOL for fees.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | string | yes | Amount to sell, in the input mint's atomic units, as a decimal string. For 1 SOL (9 decimals) send "1000000000". |
| inputMint | string | yes | Base58 mint address of the token being sold. |
| method | string | – | Optional. "jito" forces a Jito bundle venue (raydium_jito or jupiter_swap_jito) even where risk scoring would not bundle. Only bundle venues are considered, ranked by net value after the tip, and no… |
| outputMint | string | yes | Base58 mint address of the token being bought. |
| slippageBps | integer | – | Optional slippage tolerance in basis points. Omit to use the route default. |
| taker | string | yes | Base58 public key the swap is built for. Must be a mainnet wallet holding the input amount and SOL for fees and rent (a gasless Ultra fill is exempt from the SOL). Can be the paying wallet or a diffe… |
| Name | Type | Req | Description |
|---|---|---|---|
| custody | string | – | – |
| netBenefit | object | yes | Itemised cost arithmetic so the stated net can be checked, not trusted. |
| plan | object | yes | The structured intent the transaction bytes should match. |
| reasons | array | – | – |
| simulation | object | – | Pre-flight simulation. `status` is 'ok', 'failed', or 'unknown' when simulation itself was unavailable. |
| transaction | string | yes | Unsigned base64 VersionedTransaction. Verify it against `plan` before signing. |
| verdict | string|null | – | The same verdict zendiq_triage_swap gives. The transaction is built even on Refuse; do not sign it unless you mean to trade against the verdict. |
No examples provided.
zendiq_screen_token Screen a Solana token ~131
Call first, whenever you are considering a Solana token and have no trade yet: is this mint safe to touch? Returns a 0-100 risk score and level, the 17 checks behind it (authorities, holders, rug flags, LP lock, creator history and more), coverage as signals_resolved, and cache age. Treat an unknown check as unknown, never as safe. Free, no wallet or payment; mainnet data. To judge a specific trade, call zendiq_triage_swap.
| Name | Type | Req | Description |
|---|---|---|---|
| mint | string | yes | Base58 mint address of the token to screen. |
| Name | Type | Req | Description |
|---|---|---|---|
| cache | object | – | – |
| signals_resolved | string | – | Signal coverage, e.g. "13/17". |
| tokenRisk | object | yes | – |
No examples provided.
zendiq_triage_swap Triage a Solana swap ~228
Call before signing a Solana swap, to decide whether and how to trade it. Returns Safe (trade normally), Protect (trade through a Jito bundle, with the tip to use) or Refuse (do not trade), with plain-language reasons, the output token's risk score, the sandwich exposure for this trade size, and the route. Builds no transaction and handles no keys. $0.01 in USDC per call, paid via x402 on Solana mainnet; the market data is mainnet. To get the transaction itself, call zendiq_optimize_swap.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | string | yes | Amount to sell, in the input mint's atomic units, as a decimal string. For 1 SOL (9 decimals) send "1000000000". |
| inputMint | string | yes | Base58 mint address of the token being sold. |
| outputMint | string | yes | Base58 mint address of the token being bought. |
| slippageBps | integer | – | Optional slippage tolerance in basis points. Omit to use the route default. |
| Name | Type | Req | Description |
|---|---|---|---|
| reasons | array | yes | Plain-language justification for the verdict. |
| recommendedExecution | object | yes | – |
| verdict | string | yes | – |
No examples provided.
How do I install the ZendIQ MCP server?
ZendIQ runs locally as an npm package, launched with npx -y @zendiq/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 · @zendiq/mcp
claude mcp add ai-zendiq-mcp -- npx -y @zendiq/mcp
What is the ZendIQ MCP server?
ZendIQ is an MCP server listed in the public MCP registry as ai.zendiq/mcp. Solana swap safety for agents: free token screen, $0.01 swap verdict, $0.02 built swap via x402. This page covers its npm package (@zendiq/mcp).
Is the ZendIQ MCP server safe to use?
ZendIQ scores 81 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 ZendIQ MCP server expose?
ZendIQ exposes 3 tools: zendiq_triage_swap, zendiq_screen_token, zendiq_optimize_swap. Their descriptions and schemas cost roughly 784 tokens of context every time the server is loaded.
Is the ZendIQ MCP server still maintained?
ZendIQ 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 ZendIQ MCP server under?
ZendIQ declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.