Skip to main content
Glama
RedPitayaCore-MCP

RedPitayaCore-MCP

by theerayutbo

Related Servers

Alternatives to RedPitayaCore-MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables local, offline-first MCP access to OKX read-only market data and account operations plus fictional-data demo preflight, while all trading writes are rejected.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP clients to observe and inspect Sierra Chart chartbooks, charts, studies, drawings, and data, read diagnostics, and apply validated configuration changes via a local bridge, without any order execution or trading features.
      1
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables MCP clients on macOS to perform bounded read-only filesystem operations and a narrow allowlist of process diagnostics over STDIO or authenticated loopback Streamable HTTP. It excludes file writes, arbitrary shell access, GUI/browser automation, and remote relay.
      10
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Read-only MCP server for diagnosing H7-TOOL hardware via Modbus, USB HID, and Lua diagnostics, exposing only safe read operations.
      20
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables investigation of devices, model breaches and analyst incidents from an MCP host through a bounded set of read-only tools, with operator-controlled profiles and a fixed operation inventory. Writes, PCAP export, email and HTTP transport are excluded, and responses are minimized and escaped before entering model context.
      16 npm
      3
      Apache 2.0
    • A
      license
      B
      quality
      B
      maintenance
      Enables read-only diagnosis of QNX 8.0 targets over verified SSH/SFTP, exposing system information, process and IPC state, system logs, and bounded file reads to an MCP client. It helps distinguish idle receivers from real IPC dependency cycles using structured QNX evidence.
      4
      MIT

    TDQS

    A3.5/5.0

    Scored across 9 tools

    Disambiguation4/5

    Most tools are clearly separated by resource and action: diagnostics, connection checks, app lifecycle, and RX lifecycle are distinct. The diagnostics/status cluster (rp_profile, rp_device_diagnostics, rp_system_diagnostics, rp_connection_probe, rp_connection_status) has some conceptual overlap, but the descriptions clarify the boundaries and constraints.

    Naming Consistency4/5

    All tools use a consistent rp_ prefix and snake_case, making the set predictable. The pattern is mostly rp_<domain>_<action>, though several diagnostic tools are noun-like rather than strict verb_noun, which is a minor deviation.

    Tool Count5/5

    Nine tools is well-scoped for a hardware diagnostics and RX-control server. Each tool covers a distinct capability area without an excessive or thin surface.

    Completeness4/5

    The surface covers profile/diagnostics, connection checks, app lifecycle planning, and RX connect/read/disconnect. Minor gaps remain around live lifecycle operation and TX or deeper RX configuration/readback, but the core safe diagnostic and RX workflows are covered.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues