io.github.shreyassaw5394/dea
io.github.shreyassaw5394/dea
Is the io.github.shreyassaw5394/dea MCP server down? Yes. It has given no valid answer since 2026-10-20: not found.
Observe any running process from your agent. strace, py-spy, perf, lsof, tcpdump as evidence.
not found down since 2026-10-20 · probed 2026-11-14 · unchanged since 2026-10-27
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 dea-agents@0.4.0 (stdio, probed in a container with the network off)
- Host
- npmjs.com
- Repository
- https://github.com/shreyassaw5394/dea
- Website
- https://debuganything.dev
- Registry
- active, updated 2026-10-19 · 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.shopanaio/novaposhta · alive
- io.github.shotintoeternity/pocketnook · alive
- Notion Large File Upload io.github.shoubhiksaha/notion-large-file-upload · alive
- io.github.shreyassaw5394/agent-theatre · alive
- io.github.shreyassaw5394/debuganything · alive
- io.github.shreyassaw5394/mockanything · alive
- Basiiik io.github.shubhankarsd/basiiik · alive
- io.github.shubhtoy/github-project-info · alive
Servers that mention evidence or observe.
- ac.snag/snag · needs auth
- Contractor Licence Changes agency.ottobot/contractor-license-changes · alive
- AFMR Discovery ai.afmr/discovery · alive
- AIMentionTracker ai.aimentiontracker/mcp · needs auth
- ai.aqta/seal · alive
- Aviado AI ai.aviado/health · alive
- ai.colaunched/colaunched · needs auth
- ai.colaunched/public · 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-20, 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.