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/gyuch-an02/claude-omakaseWrote 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/gyuch-an02/claude-omakase/omakase)<a href="https://agentmods.dev/mcp/gyuch-an02/claude-omakase/omakase"><img src="https://agentmods.dev/badge/mcp/gyuch-an02/claude-omakase/omakase/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/gyuch-an02/claude-omakase/omakase"><img src="https://agentmods.dev/badge/mcp/gyuch-an02/claude-omakase/omakase.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
omakase 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.
This is a copy
86% identical to chrome-tools — 4 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
{
"omakase": {
"command": "npx",
"args": [
"-y",
"claude-omakase"
]
}
}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 · 9 lines scan A 35ed0b4b90af
omakase is an MCP server published in the GitHub repository gyuch-an02/claude-omakase (8 stars, last pushed yesterday), 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. It is 86% identical to chrome-tools, differing in 4 lines, and is treated as a copy.
Other mcp servers, from other repositories
whoop-mcp-server
MCP server "whoop-mcp-server" as configured in yuridivonis/whoop-mcp-server. Runs in Docker (ghcr.io/yuridivonis/whoop-mcp-server:1.4.1). Needs 7 environment variables to run.
trust-oracle
Independent A-F trust grade for any MCP server, watched for drift. Free, never for sale. Remote server at wmcp.sh.
workrail-dev
MCP server "workrail-dev", hosted remotely at localhost, as configured in EtienneBBeaulac/workrail.
sui-mcp
Read-only Sui blockchain analytics: 61 tools, protocol-aware tx decoding, no API keys or wallet. Runs locally from the sui-analytics-mcp npm package. Needs 6 environment variables to run.
slack-mcp
MCP server "slack-mcp" as configured in adelaidasofia/slack-mcp. Launched with https://github.com/adelaidasofia/slack-mcp/releases/download/v0.1.1/slack-mcp.mc. Needs 1 environment variable to run.
reddit-mcp
Read Reddit from local MCP-compatible clients, including Claude Code and Codex, with no API key, app registration or OAuth. A stdio MCP server over Reddit's public RSS feeds. Runs locally from the reddit-rss-mcp Python package.