io.github.GRU-953/dev953

Is the io.github.GRU-953/dev953 MCP server down? Yes. It has given no valid answer since 2026-10-18: not found.

dev953 method companion: exposes its multi-agent coding method as callable MCP tools.

not found down since 2026-10-18 · probed 2026-11-14 · unchanged since 2026-11-01

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 dev953-mcp@1.2.0 (stdio, probed in a container with the network off)
Host: npmjs.com
Repository: https://github.com/GRU-953/dev953
Registry: active, updated 2026-06-23 · 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.GabrielaHdzMicrosoft/mcp-server · timeout
io.github.GCTRL-TECH/gctrl · needs env
io.github.GLips/Figma-Context-MCP · alive
LayerOne (DocX + Sign) io.github.GOLayerone/layerone · alive
io.github.GORZ-APP/gorz · alive
io.github.GRU-953/gru953-crew · not found
MySQL Ops MCP io.github.GT-dinuo/mysql-ops-mcp · needs network
Server Ops MCP io.github.GT-dinuo/server-ops-mcp · crashed on start

Servers that mention companion or callable.

Lovora ai.lovora/lovora · alive
Revuo ai.revuo/revuo · alive
SessionKeeper ai.sessionkeeper/mcp · needs auth
FFT Companion app.fftcompanion/fft-companion · alive
Fryd - Your Garden Companion app.fryd/mcp-server · alive
FEDLIN Scanners com.fedlin/fedlin-mcp-server · alive
Color Companion com.gumballtools/color-companion · alive
com.httpstatus/mcp-server · 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.

Atom feed

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-18, 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.