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/tokusumi/wassden-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/tokusumi/wassden-mcp/wassden)<a href="https://agentmods.dev/mcp/tokusumi/wassden-mcp/wassden"><img src="https://agentmods.dev/badge/mcp/tokusumi/wassden-mcp/wassden/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/tokusumi/wassden-mcp/wassden"><img src="https://agentmods.dev/badge/mcp/tokusumi/wassden-mcp/wassden.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
wassden 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 12d 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
{ "wassden": { "command": "uvx", "args": [ "wassden" ] } }
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.
- 12d ago First seen · 8 lines scan A 2fe12820fe4a
wassden is an MCP server published in the GitHub repository tokusumi/wassden-mcp (1 stars, last pushed 9mo 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
slack-mcp-server
Catch up on Slack without reading it. Unreads, threads, search. Browser-session or hosted OAuth. Runs locally from the @jtalk22/slack-mcp npm package. Needs 2 environment variables to run.
context7
Context7's hosted MCP server: up-to-date library documentation and code examples on demand. Remote server at mcp.context7.com.
twscrape-twitter-mcp
Read-optimized MCP server for Twitter/X, wrapping twscrape. BYO cookies, multi-account pool, agent-friendly tools. Runs locally from the twscrape-twitter-mcp Python package.
memgrep
MCP server "memgrep" as configured in gitwork-oss/memgrep. Launched with ${userHome}/.nvm/versions/node/v20.20.2/bin/memgrep serve.
contextforge-mcp
Persistent memory MCP server for Claude Code, Cursor, and GitHub Copilot. Runs locally from the contextforge-mcp npm package. Needs 2 environment variables to run.
recall
Open-source agent-memory MCP server. recall.works. Runs locally from the ai-recallworks Python package.