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/leboncoin/spark-webWrote 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/leboncoin/spark-web/figma)<a href="https://agentmods.dev/mcp/leboncoin/spark-web/figma"><img src="https://agentmods.dev/badge/mcp/leboncoin/spark-web/figma/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/leboncoin/spark-web/figma"><img src="https://agentmods.dev/badge/mcp/leboncoin/spark-web/figma.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
figma 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 1mo 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
{
"figma": {
"url": "https://mcp.figma.com/mcp"
}
}What else mcp.json configures
This page is one entry in a file that holds 3. Installing the file brings all of them; each is measured and scanned on its own page.
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.
- 1mo ago First seen · 5 lines scan A b970e73067f6
figma is an MCP server published in the GitHub repository leboncoin/spark-web (94 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-09-07.
Other mcp servers, from other repositories
mcp
Search Keyline Icons by name and get any icon's SVG source or React import. No key, no network. Runs locally from the @keyline-icons/mcp npm package.
aicanvas
Browse and install 75+ free animated, shadcn-compatible React components from AI Canvas. Runs locally from the @aicanvas/mcp npm package.
seed-design-local
MCP server "seed-design-local" as configured in daangn/seed-design. Launched with bun ./packages/mcp/bin/index.mjs.
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.
atag-mcp
ATAG 2.0 (Authoring Tool Accessibility Guidelines) guidance for authoring tool developers. Runs locally from the atag-mcp npm package.