Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/lnksoul1/prism-ui-designWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/lnksoul1/prism-ui-design/ui-design-mcp-server)<a href="https://agentmods.dev/mcp/lnksoul1/prism-ui-design/ui-design-mcp-server"><img src="https://agentmods.dev/badge/mcp/lnksoul1/prism-ui-design/ui-design-mcp-server/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/lnksoul1/prism-ui-design/ui-design-mcp-server"><img src="https://agentmods.dev/badge/mcp/lnksoul1/prism-ui-design/ui-design-mcp-server.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket warn
Grade A, and why
ui-design-mcp-server scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 3d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{ "ui-design-mcp-server": { "command": "npx", "args": [ "-y", "ui-design-mcp-server" ] } }
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 3d ago First seen · 9 lines scan A 798cb6c9b087
ui-design-mcp-server is an MCP server published in the GitHub repository lnksoul1/prism-ui-design (0 stars, last pushed 2d ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-15.
Other mcp servers, from other repositories
standby-design-mcp
Generate design systems: OKLCH color palettes, fluid type scales, spacing, shape and icon tokens. Runs locally from the standby-design-mcp npm package.
design-data
MCP server and Claude Code skill for the design-data agent surface — read tools run in-process via wasm. Runs locally from the @adobe/design-data-agent-mcp npm package. Needs 5 environment variables to run.
figma
MCP server "figma", hosted remotely at mcp.figma.com, as configured in adobe/spectrum-design-data.
mcp-design-system-extractor
MCP server for Storybook design systems — extract component HTML, styles and metadata. Runs locally from the mcp-design-system-extractor npm package. Needs 3 environment variables to run.
mimic-ai
Builds Figma from your design system: real components and tokens, enforced, learning every build. Runs locally from the @miapre/mimic-ai npm package.
figma-mcp-bridge
MCP server "figma-mcp-bridge" as configured in atezer/FMCP. Runs /REPLACE/WITH/ABSOLUTE/PATH/TO/FCM/dist/local-plugin-only.js with node. Needs 1 environment variable to run.