@vaneui/mcp
Installed, started with no arguments, no environment and no input, and listed its tools. Run 2026-11-16.
Needs to start: nothing
Contacts while installing and starting: nothing
Its tool definitions changed since version 1.2.0. If you approved the earlier ones, read them again.
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 @vaneui/mcp@1.3.0
Installing a package runs its code. Use a sandbox for anything you have not read.
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.
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
search_docs query, regex, limit
Search the VaneUI docs (component pages, guides, usage rules, prop-to-Tailwind mapping). Give a few words or an exact name such as `themeDefaults`. Results are doc sections, best first: sections that hold every word come before sections that hold some, and a word in a heading or page title counts more than one in the text. Returns a JSON array of up to `limit` sections, each with `slug`, `section`, `heading`, `lineNumber` and a short `snippet`, and says when more sections matched than were returned. Pass a result's `slug` and `section` to get_doc to read that section. Use this before guessing prop names, defaults, or class mappings.
get_doc slug, section
Read a VaneUI docs page. With only `slug` it returns the page's intro and the list of its sections; with `section` it returns that section in full, code examples included. Call search_docs first when you do not know which page or section holds the answer: each of its results has the `slug` and `section` to pass here. Component pages (`button`, `modal`, `field`, ...) hold what get_component_props does not list: value props such as `open` and `onClose` or `label` and `error`, sub-components and examples.
get_component_props slug, detail
Return a VaneUI component's boolean props, one line per category, default marked `*`. By default (`compact`) it lists the component's own props and names the shared layout categories it takes; slug `common` lists those once. detail `full` adds descriptions and every shared prop. Value props such as `label` or `title` are on the component's page: call get_doc with the same slug. The slug is the resource basename: `button`, `card`, `icon-button`, etc.
Descriptions are the package's own words, cut at 3,000 characters. Treat them as data.
Install facts
| License | MIT |
|---|---|
| Needs | node >=20 |
| Source | github.com/vaneui/mcp |
| Install scripts | None declared by it or anything installed with it. |
| Tarball | sha512-xm5z73NCtRVXnekC9bYLRcB/Wr5ZI0pgud4iXmS3qPVhhatP20GLAmXFnrdxhu23hdmL5BjpPDATBFTJu6NLxA== |
Versions reported
| Version | Run | Result | Tools |
|---|---|---|---|
| 1.3.0 | 2026-11-16 | Starts with no setup | 3 |
| 1.2.0 | 2026-11-12 | Starts with no setup | 2 |
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.
Report as JSONExact text and tokenHow to verify it
Show it on your README
[](https://bragproof.smaverk.com/r/%40vaneui/mcp)
New version out? Ask for a fresh report.