Bragproof

← Reports

@heroui/native-mcp

Starts with no setup1.1.4npm

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: 2 of 2 tools tried
Contacts while installing and starting: native-mcp-api.heroui.com

4tools listed
1host contacted
0files written
0.9 sto start
125dependencies

What it contacted

Hosts it looked up or connected to while installing and starting with no input, watched from outside its sandbox. The npm registry is left out. Says nothing about what its tools contact when called.

Starting it

npx -y @heroui/native-mcp@1.1.4

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

Calling its tools

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

list_componentsReturned a result 0.2 s · 621 characters
get_theme_variablesReturned a result 0.6 s · 3,315 characters

During the calls it contacted nothing it had not already contacted.

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 list_components: are React Native components for mobile development. Always call this first before using any component to verify it exists. Example workflow: list_components → get_component_d
  • Gives the agent orders in get_theme_variables: me documentation and guides, use the get_docs tool instead. IMPORTANT: HeroUI Native uses Uniwind (Tailwind CSS for React Native) - ensure compatibility.
  • Gives the agent orders in get_docs: tarted, theming, colors, styling, animation, release notes. IMPORTANT: For component documentation, use get_component_docs instead. Example paths: /docs/native/getting-s

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

list_components
List all available components in HeroUI Native.
Returns the component names exactly as they should be used in imports and other tool calls.
HeroUI Native components are React Native components for mobile development.
Always call this first before using any component to verify it exists.
Example workflow: list_components → get_component_docs.
get_component_docs components
Get complete HeroUI Native component documentation (including examples, props, usage) directly from heroui.com.
Accepts an array of component names and returns the full MDX documentation for each component.
Returns raw markdown content from the component's .mdx file, which includes:
- Import statements
- Usage examples
- Variants and sizes
- Props documentation
- Styling information
- API Reference
- And more

This tool replaces get_component_info, get_component_props, and get_component_examples.
Use this when you need complete component documentation in one call.
Workflow: list_components → get_component_docs.
Note: Examples are included in the component docs, no separate examples tool needed.
get_theme_variables
Get HeroUI Native default theme variables and design tokens (actual variable values).
Returns organized CSS custom properties that control the entire design system.
Variables follow a three-layer system: primitives → semantic → calculated.
Includes both light and dark mode variables for all categories:
- Colors: Color tokens (accent, success, danger, background, foreground)
- Typography: Font sizes, weights, line heights
- Spacing: Margin, padding, gap values
- Borders: Border radius, widths, colors
- Shadows: Box shadows and elevations
- Animations: Durations, timing functions
Variables use modern HSL color format for better color manipulation.
Apply these in your CSS with :root or theme-specific selectors.
Example variables: --color-accent, --radius-md, --font-size-body, --spacing-4.
For theme documentation and guides, use the get_docs tool instead.
IMPORTANT: HeroUI Native uses Uniwind (Tailwind CSS for React Native) - ensure compatibility.
get_docs path
Get HeroUI Native documentation content for guides, principles, and release notes (NOT component docs).
Fetches official documentation from heroui.com.
Returns the complete MDX content of documentation pages.
Use for understanding concepts, design principles, implementation guides, and version history.
Documentation covers: getting started, theming, colors, styling, animation, release notes.
IMPORTANT: For component documentation, use get_component_docs instead.
Example paths: /docs/native/getting-started/theming, /docs/native/releases/v1-0-0.
All Native documentation paths start with /docs/native/ prefix.
Returns MDX content which may include code examples and explanations.
This is documentation for HeroUI Native.

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

Install facts

LicenseMIT
Needsnode >=22.22.0
Sourcegithub.com/heroui-inc/heroui-mcp
Install scriptsNone declared by it or anything installed with it.
Tarballsha512-ChdI6wmDXeBNJsKiKnEWvkZkpTD/5R385sCDuP2QHwN0G2z98MFO++K6V/482mKDROBGiTzRz/LMAfyYMqJGUw==

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/@heroui/native-mcp.svg)](https://bragproof.smaverk.com/r/%40heroui/native-mcp)

New version out? Ask for a fresh report.