Livenxmcp

io.github.bdimic-bluecatPublished by GitHub account bdimic-bluecatv0.30.1-test1Updated Oct 27, 2026

MCP server for LiveAction LiveNX (quay.io / MCP registry test publish)

VerifiedSTDIODesktop onlySecurity & Monitoring

Overview

AI-generated overview

A local MCP server for LiveAction LiveNX, described only as a test publish to the MCP registry with no documented tools.

What you can do
  • The listing gives no tool list, instructions or README, so the concrete capabilities are undocumented.
  • The description identifies it as an MCP server for LiveAction LiveNX, a network monitoring and analytics product.
  • It is published as a registry test entry, so it appears to be a packaging or publishing experiment rather than a documented integration.
When to use it
Only worth considering if you specifically want to experiment with connecting an assistant to LiveAction LiveNX and are prepared to inspect the server yourself, since nothing documents what it exposes.
Requirements
Runs as a local process on the user's machine over stdio and is desktop only. No packages, environment variables, headers or authentication are declared, so the actual runtime and any LiveNX connection details are unknown.
Before you install
No tools, credentials or data flows are documented, so you cannot tell what the server reads, changes or sends before installing it. Treat it as an unverified test publish and review the source before running it.

Installation

In SourceWeft

  1. Open Livenxmcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.30.1-test1LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.