io.github.afable702/vault-mcp-tools
io.github.afable702/vault-mcp-tools
Is the io.github.afable702/vault-mcp-tools MCP server down? Yes. It has given no valid answer since 2026-10-17: not found.
Complete Obsidian vault MCP server. 35 tools: notes, search, graph, tags, canvas.
not found down since 2026-10-17 · probed 2026-11-14 · unchanged since 2026-10-31
npm error notarget In most cases you or one of your dependencies are requesting npm error notarget a package version that doesn't exist. npm error A complete lo
- Run it
- npx -y vault-mcp-tools@1.0.1 (stdio, probed in a container with the network off)
- Host
- npmjs.com
- Repository
- https://github.com/afable702/obsidian-mcp-server
- Registry
- active, updated 2026-04-11 · registry entry
Compare this server with others.
More servers
Other registry entries on npmjs.com, the ones next to this name; all of them.
- Pane io.github.aerolalit/pane · alive
- io.github.aeronlabs/aeron-wallet · alive
- io.github.aethynio/aethyn-browser-mcp · alive
- Computer Use Turbo io.github.afaaq-io/computer-use-turbo · alive
- io.github.afferens/mcp-server · alive
- Baserow Schema MCP io.github.aficiomaquinas/mcp-baserow-schema · alive
- Bacon Services io.github.afmontoya/baconservices-mcp · alive
- io.github.africa-api/africa-api-mcp · alive
Servers that mention vault.
- Hyperresearch ai.hyperresearch/hyperresearch · needs auth
- JustOnce ai.justonce/memory · needs auth
- ai.smithery/Hint-Services-obsidian-github-mcp · not found
- ai.smithery/sunub-obsidian-mcp-server · not found
- Insuro au.com.insuro/insuro · alive
- Arca build.arca.mcp/arca-mcp-server · needs auth
- cc.accrue/mcp · alive
- AgentBrink com.agentbrink.www/mcp · needs auth
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- No valid answer since 2026-10-17, in every probe since then.
- The endpoint answers HTTP 404. The registry entry points to a URL that is not an MCP endpoint any more. Publish a new version of the registry entry with the current URL.