Wensity
NPM · @WENSITY/MCP
Find, plan, and install Wensity UI React components and blocks into your project.
Available components
Last scanned (5 hours ago)
Scores higher than 36% 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 Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects @modelcontextprotocol/sdk 1.29.0, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 31 of 93 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 5 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability70
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 770 tokens (~128/item across 6 items; 6 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 Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage85
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 48% of tool parameters carry a description.Partial
- 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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 +30
- 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 Tool coverage: 48 functional
- First check of Destructive annotations: pass functional
- First check of Schema quality: fail functional
- First check of Schema quality: good functional
- First check of Tool coverage: 100 functional
- 12 Oct 26 28
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 18 Oct 2026 · Analysed npm/@wensity/mcp@0.1.2
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-6qxp-vccf-f47h | CVE-2026-104850 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| 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 →
wensity_auth_status Check Wensity access ~68
Whether this machine has a Wensity API token, its plan, and whether Pro items can be installed. When not connected, relay howToConnect.steps so the user signs in from their own terminal. Never ask for or accept a token in the conversation.
| Name | Type | Req | Description |
|---|---|---|---|
| refresh | boolean | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
wensity_get_item Get a Wensity item ~98
Public metadata for one Wensity component or block: description, usage snippet, props, npm dependencies, install command, detail and live-preview links, and whether this machine can install it. Never returns source. Use usage verbatim and props to explain configuration; link detailUrl for examples.
| Name | Type | Req | Description |
|---|---|---|---|
| includeSimilar | boolean | – | – |
| kind | string | – | Optional disambiguation; resolved automatically if omitted. |
| slug | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
wensity_inspect_project Inspect the local project ~111
Describe the local project so you know whether and how Wensity can install into it: root, framework, language, package manager, aliases, Tailwind CSS file, cn helper, and Wensity files already installed. Local only: no network, never returns file contents. Call once at the start of an install conversation, and again afterwards to confirm state.
| Name | Type | Req | Description |
|---|---|---|---|
| projectPath | string | – | Absolute path to the project root. If omitted, the server resolves it (client root, then working directory). |
Structured output declared, but exposes no named fields.
No examples provided.
wensity_install Install a Wensity plan ~100
Install exactly one plan from wensity_plan_install, by its planToken alone. Only call after showing the user that plan. Re-checks preconditions and access, writes files with rollback on failure, then runs the planned package-manager command. Reports file and dependency outcomes separately. A repeated call changes nothing and returns the recorded result with replayed: true. Never returns source.
| Name | Type | Req | Description |
|---|---|---|---|
| planToken | string | yes | The planToken from wensity_plan_install. |
Structured output declared, but exposes no named fields.
No examples provided.
wensity_plan_install Plan a Wensity installation ~183
Plan installing a Wensity component or block, writing nothing: every file, dependency, and conflict. Call before wensity_install and show the user files, dependencies (toInstall, command, caveat), and conflicts. For a Needs Pro item, say so first and offer a Free one; never recreate it. Never returns source. The planToken binds one install to this plan; it is not proof of approval.
| Name | Type | Req | Description |
|---|---|---|---|
| force | boolean | – | Plan an overwrite of existing conflicting files. |
| includeDiff | boolean | – | Include a diff for modified config files (the Tailwind token block). |
| installDependencies | boolean | – | – |
| kind | string | – | Optional disambiguation; resolved automatically if omitted. |
| projectPath | string | – | Absolute path to the project root. Same precedence as wensity_inspect_project. |
| slug | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
wensity_search Search Wensity UI ~210
Find Wensity components, UI primitives, and blocks by need, name, slug, category, tag, tier, dependency, or similarity. Call first for any find/which/show-me request. Show each result's accessLabel (Free, Pro, Needs Pro) next to its name; if the user picks a Needs Pro item, say so and offer the closest Free result. Never recreate a Needs Pro item.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Exact category name, as listed in facets.categories. |
| cursor | string | – | – |
| dependency | string | – | npm package required by the item. Components only. |
| kind | string | – | – |
| limit | integer | – | – |
| primitivesOnly | boolean | – | – |
| query | string | – | Natural language, name, or slug. Omit to browse. |
| refresh | boolean | – | Bypass the local 60s registry cache. |
| similarTo | string | – | – |
| tags | array | – | – |
| tier | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the Wensity MCP server?
Wensity runs locally as an npm package, launched with npx -y @wensity/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 · @wensity/mcp
claude mcp add com-wensity-mcp -- npx -y @wensity/mcp
What is the Wensity MCP server?
Wensity is an MCP server listed in the public MCP registry as com.wensity/mcp. Find, plan, and install Wensity UI React components and blocks into your project. This page covers its npm package (@wensity/mcp).
Is the Wensity MCP server safe to use?
Wensity scores 58 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 18 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 Wensity MCP server expose?
Wensity exposes 6 tools: wensity_search, wensity_get_item, wensity_auth_status, wensity_inspect_project, wensity_plan_install, wensity_install. Their descriptions and schemas cost roughly 770 tokens of context every time the server is loaded.
Is the Wensity MCP server still maintained?
Wensity is still listed as active in the MCP registry. We last reached this channel on 18 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 Wensity MCP server under?
Wensity declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.