# Venturi (npm · venturi-dev)

Adds conversion components (pricing, checkout, paywalls, upsells) to AI-built Next.js apps.

- Trust score: 61/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- npm · `venturi-dev`: 61/100 (this document), [markdown](https://verifymcp.io/servers/io-useventuri-venturi/venturi-dev.md), [page](https://verifymcp.io/servers/io-useventuri-venturi/venturi-dev)

## Channel facts

- Registry: `npm`
- Package: `venturi-dev`
- Version: `0.2.1`
- 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**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 6/100
  - Repository check failed: no source repository is declared.
  - Provenance check failed: no build-provenance attestation is published.
  - Licence could not be checked: the licence is shipped as a file inside the package, not declared as a standard (SPDX) licence identifier, so we cannot tell whether it is OSI-approved.
  - Actively maintained (last published 4 days ago).
  - Security-disclosure policy not yet verified: we couldn't inspect the source repository.
- **Schema Quality & AI Usability**: 71/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 675 tokens (~84/item across 8 items; 8 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 91/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 73% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 9 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.

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

## Install

### How do I install the Venturi MCP server?

Venturi runs locally as an npm package, launched with npx -y venturi-dev. 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 io-useventuri-venturi -- npx -y venturi-dev
```

### Cursor

```json
{
  "mcpServers": {
    "io-useventuri-venturi": {
      "command": "npx",
      "args": [
        "-y",
        "venturi-dev"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io-useventuri-venturi": {
      "command": "npx",
      "args": [
        "-y",
        "venturi-dev"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add io-useventuri-venturi -- npx -y venturi-dev
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add io-useventuri-venturi --command npx --arg -y --arg venturi-dev
```

### Hermes

```yaml
mcp_servers:
  io-useventuri-venturi:
    command: "npx"
    args: ["-y", "venturi-dev"]
```

### Netclaw

```json
{
  "McpServers": {
    "io-useventuri-venturi": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "venturi-dev"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-useventuri-venturi -t stdio -c npx -a -y venturi-dev
```

### Other

```json
{
  "mcpServers": {
    "io-useventuri-venturi": {
      "command": "npx",
      "args": [
        "-y",
        "venturi-dev"
      ]
    }
  }
}
```

## 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-01 (score 61, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-10-31 (score 46)

First indexed and scored.

## MCP tools (8)

### `list_components` (~75 tokens)

List the Venturi conversion components in the user’s plan, grouped by what they do (urgency, social proof, pricing, checkout, recovery, lead capture, in-app monetization, retention, referrals…), with each one’s variants.

Input parameters:

- `benefit` (string): Only this group, e.g. "Pricing & plan choice".

### `get_component` (~75 tokens)

Details for one component: variants, files, npm packages, its props interface and doc comment, so you can wire it correctly. Call before using a component.

Input parameters:

- `name` (string, required): Component name from list_components, e.g. "pricing-table".
- `projectDir` (string): Project root, if not the current directory.

### `recommend_components` (~88 tokens)

Suggest which Venturi components to use for a page or goal, in the order they should appear on the page, with one line on why. Rule-based from the Venturi catalog.

Input parameters:

- `goal` (string): What the user wants, e.g. "pricing page for my SaaS" or "reduce churn".
- `page` (string): Pick a page type directly instead of a goal.

### `get_design_rules` (~49 tokens)

The design rules to follow when building or restyling a page with Venturi blocks: what reads as AI-generated and what to do instead. Call it before laying out a landing or pricing page.

### `add_components` (~137 tokens)

Copy Venturi components (and the helpers, UI parts and styles they need) into the user’s project as editable source files. Returns where they went, the npm install command to run, and how to import them. Never overwrites the user’s edits unless overwrite is true.

Input parameters:

- `names` (array, required): Component names, e.g. ["hero", "pricing-table"].
- `overwrite` (boolean): Replace files the user edited. Default false.
- `path` (string): Folder for components (default components/venturi, remembered in venturi.json).
- `projectDir` (string): Project root, if not the current directory.

### `list_themes` (~30 tokens)

List the themes the user generated in their Venturi portal (colors, fonts and copy for their niche).

### `apply_theme` (~65 tokens)

Apply one of the user’s portal themes: writes CSS overrides (colors, fonts) next to venturi.css and the suggested copy as JSON.

Input parameters:

- `id` (string, required): Theme id from list_themes.
- `path` (string)
- `projectDir` (string)

### `import_reviews` (~94 tokens)

Turn a CSV of the user’s REAL reviews into content/reviews.json for the testimonial components. Columns: quote, name (required); role, rating (1–5), tags (;-separated), avatarUrl, date, url, platform. Never write reviews yourself.

Input parameters:

- `file` (string, required): Path to the CSV, relative to the project.
- `out` (string)
- `projectDir` (string)

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/io-useventuri-venturi/venturi-dev#diagnostics

## Score history

- 2026-11-05: 61
- 2026-11-04: 61
- 2026-11-03: 61
- 2026-11-02: 61
- 2026-11-01: 61
- 2026-10-31: 46

## Common questions

### What is the Venturi MCP server?

Venturi is an MCP server listed in the public MCP registry as io.useventuri/venturi. Adds conversion components (pricing, checkout, paywalls, upsells) to AI-built Next.js apps. This page covers its npm package (venturi-dev).

### Is the Venturi MCP server safe to use?

Venturi scores 61 out of 100 on VerifyMCP. We found no known CVEs affecting 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 Venturi MCP server expose?

Venturi exposes 8 tools: list_components, get_component, recommend_components, get_design_rules, add_components, and 3 more. Their descriptions and schemas cost roughly 613 tokens of context every time the server is loaded.

### Is the Venturi MCP server still maintained?

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

## Links

- npm package: https://www.npmjs.com/package/venturi-dev
- Socket report: https://socket.dev/npm/package/venturi-dev
- Website: https://www.useventuri.io/
- Changelog RSS feed: https://verifymcp.io/servers/io-useventuri-venturi/venturi-dev.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-useventuri-venturi/venturi-dev.json
- HTML version of this page: https://verifymcp.io/servers/io-useventuri-venturi/venturi-dev