by StevenStavrakis · MCP Server · ★ 741
Last updated: · Indexed by AgentSkillsHub · Auto-synced every 8h
npm install -g obsidian-mcp@2Taken from the project's README on GitHub. Check the security audit before running it.
None of the 42 rules matched — no credential harvesting, no data exfiltration, no curl-pipe-shell installer. Scanned against 42 published rules built on the SlowMist agent-security taxonomy, refreshed every 8 hours. Full audit →
The quality score combines nine heuristic checks of the repo and its README: completeness, clarity, specificity, examples, structure, agent readiness, step-by-step content, instruction quality and security notes. It rates how well the project explains itself to an agent, not the code.
| Stars | 741 |
| Forks | 94 |
| Language | TypeScript |
| Category | MCP Server |
| License | MIT |
| Quality Score | 69/100 |
| Open Issues | 15 |
| Last Updated | 2026-10-08 |
| Created | 2024-12-22 |
| Platforms | mcp, node |
| Est. Tokens | ~16k |
Obsidian MCP A local Model Context Protocol server that lets MCP-compatible assistants safely read and modify explicitly configured Obsidian vaults. Version 2 supports both MCP and 2025-era clients by default, and requires Node.js 22 or newer. It works directly with Markdown files, so Obsidian does not need to be open.
Explore other popular mcp server tools:
Grades come from a rule-based scan built on the SlowMist agent-security taxonomy: 42 published rules, covering credential harvesting, data exfiltration, curl | sh installers and more. It is a first-layer scan, not a manual audit — we say so rather than overstate it.
The scale of the problem is documented independently: Liu et al. (2026), in a study of 31,132 agent skills, report that 26.1% contain security vulnerabilities. Our own full-catalog census is published as a citable open dataset.
Sources & who's responsible: