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/kimosahy/railroadedWrote 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/kimosahy/railroaded/heroui-react)<a href="https://agentmods.dev/mcp/kimosahy/railroaded/heroui-react"><img src="https://agentmods.dev/badge/mcp/kimosahy/railroaded/heroui-react/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/kimosahy/railroaded/heroui-react"><img src="https://agentmods.dev/badge/mcp/kimosahy/railroaded/heroui-react.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
heroui-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 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
{
"heroui-react": {
"command": "npx",
"args": [
"-y",
"@heroui/react-mcp@latest"
]
}
}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 · 9 lines scan A 725d4236cb19
heroui-react is an MCP server published in the GitHub repository kimosahy/railroaded (3 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
worldos-voice
MCP server "worldos-voice" as configured in electricsheephq/WorldOS. Runs locally from the ${CLAUDE_PLUGIN_ROOT}/servers/voice Python package. Needs 1 environment variable to run.
worldos-engine
MCP server "worldos-engine" as configured in electricsheephq/WorldOS. Runs locally from the ${CLAUDE_PLUGIN_ROOT}/servers/engine Python package.
worldos-rules
MCP server "worldos-rules" as configured in electricsheephq/WorldOS. Runs locally from the ${CLAUDE_PLUGIN_ROOT}/servers/rules Python package.
mcp-server
Unified MCP server for Ignite UI — documentation, API, and CLI scaffolding. Runs locally from the @igniteui/mcp-server npm package.
agent-guild
MCP server "agent-guild", hosted remotely at agent-guild-5d5r.onrender.com, as configured in AgentTanuki/agent-guild.
figma-dev-tools
Figma Dev Tools MCP Server v1.4.21 - 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.