Tavero
NPM · TAVERO
Finds UI drift in React apps (buttons, cards, colors, spacing) and gives your agent each fix
Available components
Last scanned (13 hours ago)
Scores higher than 81% of npm servers
Category Testing and QA
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 Security98
- 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
- 32 of 102 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to baccaraaa/tavero). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 10 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability69
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management40
- Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage89
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 67% 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 9 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
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 4 Nov 26 +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.
- 2 Nov 26 +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.
- 31 Oct 26 +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.
- 29 Oct 26 +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.
- 27 Oct 26 +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.
- 25 Oct 26 +26
- Tool safety: pass → unverified ▼ security
- Malware scan: unverified → pass ▲ security
- 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 security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 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 functional
- 24 Oct 26 53
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 5 Nov 2026 · Analysed npm/tavero@0.7.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | baccaraaa/tavero |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/baccaraaa/tavero/.github/workflows/release.yml@refs/heads/master |
| Rekor log index | 3463651622 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:cb7531ea545d91140f3186c6f898792d12ab4cceb7e002c08ade4ee162dba52bc56d7f840d71b868054d78b2738f83ba0a6d01f0c518382409000a7bb |
Background: How many MCP packages publish verified provenance →
Dependencies 102 packages
| Packages resolved | 102 |
|---|---|
| Stale | 32 |
| 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 →
tavero_component Component details ~49
One component by id or name: source file:line, prop names, instance count, which pages and viewports render it, and crop image paths.
| Name | Type | Req | Description |
|---|---|---|---|
| idOrName | string | yes | – |
No output schema declared.
No examples provided.
tavero_components List components ~108
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | rows per page (default 20, max 200) |
| page | integer | – | page number, from 1 |
| query | string | – | – |
| sort | string | – | – |
| unresolved | boolean | – | – |
No output schema declared.
No examples provided.
tavero_context Design-system brief ~85
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.
| Name | Type | Req | Description |
|---|---|---|---|
| budget | integer | – | approximate token budget, default 1500 |
No output schema declared.
No examples provided.
tavero_diff Diff two scans ~103
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.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | – | older scan folder name; default: the one before `to` |
| to | string | – | newer scan folder name; default: latest |
No output schema declared.
No examples provided.
tavero_finding One finding with evidence ~184
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.
| Name | Type | Req | Description |
|---|---|---|---|
| evidenceLimit | integer | – | rows per page (default 20, max 200) |
| evidencePage | integer | – | page number, from 1 |
| id | string | yes | finding id from tavero_findings, e.g. f_2d0ccc6aa1 |
No output schema declared.
No examples provided.
tavero_findings List findings ~207
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | – | – |
No output schema declared.
No examples provided.
tavero_scan Scan the running app ~183
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.
| Name | Type | Req | Description |
|---|---|---|---|
| routes | array | – | only these routes; omit for all routes |
| rules | array | – | recompute only these rules |
| url | string | yes | dev server url, e.g. http://localhost:5173 |
| viewports | array | – | default: all three |
No output schema declared.
No examples provided.
tavero_show Crop image paths ~54
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.
| Name | Type | Req | Description |
|---|---|---|---|
| idOrName | string | yes | – |
| viewport | string | – | – |
No output schema declared.
No examples provided.
tavero_tokens Design tokens ~82
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.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | – | – |
| limit | integer | – | rows per page (default 200) |
| page | integer | – | page number, from 1 |
No output schema declared.
No examples provided.
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.
npm · tavero
claude mcp add baccaraaa-tavero -- npx -y tavero mcp
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.