io.github.labacacia/banyan-memory
Banyan Memory
Is the Banyan Memory MCP server down? Yes. It has given no valid answer since 2026-10-31: not found.
Persistent, governed local memory for MCP-compatible AI clients.
not found down since 2026-10-31 · probed 2026-11-14 · unchanged since 2026-11-07
download answered HTTP 404
- Bundle
- https://github.com/labacacia/banyan-brain-lite/releases/download/v1.5.1/banyan-memory-1.5.1-win-x64.mcpb (MCPB, for a client that installs bundles; probed in a container with the network off)
- Host
- github.com
- Repository
- https://github.com/labacacia/banyan-brain-lite
- Registry
- active, updated 2026-07-27 · registry entry
Compare this server with others.
More servers
Other registry entries on github.com, the ones next to this name; all of them.
- Google Play Store io.github.kryuchenko/gpscrape · alive
- KubeDrive io.github.kubedrive/kubedrive · not found
- io.github.kubeshark/mcp · install failed
- BLACKPROOF Local MCP io.github.l0gfr/blackproof · crashed on start
- Tenable Docs MCP io.github.lanz/tenable-docs-mcp · alive
- SpecForge io.github.leaderiop/specforge · crashed on start
- AVE for Claude Code — Local Video Editing io.github.lemberalla/ave-claude-code · crashed on start
- AVE for Codex CLI — Local Video Editing io.github.lemberalla/ave-codex · crashed on start
Servers that mention memory.
- AgentPlaybooks ai.agentplaybooks/agentplaybooks · needs auth
- Ambix ai.ambix/ambix · needs auth
- Atlaso Memory ai.atlaso/mcp · needs auth
- ai.butlerbrain/mcp · needs auth
- Contexel ai.contexel/contexel · needs auth
- Daystruct ai.daystruct.api/daystruct · alive
- DoneThat ai.donethat/donethat · needs auth
- ai.dataecho/mcp · alive
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-31, 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.