Skip to main content
Glama
sohumsuthar

ntopology-mcp

by sohumsuthar
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to ntopology-mcp

No user-submitted related servers found.

    Related Servers

    • solidworks-mcp

      Christancho-co
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables building and modifying parametric solid models in a local SOLIDWORKS installation via the COM API.
      MIT

    • SolidworksMCP

      aryesil
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables control of a live SOLIDWORKS session through the Windows COM API, providing native sketch, feature, body, reference-geometry, view, probe, and export operations, along with transactional CAD plans, parametric sketches, multibody tools, and deterministic raster-to-sketch vectorization pipelines.
      -

    • ansys-agent-bridge

      1622352030
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables headless control of Ansys SpaceClaim, including opening, inspecting, modifying, scripting, and exporting geometry, while guarding operations that falsely report success to ensure geometry actually changed.
      1
      MIT

    • LS-PrePost-MCP

      lwz20210407
      A
      license
      C
      quality
      B
      maintenance
      Enables natural-language automation of LS-PrePost preprocessing and postprocessing by exposing tools that build and verify shell meshes, query nodes, parts and connectivity, run native commands, SCL and in-application Python, and read d3plot/binout results through pluggable backends. Every job runs in its own directory and returns an ID, status, log and artifacts, so results stay traceable and failures are never silently reported as success.
      30
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.7/5.0

    Scored across 14 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: adding literals vs. setting their values, reading the graph vs. inspecting the notebook, validating vs. running, searching blocks vs. finding examples. No two tools appear to do the same thing, so an agent can reliably pick the right one.

    Naming Consistency4/5

    The vast majority of tools follow a consistent verb_noun snake_case pattern (add_literal, search_blocks, set_output). Two exceptions break the pattern: 'mesh_stats' is a noun_noun compound and 'environment' is a bare noun, which slightly reduces predictability but does not cause real confusion.

    Tool Count5/5

    14 tools is well within the sweet spot for a domain-specific server. Each tool addresses a distinct step in the notebook lifecycle—inspection, editing, validation, execution, and analysis—earning its place without bloat or obvious omission.

    Completeness4/5

    The tool surface covers the core workflow: read/inspect/validate, add and modify blocks/literals, rewire inputs, set outputs, run, and check results. Minor gaps exist (e.g., no explicit block deletion, no direct 'save notebook' tool), but existing tools like prune_graph and set_input can work around these without agent failure.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources