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/Coooolinz/why-note-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/coooolinz/why-note-mcp/why-note)<a href="https://agentmods.dev/mcp/coooolinz/why-note-mcp/why-note"><img src="https://agentmods.dev/badge/mcp/coooolinz/why-note-mcp/why-note/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/coooolinz/why-note-mcp/why-note"><img src="https://agentmods.dev/badge/mcp/coooolinz/why-note-mcp/why-note.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
why-note 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 2mo 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
{
"why-note": {
"command": "npx",
"args": [
"-y",
"why-note-mcp"
],
"env": {
"NOTE_URL": "",
"NOTE_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.
- 2mo ago First seen · 13 lines scan A 905662955c47
why-note is an MCP server published in the GitHub repository Coooolinz/why-note-mcp (0 stars, last pushed 2mo 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.
why-note compared with mcp servers from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| why-noteCoooolinz/why-note-mcp | MCP server | 0 | 2mo ago | MIT | A | — | Claude Code, Codex, Cursor, Gemini CLI, OpenCode |
| obsidian-mcp-servercyanheads/obsidian-mcp-server | MCP server | 702 | 8d ago | Apache-2.0 | A | — | Claude Code |
| mcp-telegrammcp-telegram/mcp-telegram | MCP server | 67 | 6d ago | MIT | A | — | Claude Code, Codex, Cursor, Gemini CLI, OpenCode |
| mcp-flight-searcharjunprabhulal/mcp-flight-search | MCP server | 44 | 6d ago | MIT | A | — | Claude Code, Codex, Cursor, Gemini CLI, OpenCode |
| slack-mcp-serverjtalk22/slack-mcp-server | MCP server | 32 | yesterday | MIT | A | — | Claude Code, Codex, Cursor, Gemini CLI, OpenCode |
| plonkostapondo/Plonk | MCP server | 17 | 19d ago | MIT | A | — | Claude Code, Codex, Cursor, Gemini CLI, OpenCode |
| multi-account-gmail-mcpcunicopia-dev/gmail-mcp | MCP server | 6 | 5d ago | MIT | A | — | Claude Code, Codex, Cursor, Gemini CLI, OpenCode |