# ZendIQ (npm · @zendiq/mcp)

Solana swap safety for agents: free token screen, $0.01 swap verdict, $0.02 built swap via x402.

- Trust score: 81/100 (high trust)
- Change this week: +2
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- npm · `@zendiq/mcp`: 81/100 (this document), [markdown](https://verifymcp.io/servers/ai-zendiq-mcp/zendiq-mcp.md), [page](https://verifymcp.io/servers/ai-zendiq-mcp/zendiq-mcp)

## Channel facts

- Registry: `npm`
- Package: `@zendiq/mcp`
- Version: `1.0.5`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 91/100
  - No malware found by supply-chain analysis.
  - CVE check failed: a known high-severity CVE affects zod 3.25.76, reached via @x402/core > zod. A fixed version is available.
  - No install/post-install scripts declared.
  - 0 of 94 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 23 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 70/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add ai-zendiq-mcp -- npx -y @zendiq/mcp
```

### Cursor

```json
{
  "mcpServers": {
    "ai-zendiq-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@zendiq/mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ai-zendiq-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@zendiq/mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add ai-zendiq-mcp -- npx -y @zendiq/mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ai-zendiq-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@zendiq/mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ai-zendiq-mcp --command npx --arg -y --arg @zendiq/mcp
```

### Hermes

```yaml
mcp_servers:
  ai-zendiq-mcp:
    command: "npx"
    args: ["-y", "@zendiq/mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "ai-zendiq-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@zendiq/mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add ai-zendiq-mcp -t stdio -c npx -a -y @zendiq/mcp
```

### Other

```json
{
  "mcpServers": {
    "ai-zendiq-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@zendiq/mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-03 (score 81, 0)

- [functional regression] Security disclosure: unverified → fail

### 2026-11-02 (score 81, +1)

- [security] Stability: 0.97 → pass

### 2026-11-01 (score 80, 0)

- [functional regression] Security disclosure: fail → unverified

### 2026-10-30 (score 80, +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.

### 2026-10-28 (score 79, +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.

### 2026-10-26 (score 78, +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.

### 2026-10-24 (score 77, −2)

- [security regression] CVE-2023-54404 affects this package: high
- [security regression] Known CVEs: pass → fail

### 2026-10-23 (score 79, +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.

## MCP tools (3)

### `zendiq_triage_swap` (~228 tokens)

Triage a Solana swap

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.

Input parameters:

- `amount` (string, required): Amount to sell, in the input mint's atomic units, as a decimal string. For 1 SOL (9 decimals) send "1000000000".
- `inputMint` (string, required): Base58 mint address of the token being sold.
- `outputMint` (string, required): Base58 mint address of the token being bought.
- `slippageBps` (integer): Optional slippage tolerance in basis points. Omit to use the route default.

Output parameters:

- `reasons` (array): Plain-language justification for the verdict.
- `recommendedExecution` (object)
- `verdict` (string)

### `zendiq_screen_token` (~131 tokens)

Screen a Solana token

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.

Input parameters:

- `mint` (string, required): Base58 mint address of the token to screen.

Output parameters:

- `cache` (object)
- `signals_resolved` (string): Signal coverage, e.g. "13/17".
- `tokenRisk` (object)

### `zendiq_optimize_swap` (~425 tokens)

Build an optimized Solana swap

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.

Input parameters:

- `amount` (string, required): Amount to sell, in the input mint's atomic units, as a decimal string. For 1 SOL (9 decimals) send "1000000000".
- `inputMint` (string, required): 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, required): Base58 mint address of the token being bought.
- `slippageBps` (integer): Optional slippage tolerance in basis points. Omit to use the route default.
- `taker` (string, required): 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…

Output parameters:

- `custody` (string)
- `netBenefit` (object): Itemised cost arithmetic so the stated net can be checked, not trusted.
- `plan` (object): 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): 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.

## Diagnostics

Captured diagnostic sections: Provenance, Vulnerabilities, Dependencies. The full working is on the page: https://verifymcp.io/servers/ai-zendiq-mcp/zendiq-mcp#diagnostics

## Score history

- 2026-11-05: 81
- 2026-11-04: 81
- 2026-11-03: 81
- 2026-11-02: 81
- 2026-11-01: 80
- 2026-10-31: 80
- 2026-10-30: 80
- 2026-10-29: 79
- 2026-10-28: 79
- 2026-10-27: 78
- 2026-10-26: 78
- 2026-10-25: 77
- 2026-10-24: 77
- 2026-10-23: 79
- 2026-10-22: 78
- 2026-10-21: 78
- 2026-10-20: 78
- 2026-10-19: 77
- 2026-10-18: 77
- 2026-10-17: 76
- 2026-10-16: 76
- 2026-10-15: 75
- 2026-10-14: 75
- 2026-10-13: 39
- 2026-10-12: 39
- 2026-10-11: 39
- 2026-10-04: 70
- 2026-10-03: 55

## Common questions

### 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.

## Links

- npm package: https://www.npmjs.com/package/@zendiq/mcp
- Socket report: https://socket.dev/npm/package/@zendiq/mcp
- Repository: https://github.com/ZendIQ/ZendIQ-Agent-API
- Website: https://zendiq.ai/agents/
- Changelog RSS feed: https://verifymcp.io/servers/ai-zendiq-mcp/zendiq-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/ai-zendiq-mcp/zendiq-mcp.json
- HTML version of this page: https://verifymcp.io/servers/ai-zendiq-mcp/zendiq-mcp