io.github.meltingpixelsai/drainbrain
io.github.meltingpixelsai/drainbrain
Is the io.github.meltingpixelsai/drainbrain MCP server down? Yes. It has given no valid answer since 2026-10-20: not found.
AI-powered Solana token rug pull detection with ML ensemble scoring and honeypot detection.
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 drainbrain-mcp-server@1.0.2 (stdio, probed in a container with the network off)
- Host
- npmjs.com
- Repository
- https://github.com/meltingpixelsai/rugslayer
- Registry
- deprecated, updated 2026-10-27 · 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.meharajM/whatsapp-mcp · alive
- io.github.mehmetnadir/cdpilot · alive
- Rowsmith test data io.github.meiorz/rowsmith · alive
- API Key Case io.github.melavern/api-key-case · alive
- io.github.meltingpixelsai/harvey-budget · not probed
- io.github.meltingpixelsai/harvey-intel · not probed
- io.github.meltingpixelsai/harvey-tools · not probed
- io.github.meltingpixelsai/harvey-verify · not probed
Servers that mention drainbrain or detection or ensemble.
- io.github.meltingpixelsai/zero-core-intel · not found
- ai.dragoneye/mcp · needs auth
- ai.responsibleailabs/rail-score · no DNS
- Stompy – AI Memory for Claude & MCP Agents ai.stompy/stompy · needs auth
- ai.roc/mcp · timeout
- Walter Writes ai.walterwrites/mcp-server · needs auth
- APICK Vision app.apick/vision · alive
- B20 Check com.b20check/b20check · timeout
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.