io.github.quwentao2005/ensp-nexus
eNSP Nexus
Is the eNSP Nexus MCP server down? Yes. It has given no valid answer since 2026-10-16: install failed.
MCP server and web terminal for Huawei eNSP network simulation.
install failed down since 2026-10-16 · probed 2026-11-15 · unchanged since 2026-10-30
cause: Because ensp-nexus==0.2.8 has no wheels with a matching platform tag (e.g., `manylinux_2_36_x86_64`) and you require ensp-nexus==0.2.8, we can conclude
- Run it
- uvx ensp-nexus@0.2.8 (stdio, probed in a container with the network off)
- Host
- pypi.org
- Repository
- https://github.com/quwentao2005/mcp_dev
- Registry
- active, updated 2026-08-28 · registry entry
Compare this server with others.
More servers
Other registry entries on pypi.org, the ones next to this name; all of them.
- io.github.qso-graph/solar-mcp · alive
- io.github.qso-graph/sota-mcp · alive
- io.github.qso-graph/wspr-mcp · alive
- Graqle io.github.quantamixsol/graqle · crashed on start
- SSH Nexus io.github.quwentao2005/ssh-nexus · install failed
- io.github.qwe4559999/scopus-mcp · crashed on start
- Market Data (x402) io.github.r0dell/market-data-mcp · alive
- PG Bloat Detective io.github.r69shabh/pg-bloat-detective · alive
Servers that mention nexus.
- BlueNexus Universal MCP ai.bluenexus/universal-mcp · needs auth
- DocNexus ai.docnexus.mcp/docnexus · needs auth
- ai.dragoneye/mcp · needs auth
- Agent Nexus app.agentnexus/agent-nexus · alive
- ZP Nexus br.com.sistemasinovadores/zp-nexus · needs auth
- Avalara AvaTax com.avalara/avatax · needs auth
- Mochii work graph com.chibitek/mochii · needs auth
- Nexus Memory com.chibitek/nexus · 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.
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-16, in every probe since then.
- npx or uvx could not install the package. The package name in the registry entry is wrong, the package is not published, or the install needs a build step.