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/ViGi-P/lucide-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/vigi-p/lucide-mcp/lucide-mcp)<a href="https://agentmods.dev/mcp/vigi-p/lucide-mcp/lucide-mcp"><img src="https://agentmods.dev/badge/mcp/vigi-p/lucide-mcp/lucide-mcp/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/vigi-p/lucide-mcp/lucide-mcp"><img src="https://agentmods.dev/badge/mcp/vigi-p/lucide-mcp/lucide-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
lucide-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 11d 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
{ "lucide-mcp": { "command": "npx", "args": [ "-y", "@vigi-p/lucide-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.
- 11d ago First seen · 9 lines scan A af1f5c27b454
lucide-mcp is an MCP server published in the GitHub repository ViGi-P/lucide-mcp (0 stars, last pushed 1mo 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-08-31.
Other mcp servers, from other repositories
vynix-mcp
Give AI coding agents access to your Vynix visual feedback, bug reports, and AI diagnosis. Runs locally from the @usevynix/mcp-server npm package. Needs 2 environment variables to run.
uiverse-mcp
MCP server "uiverse-mcp" as configured in Fabi-SPL/uiverse-mcp. Runs locally from the uiverse-mcp npm package.
pare-search
Pare Search ג€” Structured code search operations (ripgrep + fd) as typed JSON. Runs locally from the @paretools/search npm package.
pare-test
Pare Test ג€” Auto-detects test framework (pytest, jest, vitest, mocha), returns typed JSON. Runs locally from the @paretools/test npm package.
m1nd
MCP server "m1nd" as configured in maxkle1nz/m1nd. Launched with m1nd-mcp --stdio --no-gui. Needs 1 environment variable to run.
mcp-flux-pro
MCP Server for Flux AI Image Generation via AceDataCloud API. Runs locally from the mcp-flux-pro Python package. Needs 1 environment variable to run.