Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"random-design": {
"args": [
"-y",
"random-design-mcp"
],
"command": "npx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
TypeScript MCP server that returns randomized English Markdown frontend design directions. It uses curated catalogs and optional soft compatibility scoring. It
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
npx -y 'npm' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories — click any category to see the underlying evidence.
Packing does not respect root-level ignore files in workspaces
### Impact `npm pack` ignores root-level `.gitignore` & `.npmignore` file exclusion directives when run in a workspace or with a workspace flag (ie. `--workspaces`, `--workspace=<name>`). Anyone who has run `npm pack` or `npm publish` with workspaces, as of [v7.9.0](https://github.com/npm/cli/releases/tag/v7.9.0) & [v7.13.0](https://github.com/npm/cli/releases/tag/v7.13.0) respectively, may be affected and have published files into the npm registry they did not intend to include. ### Patch - Up
Incorrect Permission Assignment for Critical Resource in NPM
An issue was discovered in an npm 5.7.0 2018-02-21 pre-release (marked as "next: 5.7.0" and therefore automatically installed by an "npm upgrade -g npm" command, and also announced in the vendor's blog without mention of pre-release status). It might allow local users to bypass intended filesystem access restrictions because ownerships of /etc and /usr directories are being changed unexpectedly, related to a "correctMkdir" issue.
Local Privilege Escalation in npm
Affected versions of `npm` use predictable temporary file names during archive unpacking. If an attacker can create a symbolic link at the location of one of these temporary file names, the attacker can arbitrarily write to any file that the user which owns the `npm` process has permission to write to, potentially resulting in local privilege escalation. ## Recommendation Update to version 1.3.3 or later.
npm CLI exposing sensitive information through logs
Versions of the npm CLI prior to 6.14.6 are vulnerable to an information exposure vulnerability through log files. The CLI supports URLs like `<protocol>://[<user>[:<password>]@]<hostname>[:<port>][:][/]<path>`. The password value is not redacted and is printed to stdout and also to any generated log files.
npm Vulnerable to Global node_modules Binary Overwrite
Versions of the npm CLI prior to 6.13.4 are vulnerable to a Global node_modules Binary Overwrite. It fails to prevent existing globally-installed binaries to be overwritten by other package installations. For example, if a package was installed globally and created a `serve` binary, any subsequent installs of packages that also create a `serve` binary would overwrite the first binary. This will not overwrite system binaries but only binaries put into the global node_modules directory. This b
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in writing / maps
Open-source toolkit for the QVeris capability routing network: CLI, MCP server, Python SDK, skills, and REST API docs for agents to discover, inspect, call, and audit real-world tools.
Markdown to WeChat CLI | 一键排版发布到微信公众号:支持 40+ 排版样式和专业主题 、AI 配图 、批量发布
Define task-specific AI sub-agents in Markdown for any MCP-compatible tool.
AI prompt optimization for 58+ platforms across 7 categories with custom platforms
MCP Security Weekly
Get CVE alerts and security updates for io.github.yanislav-igonin/random-design-mcp and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
TypeScript MCP server that returns randomized English Markdown frontend design directions. It uses curated catalogs and optional soft compatibility scoring. It does not call an LLM.
Website: https://random-design-mcp.h0b0.dev
Use the published npm package from any MCP client that supports stdio servers:
{
"mcpServers": {
"random-design": {
"command": "npx",
"args": ["-y", "random-design-mcp"]
}
}
}
generate_design_description returns one randomized Markdown design direction.
All input fields are optional, but passing context makes the result easier to
use:
{
productType?: string;
audience?: string;
priority?: string;
compatibility?: boolean; // defaults to true
}
productType: what you are designing, such as landing page, dashboard,
mobile app, or pricing page.audience: who the interface is for, such as developers, founders, or
enterprise buyers.priority: what the design should optimize for or pay extra attention to,
such as conversion, readability, premium feel, dense data display, or
playful experimentation.compatibility: controls how wild the random combination can be. It defaults
to true, which keeps generated parameters more coherent and practical. Set
it to false for unconstrained combinations that can intentionally mix
clashing eras, styles, palettes, layouts, and materials.get_version takes no arguments and returns the package version from
package.json. Use it to confirm which published or cached MCP package version
an MCP client is running.
npm install
npm run build
npm run check
Preview one generated design direction locally:
npm run dev
Optional preview context:
RANDOM_DESIGN_PRODUCT_TYPE="Landing page" \
RANDOM_DESIGN_AUDIENCE="Developers" \
RANDOM_DESIGN_PRIORITY="Conversion" \
RANDOM_DESIGN_COMPATIBILITY=false \
npm run dev