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/SrinjoyDev/rewyndInstalling this writes the configuration, not the program: `rewynd` has to be on your PATH already, or the server will not start.
Wrote 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/srinjoydev/rewynd/claude-code-rewynd)<a href="https://agentmods.dev/mcp/srinjoydev/rewynd/claude-code-rewynd"><img src="https://agentmods.dev/badge/mcp/srinjoydev/rewynd/claude-code-rewynd/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/srinjoydev/rewynd/claude-code-rewynd"><img src="https://agentmods.dev/badge/mcp/srinjoydev/rewynd/claude-code-rewynd.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
rewynd 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
{
"rewynd": {
"command": "rewynd",
"args": [
"mcp"
]
}
}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 · 8 lines scan A c89c21b1e4b7
rewynd is an MCP server published in the GitHub repository SrinjoyDev/rewynd (2 stars, last pushed 4mo 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
code-review-graph
MCP server "code-review-graph" as configured in mrwogu/promptscript. Launched with code-review-graph serve.
tirith-gateway
MCP server "tirith-gateway" as configured in sheeki03/tirith. Launched with tirith gateway run --upstream-bin tirith --upstream-arg mcp-server --config ~/.c.
portview
MCP server "portview" as configured in Mapika/portview. Launched with portview.
patchloom
MCP server "patchloom" as configured in patchloom/patchloom. Launched with patchloom.
log-essence
Intelligent log analysis for LLMs - extract patterns, redact secrets, compress 50%+. Runs locally from the log-essence Python package.
aegis
Credential isolation for AI agents. Inject secrets at the network boundary. Runs locally from the @getaegis/cli npm package. Needs 11 environment variables to run.