# Tavero (npm · tavero)

Finds UI drift in React apps (buttons, cards, colors, spacing) and gives your agent each fix

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

## Components

- npm · `tavero`: 84/100 (this document), [markdown](https://verifymcp.io/servers/baccaraaa-tavero/tavero.md), [page](https://verifymcp.io/servers/baccaraaa-tavero/tavero)

## Channel facts

- Registry: `npm`
- Package: `tavero`
- Version: `0.7.0`
- 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**: 98/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.
  - 32 of 102 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to baccaraaa/tavero).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 10 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 69/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1055 tokens (~117/item across 9 items; 9 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 40/100
  - Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 89/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 67% 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 9 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.

## Install

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

Tavero runs locally as an npm package, launched with npx -y tavero 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 baccaraaa-tavero -- npx -y tavero mcp
```

### Cursor

```json
{
  "mcpServers": {
    "baccaraaa-tavero": {
      "command": "npx",
      "args": [
        "-y",
        "tavero",
        "mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "baccaraaa-tavero": {
      "command": "npx",
      "args": [
        "-y",
        "tavero",
        "mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add baccaraaa-tavero -- npx -y tavero mcp
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add baccaraaa-tavero --command npx --arg -y --arg tavero --arg mcp
```

### Hermes

```yaml
mcp_servers:
  baccaraaa-tavero:
    command: "npx"
    args: ["-y", "tavero", "mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "baccaraaa-tavero": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "tavero",
        "mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add baccaraaa-tavero -t stdio -c npx -a -y tavero mcp
```

### Other

```json
{
  "mcpServers": {
    "baccaraaa-tavero": {
      "command": "npx",
      "args": [
        "-y",
        "tavero",
        "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-04 (score 84, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

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

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-31 (score 82, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-29 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-27 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-25 (score 79, +26)

- [security regression] Tool safety: pass → unverified
- [security improvement] Malware scan: unverified → pass
- [security improvement] Provenance: fail → pass
- [security] Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.
- [security] The attested source repository moved: baccaraaa/tavero
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional improvement] Stability: unverified → 0.03
- [functional] First check of Schema quality: unverified
- [functional] Package version: 0.5.1 → 0.7.0
- [functional] Package version: 0.5.1 → 0.6.0

### 2026-10-24 (score 53)

First indexed and scored.

## MCP tools (9)

### `tavero_context` (~85 tokens)

Design-system brief

Compact Markdown brief of this React app's design system: stack, tokens, the canonical button/icon-button/card components with files and props, dominant radius/spacing/typography, and open problems. Call it BEFORE writing or changing UI, then reuse the components and tokens it names instead of inventing styles.

Input parameters:

- `budget` (integer): approximate token budget, default 1500

### `tavero_findings` (~207 tokens)

List findings

UI consistency problems of the latest scan, worst first: distinct button and card styles, colors outside the tokens, Tailwind defaults, hardcoded literals, off-scale radius/spacing/typography. Each row has a stable id, severity, rule, title and evidence count; evidence is not included. Filter by rule or severity; paginate with limit/page. Open one with tavero_finding. A human may have triaged findings in the Tavero panel: `decision.status` fix means confirmed work (listed first), findings marked accepted are hidden, `decision.note` is a message to you.

Input parameters:

- `decision` (string): human decision; fix = a human confirmed it
- `includeAccepted` (boolean): also list findings a human marked as intended
- `limit` (integer): rows per page (default 20, max 200)
- `page` (integer): page number, from 1
- `rule` (string)
- `severity` (string)

### `tavero_finding` (~184 tokens)

One finding with evidence

One finding with paged evidence rows: current value, `expected` (the project token or canonical component to use instead, or a note that no close token exists and one should be added), component, file:line, route/viewport and a crop image path. Rows valued "literal … in source" are where the value is written (often CSS); the other rows are where it renders (the component JSX). Fix the code using `expected`, then rescan only the affected routes with tavero_scan (routes + rules) and confirm with tavero_diff.

Input parameters:

- `evidenceLimit` (integer): rows per page (default 20, max 200)
- `evidencePage` (integer): page number, from 1
- `id` (string, required): finding id from tavero_findings, e.g. f_2d0ccc6aa1

### `tavero_components` (~108 tokens)

List components

React components seen in the latest scan with instance counts, pages and source file:line. Search by name or file with `query`; sort by instances (default) or name; `unresolved` lists components without a source file.

Input parameters:

- `limit` (integer): rows per page (default 20, max 200)
- `page` (integer): page number, from 1
- `query` (string)
- `sort` (string)
- `unresolved` (boolean)

### `tavero_component` (~49 tokens)

Component details

One component by id or name: source file:line, prop names, instance count, which pages and viewports render it, and crop image paths.

Input parameters:

- `idOrName` (string, required)

### `tavero_show` (~54 tokens)

Crop image paths

Absolute paths of PNG crops showing how a component actually renders, optionally for one viewport. Open them with your image/file reader to see the component.

Input parameters:

- `idOrName` (string, required)
- `viewport` (string)

### `tavero_tokens` (~82 tokens)

Design tokens

Design tokens found in the app (CSS custom properties and Tailwind theme): name, kind, raw and resolved value, source file:line. Use these names instead of literal colors and sizes.

Input parameters:

- `kind` (string)
- `limit` (integer): rows per page (default 200)
- `page` (integer): page number, from 1

### `tavero_diff` (~103 tokens)

Diff two scans

Findings that are new, resolved or unchanged (with changed stats) between the previous and the latest scan, by stable id. A finding is fixed when it is listed under resolved. After a partial rescan, `note` says how many routes were not rescanned and may still carry the finding.

Input parameters:

- `from` (string): older scan folder name; default: the one before `to`
- `to` (string): newer scan folder name; default: latest

### `tavero_scan` (~183 tokens)

Scan the running app

Crawl the app in a real browser at mobile/tablet/desktop widths (plus one dark-theme pass at desktop width when the project styles a dark theme), map every element to its React component and file:line, and recompute findings. A full scan takes minutes; after a code fix pass only the affected `routes` and the finding's `rules` (seconds) — findings on other routes are carried over. Needs the dev server url (it is started with `npm run dev` if nothing answers and kept running for later scans). Then call tavero_diff.

Input parameters:

- `routes` (array): only these routes; omit for all routes
- `rules` (array): recompute only these rules
- `url` (string, required): dev server url, e.g. http://localhost:5173
- `viewports` (array): default: all three

## Diagnostics

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

## Score history

- 2026-11-05: 84
- 2026-11-04: 84
- 2026-11-03: 83
- 2026-11-02: 83
- 2026-11-01: 82
- 2026-10-31: 82
- 2026-10-30: 81
- 2026-10-29: 81
- 2026-10-28: 80
- 2026-10-27: 80
- 2026-10-26: 79
- 2026-10-25: 79
- 2026-10-24: 53

## Common questions

### What is the Tavero MCP server?

Tavero is an MCP server listed in the public MCP registry as io.github.baccaraaa/tavero. Finds UI drift in React apps (buttons, cards, colors, spacing) and gives your agent each fix. This page covers its npm package (tavero).

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

Tavero scores 84 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. Its build provenance is signed and verified. 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 Tavero MCP server expose?

Tavero exposes 9 tools: tavero_context, tavero_findings, tavero_finding, tavero_components, tavero_component, and 4 more. Their descriptions and schemas cost roughly 1,055 tokens of context every time the server is loaded.

### Is the Tavero MCP server still maintained?

Tavero 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 Tavero MCP server under?

Tavero declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

### What did VerifyMCP test on the Tavero MCP server?

VerifyMCP ran 16 checks on Tavero, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- npm package: https://www.npmjs.com/package/tavero
- Socket report: https://socket.dev/npm/package/tavero
- Repository: https://github.com/baccaraaa/tavero
- Website: https://taveroui.com/
- Changelog RSS feed: https://verifymcp.io/servers/baccaraaa-tavero/tavero.xml
- Changelog JSON feed: https://verifymcp.io/servers/baccaraaa-tavero/tavero/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/baccaraaa-tavero/tavero.json
- HTML version of this page: https://verifymcp.io/servers/baccaraaa-tavero/tavero