Skip to main content
Glama
yaniswav

TopicForge

by yaniswav
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to TopicForge

No user-submitted related servers found.

    Related Servers

    • ros2-inspector

      XuChen-AI
      A
      license
      A
      quality
      B
      maintenance
      A read-only MCP server that enables LLMs to inspect and analyze ROS 2 systems through natural language, covering nodes, topics, parameters, actions, rates, QoS, and environment health. It can run without ROS 2 installed and safely surfaces runtime system state for diagnosis.
      13
      1
      MIT

    • AgentInspect MCP Server

      rajudandigam
      A
      license
      Not graded
      quality
      A
      maintenance
      Read-only local MCP server for inspecting AgentInspect TypeScript AI-agent traces. Lists runs, exposes bounded causal-failure and TraceFacts evidence, evaluates TraceContract checks, compares runs, and creates share-checked evidence without mutating traces or invoking agent tools.
      15,969 npm
      233
      MIT

    • ros2_perception_mcp

      vagotec
      A
      license
      Not graded
      quality
      C
      maintenance
      A read-only MCP server for bounded semantic inspection of ROS 2 perception systems, enabling discovery and metadata extraction from sensors such as cameras, depth sensors, and LiDARs without device configuration or actuation.
      Apache 2.0

    • Forgeline

      codenikhildr
      A
      license
      A
      quality
      D
      maintenance
      Read-only Modbus TCP monitoring server that exposes safe MCP tools for AI agents to read holding/input registers, coils, and device identity from industrial devices without write access.
      4
      Apache 2.0

    • autopsy-mcp

      th0r10293847
      A
      license
      Not graded
      quality
      C
      maintenance
      Read-only MCP server that exposes Autopsy digital forensics case data as tools, enabling LLM clients like Cline to browse filesystems, query artifacts, and search keywords without modifying the case.
      1
      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

    A4.4/5.0

    Scored across 12 tools

    Disambiguation4/5

    The three sampling tools (peek_dds_samples, sample_messages, peek_bag_samples) share the same SampleResult shape and verb, but each description explicitly states its source (raw DDS layer, ros2 CLI, offline bag) and cross-references the others. list_endpoints vs list_topics and peek_dds_samples on DCPSPublication vs list_endpoints also overlap slightly, but the descriptions resolve these with explicit 'use X instead' guidance.

    Naming Consistency4/5

    All names are snake_case, which is consistent, and most are verb_noun (list_endpoints, list_topics, get_topic_info, sample_messages, analyze_bag, detect_qos_mismatches). A few are noun_noun (topic_metrics, participant_events, health_check), a minor deviation that stays readable and predictable.

    Tool Count5/5

    12 tools is well within the ideal 3-15 range and each covers a distinct facet of DDS/ROS 2 introspection (discovery, sampling, bags, QoS, metrics, health). No tool looks redundant or filler.

    Completeness4/5

    The surface covers the topic-centric lifecycle well: participants and events, endpoints and QoS, ROS 2 topic listing/info, sampling from three sources, bag peek/analysis, metrics, and health. Gaps are minor for a topics-focused server (no ROS 2 node/service/action introspection, no time-window history queries beyond events), and read-only is a stated design choice rather than a missing operation.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources