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/manansingh2001/figma-react-mcp-server/figma-reactgit clone --depth 1 https://github.com/MananSingh2001/figma-react-mcp-serverWrote 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/manansingh2001/figma-react-mcp-server/figma-react)<a href="https://agentmods.dev/mcp/manansingh2001/figma-react-mcp-server/figma-react"><img src="https://agentmods.dev/badge/mcp/manansingh2001/figma-react-mcp-server/figma-react.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
figma-react 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
{
"figma-react": {
"command": "npx",
"args": [
"-y",
"@manansiingh/figma-react-mcp-server"
],
"env": {}
}
}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 · 10 lines scan A a718a2419071
figma-react is an MCP server published in the GitHub repository MananSingh2001/figma-react-mcp-server (1 stars, last pushed 5mo 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
aicanvas
Browse and install 75+ free animated, shadcn-compatible React components from AI Canvas. Runs locally from the @aicanvas/mcp npm package.
metricui
React dashboard components — API lookup, code generation, and prop validation for AI tools. Runs locally from the @metricui/mcp-server npm package.
figma-dev-tools
Figma Dev Tools MCP Server v1.4.13 - Bridge Figma designs to code with AI-powered token extraction, framework-agnostic structured data, React/Vue/HTML component generation, asset downloads, XSS security protection, smart hierarchy fixing, SVG inline rende. Runs locally from the figma-dev-tools npm package.
uiux-tools-react-mui
MCP Server with UX/UI best practices for React + Material-UI (Nielsen Heuristics, Cognitive Biases, Apple Design, Responsive patterns). Runs locally from the @marcusbarcelos/uiux-tools-react-mui npm package.
react-design-systems-mcp
Model Context Protocol (MCP) server that provides comprehensive information about design systems created for React, currently focusing on AWS Cloudscape Design System. Runs locally from the @agentience/react-design-systems-mcp npm package.
its-just-mcp
MCP server for its-just-ui React component library - Generate, customize, and document UI components with AI. Runs locally from the its-just-mcp npm package.