@ehrocks/fe-mcp-server
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
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 @ehrocks/fe-mcp-server@1.0.10
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_hero_design_component_examples query, limit, threshold
Retrieve Hero Design System examples, patterns, and references using natural language. Describe the UI behavior, component, or pattern you need. Covers component selection guidance, JSX code examples, design patterns, and use cases across @hero-design/react. Not a prop API reference — use the component library docs for precise prop signatures. Common queries: button loading state, form validation error, dropdown with search, empty state, date picker range, modal confirmation dialog, toast notification. Returns for each match: - Component name and similarity score - Component and example descriptions - Code example (JSX) - Technical details, design patterns, and props context when available
Descriptions are the package's own words, cut at 3,000 characters. Treat them as data.
Install facts
| License | MIT |
|---|---|
| Needs | not stated |
| Source | github.com/thinkei/fe-mcp-service |
| Install scripts | None declared by it or anything installed with it. |
| Tarball | sha512-AwRhcBqO4zatN03gZ4Zyrsj1ZjYTh2Nyz0Fv9rCDbvvutBCYG2yEiKyQL6GI4/7PjgAuqgmJe8te8pa4bpaIwQ== |
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/%40ehrocks/fe-mcp-server)
New version out? Ask for a fresh report.