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/crunchtools/mcp-metsukeWrote 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/crunchtools/mcp-metsuke/metsuke)<a href="https://agentmods.dev/mcp/crunchtools/mcp-metsuke/metsuke"><img src="https://agentmods.dev/badge/mcp/crunchtools/mcp-metsuke/metsuke/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/crunchtools/mcp-metsuke/metsuke"><img src="https://agentmods.dev/badge/mcp/crunchtools/mcp-metsuke/metsuke.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
metsuke 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.
The source is not reproduced here
Licensed AGPL-3.0
The repository is licensed AGPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
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 7f4bd81e8592
metsuke is an MCP server published in the GitHub repository crunchtools/mcp-metsuke (0 stars, last pushed 6d ago), licensed AGPL-3.0. 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
slack
Secure read-only MCP server for Slack workspaces. Runs locally from the mcp-slack-crunchtools Python package.
gitlab
Secure MCP server for GitLab projects, merge requests, issues, and pipelines. Runs locally from the mcp-gitlab-crunchtools Python package.
wordpress
Secure MCP server for WordPress content management. Runs locally from the mcp-wordpress-crunchtools Python package.
workboard
Secure MCP server for WorkBoard OKR and strategy execution platform. Runs locally from the mcp-workboard-crunchtools Python package.
nagios
Secure MCP server for Nagios Core monitoring — query status, acknowledge problems, manage checks. Runs locally from the mcp-nagios-crunchtools Python package.
github
Secure MCP server for GitHub issues, pull requests, files, and search. Runs locally from the mcp-github-crunchtools Python package.