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/dazeb/mcp-react-component-harvesterWrote 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/dazeb/mcp-react-component-harvester/mcp-component-harvester)<a href="https://agentmods.dev/mcp/dazeb/mcp-react-component-harvester/mcp-component-harvester"><img src="https://agentmods.dev/badge/mcp/dazeb/mcp-react-component-harvester/mcp-component-harvester.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
mcp-component-harvester 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 8d 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 8d ago First seen · 9 lines scan A b4299922c4d0
mcp-component-harvester is an MCP server published in the GitHub repository dazeb/mcp-react-component-harvester (8 stars, last pushed 1y ago), with no licence file. 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
should-i-render
A measured React component fit index for coding agents, served as a bundled-data MCP server. Runs locally from the should-i-render npm package.
mcp-react-toolkit
9 MCP servers for React/TypeScript — dep auditing, a11y, test gen, and TypeScript enforcement. Runs locally from the mcp-react-toolkit npm package.
local-component-mcp
AST-powered MCP server for Vue/React component analysis — eliminates AI hallucinations on local business components. Runs locally from the @wllcyg001/local-component-mcp npm package.
mern-mcp
Scaffolds MERN CRUD resources into existing Express and React codebases. Runs locally from the mern-mcp npm package. Needs 1 environment variable to run.
next-devtools
Next.js development tools MCP server with stdio transport. Runs locally from the next-devtools-mcp npm package.
svgr-mcp
MCP server for converting SVG to React components using SVGR. Runs locally from the svgr-mcp npm package.