com.bluecat/livenxmcp
com.bluecat/livenxmcp
LiveNX Network Observability MCP Server
not probed in the official registry, not probed
- Run it
- docker run -i --rm quay.io/bluecat/livenxmcp@sha256:c8c17c3428b274be20a5f8f159cc636535018dfff87bd27a72d25cdd8f0a61c3 (stdio, probed in a container with the network off)
- Host
- quay.io
- Registry
- active, updated 2026-09-24 · registry entry
Compare this server with others.
More servers
Other registry entries on quay.io.
- com.bluecat/integritymcp · not probed
- com.bluecat/livewiremcp · not probed
- com.bluecat/micetromcp · not probed
Servers that mention observability or network.
- ac.snag/snag · needs auth
- UGC, the Human Ad Network africa.ugc/ugc · needs auth
- 69.ai ai.69ai/69ai · no DNS
- AgentMesh ai.agentmesh/mesh · needs auth
- Agentic Fabrication Network (AFN) ai.agenticfabricationnetwork/ufp · alive
- AnomalyArmor ai.anomalyarmor/armor-mcp · needs auth
- Affiliate Networks MCP ai.agenticaffiliate/affiliate-networks-mcp · needs auth
- Caulo ai.caulo/caulo · 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
- The entry has only an OCI image that serves streamable-http. The probe starts packages that talk over stdio only. The entry is on the board so that the list holds the whole registry and says what it does not check.