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/lyr1cs/reinWrote 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/lyr1cs/rein/rein-rein)<a href="https://agentmods.dev/mcp/lyr1cs/rein/rein-rein"><img src="https://agentmods.dev/badge/mcp/lyr1cs/rein/rein-rein/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/lyr1cs/rein/rein-rein"><img src="https://agentmods.dev/badge/mcp/lyr1cs/rein/rein-rein.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
rein 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 11d 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
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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.
- 11d ago First seen · 8 lines scan A b605e69545fb
rein is an MCP server published in the GitHub repository lyr1cs/rein (9 stars, last pushed 5d 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
rtfm
MCP server "rtfm" as configured in roomi-fields/rtfm. Launched with rtfm-serve. Needs 1 environment variable to run.
paper-intelligence
MCP server enabling AI agents to efficiently search and understand PDF documents. Runs locally from the paper-intelligence Python package.
ephemeral-buffer-mcp
MCP server "ephemeral-buffer-mcp" as configured in k-rister/ephemeral-buffer-mcp. Runs locally from the ephemeral-buffer-mcp Python package.
vectr
Semantic codebase search + persistent working memory for AI code editors. Local, zero-config, MCP. No API key. Runs locally from the vectr Python package.
tool-compass
Semantic MCP tool discovery gateway - find tools by intent, not memory. Runs locally from the tool-compass Python package.
nxopen-mcp
MCP server that gives AI coding agents accurate NXOpen .NET API knowledge via hybrid retrieval. Runs locally from the nxopen-mcp Python package.