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/supertrained/rhumbWrote 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/supertrained/rhumb/mcp-rhumb-mcp)<a href="https://agentmods.dev/mcp/supertrained/rhumb/mcp-rhumb-mcp"><img src="https://agentmods.dev/badge/mcp/supertrained/rhumb/mcp-rhumb-mcp.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
rhumb-mcp 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 8d 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
{
"rhumb-mcp": {
"command": "npx",
"args": [
"-y",
"rhumb-mcp"
],
"env": {
"RHUMB_API_KEY": ""
}
}
}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.
- 8d ago First seen · 12 lines scan A 21d8e9f6bbaa
rhumb-mcp is an MCP server published in the GitHub repository supertrained/rhumb (3 stars, last pushed 3mo 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
mandu
MCP server "mandu" as configured in konamgil/mandu. Launched with bun run packages/mcp/src/index.ts.
workspaceguard
Per-workspace usage metering and fail-closed quota caps for shared self-hosted AI assistant deployments (Odysseus and compatible backends). Genuine independent Python port with the same CLI and --json shapes as the npm package. Runs locally from the workspaceguard-cli Python package.
toolcairn-mcp
MCP server for tool discovery: find, compare, and verify tools across 35+ registries. Runs locally from the @neurynae/toolcairn-mcp npm package.
lsp
MCP server "lsp" as configured in blackwell-systems/agent-lsp. Launched with agent-lsp go:gopls.
pare-test
Pare Test ג€” Auto-detects test framework (pytest, jest, vitest, mocha), returns typed JSON. Runs locally from the @paretools/test npm package.
chist
MCP server "chist" as configured in hiropon164/chist-server. Runs locally from the chist Python package.