# Wensity (npm · @wensity/mcp)

Find, plan, and install Wensity UI React components and blocks into your project.

- Trust score: 58/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-18

## Components

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

## Channel facts

- Registry: `npm`
- Package: `@wensity/mcp`
- Version: `0.1.2`
- 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-10-18.

- **Supply Chain Security**: 81/100
  - No malware found by supply-chain analysis.
  - CVE check failed: a known high-severity CVE affects @modelcontextprotocol/sdk 1.29.0, a direct dependency. A fixed version is available.
  - No install/post-install scripts declared.
  - 31 of 93 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 19/100
  - Repository check failed: no source repository is declared.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 5 days ago).
  - Security-disclosure policy not yet verified: we couldn't inspect the source repository.
- **Schema Quality & AI Usability**: 70/100
  - AI-judged instruction clarity (good).
  - 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.
  - 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**: 85/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 48% 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 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 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.

### Claude

```bash
claude mcp add com-wensity-mcp -- npx -y @wensity/mcp
```

### Cursor

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

### VS Code

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

### Codex

```bash
codex mcp add com-wensity-mcp -- npx -y @wensity/mcp
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add com-wensity-mcp --command npx --arg -y --arg @wensity/mcp
```

### Hermes

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

### Netclaw

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

### Vellum

```bash
assistant mcp add com-wensity-mcp -t stdio -c npx -a -y @wensity/mcp
```

### Other

```json
{
  "mcpServers": {
    "com-wensity-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@wensity/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-10-14 (score 58, +30)

- [security improvement] 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).
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] 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

### 2026-10-12 (score 28)

First indexed and scored.

## MCP tools (6)

### `wensity_search` (~210 tokens)

Search Wensity UI

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.

Input parameters:

- `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)

### `wensity_get_item` (~98 tokens)

Get a Wensity item

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.

Input parameters:

- `includeSimilar` (boolean)
- `kind` (string): Optional disambiguation; resolved automatically if omitted.
- `slug` (string, required)

### `wensity_auth_status` (~68 tokens)

Check Wensity access

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.

Input parameters:

- `refresh` (boolean)

### `wensity_inspect_project` (~111 tokens)

Inspect the local project

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.

Input parameters:

- `projectPath` (string): Absolute path to the project root. If omitted, the server resolves it (client root, then working directory).

### `wensity_plan_install` (~183 tokens)

Plan a Wensity installation

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.

Input parameters:

- `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, required)

### `wensity_install` (~100 tokens)

Install a Wensity plan

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.

Input parameters:

- `planToken` (string, required): The planToken from wensity_plan_install.

## Diagnostics

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

## Score history

- 2026-10-18: 58
- 2026-10-17: 58
- 2026-10-16: 58
- 2026-10-15: 58
- 2026-10-14: 58
- 2026-10-13: 28
- 2026-10-12: 28

## Common questions

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

## Links

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