io.github.runyourempire/4da-mcp-server
4da-server
Is the io.github.runyourempire/4da-mcp-server MCP server down? Yes. It has given no valid answer since 2026-10-20: not found.
Dependency intelligence for AI agents. CVE scanning, health checks, upgrade planning.
not found down since 2026-10-20 · probed 2026-11-14 · unchanged since 2026-10-27
command not found: node
- Run it
- npx -y @4da/mcp-server@4.6.0 (stdio, probed in a container with the network off)
- Host
- npmjs.com
- Reports itself as
- 4da-server 4.6.0
- Capabilities
- resources, tools
- Repository
- https://github.com/runyourempire/4DA
- Registry
- deprecated, updated 2026-10-03 · registry entry
Compare this server with others.
More servers
Other registry entries on npmjs.com, the ones next to this name; all of them.
- Runhooks io.github.runhooks/runhooks-mcp · alive
- figlens io.github.runkids/figlens · needs network
- Agent Wormhole io.github.runningoffcode/wormhole-x402 · alive
- io.github.runsec-io/mcp · alive
- io.github.rushi053/privacypage-mcp · alive
- io.github.ruslanlap/pagespeed-insights-mcp · alive
- io.github.ruvnet/claude-flow · crashed on start
- io.github.ruvnet/flow-nexus · timeout
Servers that mention intelligence or dependency.
- Agentic News ai.agentic-news/mcp · needs auth
- ai.agentberg/agentberg · alive
- ai.astrofabric/mcp · not MCP
- ai.bassethound/bassethound · needs auth
- Bezal — Local Business Intelligence for AI Agents ai.bezal/local-commerce · alive
- BidDeed MCP ai.biddeed/biddeed-mcp · needs auth
- China Marketing AI Intelligence MCP ai.chinamarketing/intelligence · needs auth
- CreativeScope — Mobile Game Ad Creative Intelligence ai.creativescope/creative-intelligence · 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.