io.github.shinzarou-eng/codebase-chat
io.github.shinzarou-eng/codebase-chat
Is the io.github.shinzarou-eng/codebase-chat MCP server down? Yes. It has given no valid answer since 2026-10-20: install failed.
Local-first codebase intelligence: cited answers, audits, reports. EN/FR.
install failed down since 2026-10-20 · probed 2026-11-15 · unchanged since 2026-10-27
npm error code EUNSUPPORTEDPROTOCOL npm error Unsupported URL Type "workspace:": workspace:^ npm error A complete log of this run can be found in: /root/.npm/_l
- Run it
- npx -y codebase-chat-mcp@0.10.1 (stdio, probed in a container with the network off)
- Host
- npmjs.com
- Repository
- https://github.com/shinzarou-eng/codebase-chat
- Registry
- active, updated 2026-09-14 · 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.shinpr/mcp-image · alive
- io.github.shinpr/mcp-local-rag · needs env
- io.github.shinpr/sub-agents-mcp · needs env
- rutter io.github.shinytoyrobots/rutter · alive
- io.github.shinzarou-eng/dsh-codebase-chat · not found
- io.github.shitianfang/jev-use · crashed on start
- io.github.shivam-app-developers/ai-optimizer · alive
- io.github.shiyue1250/nuttle · alive
Servers that mention codebase.
- ai.docuwriter/docuwriter · needs auth
- Spiderbrain ai.spiderbrain/spiderbrain · needs auth
- RepoPilot app.repopilot/repopilot · not found
- VibeCom Growth Autopilot app.vibecom/growth · needs auth
- XRay-Vision com.emtailabs/xray-vision · needs auth
- Repowise (Hosted) dev.repowise/repowise-hosted · needs auth
- Architecture-DNA io.github.Evozim/architecture-dna · not found
- CleanCode AI io.github.Evozim/cleancode-ai · not found
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-20, in every probe since then.
- npx or uvx could not install the package. The package name in the registry entry is wrong, the package is not published, or the install needs a build step.