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/euuuuuuan/reasonforge-publicWrote 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/euuuuuuan/reasonforge-public/reasonforge)<a href="https://agentmods.dev/mcp/euuuuuuan/reasonforge-public/reasonforge"><img src="https://agentmods.dev/badge/mcp/euuuuuuan/reasonforge-public/reasonforge/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/euuuuuuan/reasonforge-public/reasonforge"><img src="https://agentmods.dev/badge/mcp/euuuuuuan/reasonforge-public/reasonforge.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
reasonforge 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
{ "reasonforge": { "command": "npx", "args": [ "-y", "reasonforge" ] } }
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 712e81c9d110
reasonforge is an MCP server published in the GitHub repository euuuuuuan/reasonforge-public (0 stars, last pushed 2mo ago), licensed Apache-2.0. 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
mcptoon
MCP server "mcptoon" as configured in activeing123/mcptoon. Launched with mcptoon serve.
tweetkit-x
Post, delete & read on X (Twitter) from Python & MCP using your own web session — no paid API. Runs locally from the tweetkit-x Python package. Needs 2 environment variables to run.
sqlike-mcp
SQL static analysis & query-equivalence for Postgres, MySQL, SQLite, and SQL Server. Runs locally from the @sqlike/mcp npm package. Needs 1 environment variable to run.
aiterm-mcp
Persistent terminals and one launcher for Claude, Codex, Grok, and Cursor harnesses. Runs locally from the aiterm-mcp npm package.
tiktok-agent-publisher
Local-first TikTok Content Posting API for AI agents: OAuth checks, dry-run and live uploads. Runs locally from the tiktok-agent-publisher npm package. Needs 3 environment variables to run.
labellevie-mcp
MCP server "labellevie-mcp" as configured in McCANNParis/MCPServerLaBelleVie. Runs locally from the labellevie-mcp npm package.