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/n24q02m/wet-mcpWrote 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/n24q02m/wet-mcp/wet-mcp)<a href="https://agentmods.dev/mcp/n24q02m/wet-mcp/wet-mcp"><img src="https://agentmods.dev/badge/mcp/n24q02m/wet-mcp/wet-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/n24q02m/wet-mcp/wet-mcp"><img src="https://agentmods.dev/badge/mcp/n24q02m/wet-mcp/wet-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
wet-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.
Copies of this mod
1 near-identical copy found in the catalogue:
- wet-mcp — 100% identical, 0 lines differ
What it actually says
{
"wet-mcp": {
"command": "uvx",
"args": [
"wet-mcp"
],
"env": {
"API_KEYS": "",
"GITHUB_TOKEN": ""
}
}
}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 · 12 lines scan A c2c0d4b201c1
wet-mcp is an MCP server published in the GitHub repository n24q02m/wet-mcp (17 stars, last pushed 1mo ago), licensed Apache-2.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-30.
Other mcp servers, from other repositories
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.
mcp-synology
MCP server for Synology NAS — manage files on your NAS via Claude. Runs locally from the mcp-synology Python package.
computer-use-mcp
Control your computer with screenshots, mouse, and keyboard automation. Runs locally from the computer-use-mcp npm package.
charlotte
Renders web pages into structured, agent-readable representations using headless Chromium. Runs locally from the @ticktockbent/charlotte npm package.
unraid-mcp
MCP Server for Unraid API - provides tools to interact with an Unraid server's GraphQL API. Runs locally from the unraid-mcp Python package. Needs 3 environment variables to run.
ninjaone-mcp
MCP server "ninjaone-mcp" as configured in WYRE-AI/ninjaone-mcp. Runs in Docker (ghcr.io/wyre-ai/ninjaone-mcp:v2.5.2). Needs 6 environment variables to run.