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/vasylenko/bear-notes-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/vasylenko/bear-notes-mcp/bear-notes-project-local)<a href="https://agentmods.dev/mcp/vasylenko/bear-notes-mcp/bear-notes-project-local"><img src="https://agentmods.dev/badge/mcp/vasylenko/bear-notes-mcp/bear-notes-project-local/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/vasylenko/bear-notes-mcp/bear-notes-project-local"><img src="https://agentmods.dev/badge/mcp/vasylenko/bear-notes-mcp/bear-notes-project-local.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
bear-notes-project-local 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.
What it actually says
{
"bear-notes-project-local": {
"env": {
"UI_ENABLE_NEW_NOTE_CONVENTION": "true",
"UI_ENABLE_CONTENT_REPLACEMENT": "true"
},
"command": "npx",
"args": [
"tsx",
"src/main.ts"
]
}
}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 · 13 lines scan A 86fc79f498ed
bear-notes-project-local is an MCP server published in the GitHub repository vasylenko/bear-notes-mcp (205 stars, last pushed 3mo 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
bear-notes
MCP server "bear-notes" as configured in bejaminjones/bear-notes-mcp. Runs /path/to/bear-notes-mcp/dist/index.js with node. Needs 2 environment variables to run.
codemaster
Explore the Claude Code CLI source — browse tools, commands, search code, and more. Runs locally from the @divyesh2000/codemaster npm package.
nodejs-api-docs
An MCP Server for Node.js API documentation. Runs locally from the mcp-server-nodejs-api-docs npm package.
fetch
Lets the agent fetch a URL and read its content as markdown. Runs locally from the mcp-server-fetch Python package.
claude-faf-mcp
Persistent project context for Claude. IANA-registered .faf format. Runs locally from the claude-faf-mcp npm package.
canvas
MCP server "canvas" as configured in 98ping/chip. Runs vendor/canvas-mcp/server/index.js with node. Needs 2 environment variables to run.