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/suomimasuda/rightos-sdkWrote 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/suomimasuda/rightos-sdk/rightos-mcp)<a href="https://agentmods.dev/mcp/suomimasuda/rightos-sdk/rightos-mcp"><img src="https://agentmods.dev/badge/mcp/suomimasuda/rightos-sdk/rightos-mcp/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/suomimasuda/rightos-sdk/rightos-mcp"><img src="https://agentmods.dev/badge/mcp/suomimasuda/rightos-sdk/rightos-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
rightos-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 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
{
"rightos-mcp": {
"command": "npx",
"args": [
"-y",
"@i-s3/rightos-mcp"
],
"env": {
"RIGHTOS_API_KEY": "",
"RIGHTOS_BASE_URL": ""
}
}
}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 · 13 lines scan A f8d9e7d5113e
rightos-mcp is an MCP server published in the GitHub repository suomimasuda/rightos-sdk (0 stars, last pushed 7d 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
picocalc-mcp
MCP server for PicoCalc MicroPython hardware development. Runs locally from the picocalc-mcp Python package.
mcp-synology
MCP server for Synology NAS — manage files on your NAS via Claude. Runs locally from the mcp-synology Python package.
weilink
MCP server "weilink" as configured in Oaklight/weilink. Launched with weilink mcp.
wet-mcp
Open-source MCP Server for web search, extract, crawl, academic research, and library docs with embedded SearXNG. Runs locally from the wet-mcp Python package. Needs 2 environment variables to run.
mnemo-mcp
Open-source MCP Server for persistent AI memory with embedded sync. Runs locally from the mnemo-mcp Python package. Needs 1 environment variable to run.
starlink-mcp-server
MCP server "starlink-mcp-server" as configured in ry-ops/starlink-enterprise-mcp-server. Runs locally from the starlink-mcp-server Python package.