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/bejaminjones/bear-notes-mcp/bear-notesgit clone --depth 1 https://github.com/bejaminjones/bear-notes-mcpGrade 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 yesterday.
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.
- yesterday 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 6mo 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.
better-bear
MCP server for Bear notes — read, search, create, edit, tag, and manage notes via CloudKit. Runs locally from the better-bear npm package.
sequential-thinking
Adds a structured step-by-step reasoning tool the agent can call to break a problem into revisable thoughts. Runs locally from the @modelcontextprotocol/server-sequential-thinking npm package.
context7
Gives the agent up-to-date documentation and code examples for libraries and frameworks, fetched on demand so answers are not stuck at the model's training cutoff. Runs locally from the @upstash/context7-mcp npm package.
oka-anywhere
Your office's procedures inside Claude or ChatGPT - verified citations or an honest refusal. Remote server at console.forgeagentsai.com.