by jimprosser · MCP Server · ★ 187
Last updated: · Indexed by AgentSkillsHub · Auto-synced every 8h
git clone https://github.com/jimprosser/obsidian-web-mcp.gitTaken 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 | 187 |
| Forks | 58 |
| Language | Python |
| Category | MCP Server |
| License | MIT |
| Quality Score | 75/100 |
| Open Issues | 2 |
| Last Updated | 2026-10-22 |
| Created | 2026-03-17 |
| Platforms | browser, claude-code, cli, mcp, python |
| Est. Tokens | ~18k |
obsidian-web-mcp A secure, remote-accessible MCP server that gives LLMs read/write access to your Obsidian vault from anywhere -- your desktop, your phone, a hotel Wi-Fi network. Unlike local-only Obsidian MCP servers, this one runs over HTTPS with real authentication, so Claude (or any MCP client) can reach your vault whether you're at your desk or not.
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: