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/vola-trebla/react-render-profile-mcp/react-render-profile-mcpgit clone --depth 1 https://github.com/vola-trebla/react-render-profile-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/vola-trebla/react-render-profile-mcp/react-render-profile-mcp)<a href="https://agentmods.dev/mcp/vola-trebla/react-render-profile-mcp/react-render-profile-mcp"><img src="https://agentmods.dev/badge/mcp/vola-trebla/react-render-profile-mcp/react-render-profile-mcp.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
react-render-profile-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 4d 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
{
"react-render-profile-mcp": {
"command": "npx",
"args": [
"-y",
"react-render-profile-mcp"
],
"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.
- 4d ago First seen · 10 lines scan A 715cf4defd59
react-render-profile-mcp is an MCP server published in the GitHub repository vola-trebla/react-render-profile-mcp (2 stars, last pushed 3mo 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
mcp
MCP server for UI Beats. Let your coding agent search, read and install animated React components. Runs locally from the @uibeats/mcp npm package.
mcp-server
Unified MCP server for Ignite UI — documentation, API, and CLI scaffolding. Runs locally from the @igniteui/mcp-server npm package.
ai-elements
MCP server "ai-elements", hosted remotely at registry.ai-sdk.dev, as configured in laguagu/claude-code-nextjs-skills.
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.
next-devtools
Next.js development tools MCP server with stdio transport. Runs locally from the next-devtools-mcp npm package.
docs-langchain
MCP server "docs-langchain", hosted remotely at docs.langchain.com, as configured in langchain-ai/langchain.