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.
npx agentmods add mcp/coooolinz/why-note-mcp/why-notegit clone --depth 1 https://github.com/Coooolinz/why-note-mcpGrade 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 2d 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.
- 2d 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 23d 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
obsidian-mcp-server
Read, write, search, and surgically edit Obsidian notes, tags, and frontmatter via MCP. Runs locally from the obsidian-mcp-server npm package. Needs 10 environment variables to run.
better-notion-mcp
Markdown-first MCP server for Notion API with 8 composite tools and 39 actions. Runs locally from the @n24q02m/better-notion-mcp npm package. Needs 1 environment variable to run.
plonk
MCP server for Plonk: macOS window zones, workspaces, keep-awake, screenshots and on-device OCR. Runs locally from the plonk-mcp npm package.
multi-account-gmail-mcp
Multi-account Gmail MCP server for AI agents. Runs locally from the multi-account-gmail-mcp Python package. Needs 3 environment variables to run.
better-workspace-mcp
Google Workspace MCP — Docs, Drive, Calendar, Gmail, Sheets, Slides, Tasks, Chat, People, Forms. Runs locally from the @n24q02m/better-workspace-mcp npm package. Needs 2 environment variables to run.
slack-mcp
Read and write Slack with session tokens — no OAuth, no bot, no admin approval. Runs locally from the @aaronsb/slack-mcp npm package. Needs 2 environment variables to run.