Skip to main content
Glama
Blackman99

rackhands

by Blackman99
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Local

Related Servers

Alternatives to rackhands

No user-submitted related servers found.

    Related Servers

    • Redfish MCP Server

      hankerbiao
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables interaction with Redfish-compliant BMC devices for server management, firmware updates, and hardware monitoring through session-based authentication and standardized API endpoints.
      1
      MIT

    • Redfish MCP Server

      carlosedp
      F
      license
      C
      quality
      D
      maintenance
      Enables AI agents and LLMs to control and monitor Redfish-enabled hardware through power operations, system inventory, event logs, health monitoring, sensor readings, and user account management.
      15
      1
      -

    • mcp-redfish

      fredriksknese
      F
      license
      A
      quality
      C
      maintenance
      Enables AI assistants to monitor and control server hardware (power, thermal, storage, firmware, event logs) via Redfish BMC API on Dell iDRAC, HPE iLO, Lenovo XCC, Supermicro BMC, and others.
      17
      3
      -

    • jumpserver-mcp

      pc439527
      A
      license
      A
      quality
      B
      maintenance
      Provides persistent SSH/PTY sessions to a bastion host with asset discovery, permission-gated audited command execution, and batch operations across multiple targets.
      23
      10 npm
      1
      MIT

    • identity-aiops

      AIops-tools
      A
      license
      A
      quality
      A
      maintenance
      Governed SSO/IAM operations for Keycloak and Authentik — login-failure, stale-permission, client-config, and MFA RCA, with unbypassable audit logging (MCP + CLI), budget/runaway guards, dry-run, and undo/rollback.
      29
      MIT

    This server cannot be deployed

    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

    B3.3/5.0

    Scored across 8 tools

    Disambiguation4/5

    Tools cover distinct data categories such as boot, logs, targets, firmware, health, inventory, power, and sensors. Minor overlap exists between get_health/get_sensors and get_inventory/get_firmware_inventory, but descriptions make the boundaries clear enough.

    Naming Consistency5/5

    All names use consistent snake_case with a verb_noun pattern: get_* for reads and list_targets for collection listing. The convention is predictable throughout.

    Tool Count5/5

    Eight tools are well-scoped for a BMC monitoring/inventory server. Each tool covers a distinct resource and there is no obvious redundancy.

    Completeness3/5

    The read-only monitoring and inventory surface is fairly complete, but no tools exist for power control, boot override setting, firmware update, log clearing, or other management actions referenced by the descriptions. This is a notable gap for a BMC management domain.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive

    Resources