io.github.pasichDev/todo-mcp

Is the io.github.pasichDev/todo-mcp MCP server down? Yes. It has given no valid answer since 2026-10-19: not found.

Shared TODO/backlog MCP server with claim tracking, web UI, and encrypted local storage.

not found down since 2026-10-19 · probed 2026-11-14 · unchanged since 2026-10-26

npm error 404 Note that you can also install from a npm error 404 tarball, folder, http url, or git url. npm error A complete log of this run can be found in: /

Run it: npx -y @pasichdev/todo-mcp@2.2.0 (stdio, probed in a container with the network off)
Host: npmjs.com
Repository: https://github.com/pasichDev/todo-mcp
Registry: active, updated 2026-09-02 · registry entry

Compare this server with others.

More servers

Other registry entries on npmjs.com, the ones next to this name; all of them.

ParseRelay io.github.parserelay/mcp · alive
io.github.parthsevak2/curb-cut-mcp · crashed on start
FireKey MCP io.github.partnerhbhl/firekey-mcp · alive
io.github.pasichDev/docket · alive
Pastea io.github.pastea-app/pastea-mcp · alive
Patchloom io.github.patchloom/patchloom · crashed on start
PathCourse Health (PCH) io.github.pathcourse-health/mcp-server · alive
io.github.pathmodeio/mcp-server · alive

Servers that mention todo.

Signal not Noise ai.lifeisagame/signal-not-noise · needs auth
A Corrida dos Bairros: preço do m² por bairro br.com.acorridadosbairros/metro-quadrado · alive
MoonlyBox MoonLink cn.moonlybox/moonlink · needs auth
com.octo-dock/octodock · needs your URL
com.ritzademo/acme-todo · TLS error
RESET Verifica com.resetparatodos/verifica · alive
Schedule & Chill com.schedulenchill/mcp · needs auth
reapx fediverse - Mastodon posts and instance timelines dev.reapx/mastodon-fediverse · 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-19, 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.