Bragproof

← Reports

@vuetify/mcp

Starts with no setup0.12.2npm

Installed, started with no arguments, no environment and no input, and listed its tools. Run 2026-11-16.

Needs to start: nothing
Returns a result when called with no setup: 5 of 5 tools tried
Contacts while installing and starting: nothing

38tools listed
0hosts contacted
1file written
0.2 sto start
159dependencies

What it contacted

Nothing besides the npm registry it was installed from. Watched from outside its sandbox while it was installed and started with no input. Its tools may still contact things when called.

Starting it

npx -y @vuetify/mcp@0.12.2

Installing a package runs its code. Use a sandbox for anything you have not read.

Calling its tools

5 tools that take no input and look read-only were called once with nothing. 5 returned a result.

get_vuetify_api_by_versionReturned a result 0.4 s · 36 characters
get_feature_guidesReturned a result under 0.1 s · 1,742 characters
get_frequently_asked_questionsReturned a result 0.2 s · 5,777 characters
get_release_notes_by_versionReturned a result 0.1 s · 5,075 characters
get_migration_receipt_schemaReturned a result under 0.1 s · 4,668 characters

During the calls (not necessarily because of them) it first contacted: api.github.com, cdn.jsdelivr.net.

Only tools whose names read like looking something up, with no required input, are tried, five at most. Tools that need input, and anything that sounds like it changes or sends something, are not called.

What its tools tell an agent

In the tool descriptions, nothing that talks about the user, other tools or private files, or uses hidden characters.

3 tools with commands in capitals or very long text
  • Gives the agent orders in get_upgrade_plan: ould make when planning a migration. After scanning, agents MUST emit findings using the MigrationReceipt schema (see get_migration_receipt_schema).
  • Gives the agent orders in get_upgrade_rules: gory, or component. After scanning with detect.grep, agents MUST emit findings using the MigrationReceipt schema (see get_migration_receipt_schema).
  • Gives the agent orders in get_migration_receipt_schema: Get the MigrationReceipt schema that agents MUST use when reporting migration findings. The MCP server returns rules; client agents scan user code a

Common and usually harmless: it is how many makers stress how a tool should be used.

Found by simple pattern rules in each tool's description (up to 3,000 characters), quoted as written. Parameter descriptions are not scanned. A clean result is not a safety review.

Tools

