io.github.photoxpedia/bolor-brain-mcp
io.github.photoxpedia/bolor-brain-mcp
Is the io.github.photoxpedia/bolor-brain-mcp MCP server down? Yes. It has given no valid answer since 2026-10-16: not found.
Cognitive architecture MCP server with memory, learning, and contextual understanding
not found down since 2026-10-16 · probed 2026-11-15 · unchanged since 2026-10-30
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 bolor-brain-mcp@1.1.0 (stdio, probed in a container with the network off)
- Host
- npmjs.com
- Repository
- https://github.com/photoxpedia/bolor-brain-mcp.git
- Registry
- active, updated 2025-11-26 · registry entry
Compare this server with others.
More servers
Other registry entries on npmjs.com, the ones next to this name; all of them.
- io.github.philo-kim/openharness · alive
- io.github.philpof102-svg/lawbor · crashed on start
- io.github.philrox/ris · alive
- PhotoFresco io.github.photofresco/photofresco · alive
- io.github.pi22by7/in-memoria · crashed on start
- Pic2Vector io.github.pic2vector/pic2vector · alive
- picomcp docs io.github.picomcp/picomcp-docs · alive
- io.github.pierreb4/seven-dpt-mcp · alive
Servers that mention understanding or architecture.
- Arketo ai.arketo/arketo · needs auth
- ai.primateintelligence/mcp · needs auth
- aiponge app.aiponge/mcp · not MCP
- FactScan AI app.factscanai/factscan · needs auth
- Aiqbee Brain com.aiqbee/brain · needs auth
- Brainiall Image com.brainiall/image · alive
- ExcaliClaw com.excaliclaw/excaliclaw · needs auth
- GitDiagram com.gitdiagram/gitdiagram · 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-16, 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.