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/bejaminjones/bear-notes-mcpInstalling this writes the configuration, not the program: `node` runs a file from the repository, so clone it first and make the path in the command match where you put it.
Wrote 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/bejaminjones/bear-notes-mcp/bear-notes)<a href="https://agentmods.dev/mcp/bejaminjones/bear-notes-mcp/bear-notes"><img src="https://agentmods.dev/badge/mcp/bejaminjones/bear-notes-mcp/bear-notes/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/bejaminjones/bear-notes-mcp/bear-notes"><img src="https://agentmods.dev/badge/mcp/bejaminjones/bear-notes-mcp/bear-notes.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
bear-notes 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": {
"command": "node",
"args": [
"/path/to/bear-notes-mcp/dist/index.js"
],
"env": {
"BEAR_DB_PATH": "~/Library/Group Containers/9K33E3U3T4.net.shinyfrog.bear/Application Data/database.sqlite",
"LOG_LEVEL": "info"
}
}
}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 ce6df465ad5b
bear-notes is an MCP server published in the GitHub repository bejaminjones/bear-notes-mcp (32 stars, last pushed 8mo 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-30.
Other mcp servers, from other repositories
bear-notes-project-local
TypeScript Execute (tsx): Node.js enhanced with esbuild to run TypeScript & ESM files. Runs locally from the tsx npm package. Needs 2 environment variables to run.
memory-engine-mcp
MCP server "memory-engine-mcp" as configured in SimoneB79/memory-engine-mcp. Runs in Docker (ghcr.io/simoneb79/memory-engine-mcp:1.5.3). Needs 3 environment variables to run.
remem
Local-first automatic memory for Claude Code and Codex: capture, distill, recall from SQLite. Runs locally from the @remem-ai/remem npm package.
tokenmizer
MCP server "tokenmizer" as configured in Shweta-Mishra-ai/tokenmizer. Launched with tokenmizer-mcp. Needs 2 environment variables to run.
claude-faf-mcp
Persistent project context for Claude. IANA-registered .faf format. Runs locally from the claude-faf-mcp npm package.
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.