Venturi
NPM · VENTURI-DEV
Adds conversion components (pricing, checkout, paywalls, upsells) to AI-built Next.js apps.
Available components
Last scanned (23 hours ago)
Scores higher than 31% of npm servers
Category Developer Tools
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 Security100
- 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
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency6
- 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
- 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.Unverified
- Actively maintained (last published 3 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability71
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 675 tokens (~84/item across 8 items; 8 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 Coverage91
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 73% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 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.
- 1 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 31 Oct 26 46
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 4 Nov 2026 · Analysed npm/venturi-dev@0.2.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 0 packages
| Packages resolved | 0 |
|---|---|
| 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 →
add_components ~137
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.
| Name | Type | Req | Description |
|---|---|---|---|
| names | array | yes | 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. |
No output schema declared.
No examples provided.
apply_theme ~65
Apply one of the user’s portal themes: writes CSS overrides (colors, fonts) next to venturi.css and the suggested copy as JSON.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Theme id from list_themes. |
| path | string | – | – |
| projectDir | string | – | – |
No output schema declared.
No examples provided.
get_component ~75
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.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Component name from list_components, e.g. "pricing-table". |
| projectDir | string | – | Project root, if not the current directory. |
No output schema declared.
No examples provided.
get_design_rules ~49
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
import_reviews ~94
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.
| Name | Type | Req | Description |
|---|---|---|---|
| file | string | yes | Path to the CSV, relative to the project. |
| out | string | – | – |
| projectDir | string | – | – |
No output schema declared.
No examples provided.
list_components ~75
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.
| Name | Type | Req | Description |
|---|---|---|---|
| benefit | string | – | Only this group, e.g. "Pricing & plan choice". |
No output schema declared.
No examples provided.
list_themes ~30
List the themes the user generated in their Venturi portal (colors, fonts and copy for their niche).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
recommend_components ~88
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
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.
npm · venturi-dev
claude mcp add io-useventuri-venturi -- npx -y venturi-dev
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 4 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 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.