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.
npx agentmods add mcp/fidgetcoding/refero-design-mcp/fidgetcoding-refero-mcpgit clone --depth 1 https://github.com/fidgetcoding/refero-design-mcpWrote 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/fidgetcoding/refero-design-mcp/fidgetcoding-refero-mcp)<a href="https://agentmods.dev/mcp/fidgetcoding/refero-design-mcp/fidgetcoding-refero-mcp"><img src="https://agentmods.dev/badge/mcp/fidgetcoding/refero-design-mcp/fidgetcoding-refero-mcp.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
fidgetcoding-refero-mcp 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 5d 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
{ "fidgetcoding-refero-mcp": { "command": "npx", "args": [ "-y", "fidgetcoding-refero-mcp" ] } }
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.
- 5d ago First seen · 9 lines scan A fae12f8cb258
fidgetcoding-refero-mcp is an MCP server published in the GitHub repository fidgetcoding/refero-design-mcp (13 stars, last pushed yesterday), 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-08-30.
Other mcp servers, from other repositories
seed-design-local
MCP server "seed-design-local" as configured in daangn/seed-design. Launched with bun ./packages/mcp/bin/index.mjs.
ng-blatui
MCP server "ng-blatui", hosted remotely at ngblatui.remix-it.com, as configured in anousss007/ng-blatui.
slack
MCP server "slack" as configured in instructure/instructure-ui. Launched with sh -c set -a; [ -f ./.env ] && . ./.env; set +a; exec npx -y @modelcontextprotoc.
figma-desktop
MCP server "figma-desktop", hosted remotely at 127.0.0.1, as configured in naver/design-to-ui.
picassoweb
PicassoWeb — MCP server that turns any website into a faithful replication kit: design tokens, real assets, animations, layout trees, section clones, screenshots, and pixel-diff verification. Runs locally from the picassoweb npm package.
angular-cli
CLI tool for Angular. Runs locally from the @angular/cli npm package.