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.
npx agentmods add mcp/rhesis-ai/rhesis/rhesis-rhesisgit clone --depth 1 https://github.com/rhesis-ai/rhesisWrote 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/rhesis-ai/rhesis/rhesis-rhesis)<a href="https://agentmods.dev/mcp/rhesis-ai/rhesis/rhesis-rhesis"><img src="https://agentmods.dev/badge/mcp/rhesis-ai/rhesis/rhesis-rhesis.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
rhesis 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 2d 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.
- 2d ago Changed 40476985bea1
- 6d ago First seen · 9 lines scan A 12feefe35eec
rhesis is an MCP server published in the GitHub repository rhesis-ai/rhesis (391 stars, last pushed yesterday), 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-30.
Other mcp servers, from other repositories
nora
Operate self-hosted OpenClaw and Hermes agent fleets on Docker or Kubernetes from MCP clients. Runs locally from the @noraai/mcp-server npm package. Needs 3 environment variables to run.
mcp-zenml
MCP server "mcp-zenml" as configured in zenml-io/mcp-zenml. Runs in Docker (docker.io/zenmldocker/mcp-zenml:1.5.1). Needs 2 environment variables to run.
unified-ai-system
MCP server "unified-ai-system" as configured in happy520ai/unified-ai-system. Runs in Docker (ghcr.io/happy520ai/unified-ai-system/mcp-server@sha256:751a0d32acd2d6b1da6ad9ac67987fbd1ff36ce26b7160014d8605f18b7907b3).
resilireplay
Inject deterministic MCP failures, verify bounded recovery, and generate executable regression tests. Runs locally from the resilireplay npm package.
agenttape
MCP server "agenttape" as configured in jiangkoumo/agenttape. Runs ./dist/mcp-server.mjs with node.
hotato
Find what broke in your agent calls. Pin it and CI stays red until you fix it. Local call forensics and regression guards for AI agents: turn timing, and whether the agent did what it said. Nothing leaves your machine. Runs locally from the hotato Python package.