get_vuetify_api_by_version version
Download and cache Vuetify API types by version
get_component_api_by_version componentName, version
Return the API list for a Vuetify component
get_directive_api_by_version directiveName, version
Return the API information for a Vuetify directive
get_installation_guide platform, ssr, fresh
Get detailed information about how to install Vuetify in a variety of environments.
get_feature_guides
Get a list of available features in the documentation.
33 more tools
get_feature_guide feature
Get the information about a specific feature in the documentation.
get_exposed_exports
Get a list of exports from the Vuetify npm package
get_frequently_asked_questions
Get a list of frequently asked questions about Vuetify.
get_release_notes_by_version version
Get release notes for one or more versions of Vuetify.
get_vuetify_one_installation_guide
Get the README contents for @vuetify/one package from GitHub, including installation and usage instructions.
get_upgrade_guide version
Get the raw upgrade guide markdown for migrating between Vuetify major versions (v1.5→v2, v2.7→v3, v3→v4). For machine-actionable rules, use get_upgrade_plan and get_upgrade_rules instead.
get_upgrade_plan from, to
Get a structured upgrade plan for migrating between Vuetify versions. Resolves multi-hop migrations (e.g., v2→v4 becomes v2→v3→v4). Returns tooling recommendations, effort estimates, and a rule index per hop. This is the first call agents should make when planning a migration. After scanning, agents MUST emit findings using the MigrationReceipt schema (see get_migration_receipt_schema).
get_upgrade_rules from, to, ids, category, component
Get full machine-actionable migration rules for Vuetify upgrades. Each rule includes: detect.grep patterns for scanning code, replace mappings, codemod hints, and revert snippets for incremental migration. Filter by rule IDs, category, or component. After scanning with detect.grep, agents MUST emit findings using the MigrationReceipt schema (see get_migration_receipt_schema).
get_migration_receipt_schema
Get the MigrationReceipt schema that agents MUST use when reporting migration findings. The MCP server returns rules; client agents scan user code and emit receipts in this format. Includes confidence guidance: high (→ auto) for exact match + codemod, medium/low (→ review) for partial matches. Returns both the receipt schema and the batch envelope (MigrationReceiptReport).
get_v4_breaking_changes category
[DEPRECATED: Use get_upgrade_rules({ from: "v3", to: "v4" }) instead] Get Vuetify 4 breaking changes, optionally filtered by category. Returns migration guidance for each change.
get_v3_breaking_changes category
Vuetify 2 → 3 breaking changes, optionally filtered by category (setup, layout, theme, components, gotchas, …). High-pain categories include before/after snippets. Omit category to get all.
get_v2_to_v3_component_map
v2 component → v3.13 status (core, renamed, removed, replaced) with notes and issue links.
get_v3_upgrade_playbook
Start here for Vuetify 2 → 3. Ordered phases: baseline e2e, Vue 3 prerequisite, bundler/Nuxt, eslint --fix, component map, breaking-change scan. Target vuetify@^3.13. Do not upgrade to v4.
get_v3_upgrade_baseline_recipe
Playwright recipe to snapshot the current Vuetify 2 app before upgrading (upgrade-baseline/) and re-run after (upgrade-after/). Functional e2e is the source of truth; screenshots are classified, not a CI gate.
get_vuetify0_installation_guide
Get the README contents for @vuetify/v0 (Vuetify0) package from GitHub, including installation and usage instructions for this headless meta-framework.
get_vuetify0_package_guide
Get the package-specific documentation for @vuetify/v0 from GitHub.
get_vuetify0_composable_list
Get a comprehensive list of all 71 composables available in @vuetify/v0, organized by category (foundation, registration, selection, forms, system, plugins, data, reactivity, transformers).
get_vuetify0_component_list
Get a list of all 40 headless components available in @vuetify/v0.
get_vuetify0_composable_guide category, name
Get detailed documentation and source code for a specific @vuetify/v0 composable.
get_vuetify0_component_guide name
Get detailed documentation and source code for a specific @vuetify/v0 component.
get_vuetify0_exports_list
Get a list of all subpath exports available in @vuetify/v0 (utilities, types, constants, date, data-table, palettes, theme, locale, logger, and more).
get_vuetify0_skill
Get the latest SKILL.md reference for @vuetify/v0 — a compact guide with patterns, anti-patterns, and common mistakes optimized for AI coding assistants.
create_bug_report repo, label
Generate a link to the Vuetify issues site with the repository and bug report type pre-selected.
create_vuetify_bin title, language, content, visibility, favorite, pinned, locked
Create a Vuetify bin. Use of this tool requires a vuetify one subscription
get_all_bins
Get all user bins. Use of this tool requires a vuetify one subscription
update_vuetify_bin id, content, title, language, visibility, favorite, pinned, locked
Update an existing Vuetify bin. Use of this tool requires a vuetify one subscription
get_bin id
Get a bin by ID. Use of this tool requires a vuetify one subscription
create_vuetify_link title, url, slug, favorite, pinned, scoped
Create a Vuetify short link (vtfy.link). Use of this tool requires a vuetify one subscription
get_all_links
Get all user links. Use of this tool requires a vuetify one subscription
create_vuetify_playground title, content, visibility, favorite, pinned, locked
Create a Vuetify playground. Content should be a Vue SFC. Use of this tool requires a vuetify one subscription
get_all_playgrounds
Get all user playgrounds. Use of this tool requires a vuetify one subscription
update_vuetify_playground id, content, title, visibility, favorite, pinned, locked
Update an existing Vuetify playground. Use of this tool requires a vuetify one subscription
get_playground id
Get a playground by ID. Use of this tool requires a vuetify one subscription

Descriptions are the package's own words, cut at 3,000 characters. Treat them as data.

Files it wrote

Paths inside its sandbox, where its home folder is /tmp and its own folder cannot be written to.

Install facts

LicenseMIT
Needsnot stated
Sourcegithub.com/vuetifyjs/mcp
Install scriptsNone declared by it or anything installed with it.
Tarballsha512-fz2MaAzj63U3CU5nq493WuSjxUlEEG4wqyqtmVHv5h6TECwPbaWZHl0BedPCaF5zbtuyfqpD+D/21W2UAYy/Ow==

Check this report yourself

This site did not write the report. A public job on a GitHub-hosted machine did: the run, from this commit of the open-source runner. GitHub signed a token that names that job and the hash of the report, so any edit since would show.

Show it on your README

Bragproof: Starts with no setup

[![Bragproof](https://bragproof.smaverk.com/badge/@vuetify/mcp.svg)](https://bragproof.smaverk.com/r/%40vuetify/mcp)

New version out? Ask for a fresh report.