Skip to main content
Glama
Isotel

idm-mcp

by Isotel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to idm-mcp

No user-submitted related servers found.

    Related Servers

    • mcp-rport

      LuisQueo
      A
      license
      A
      quality
      C
      maintenance
      Enables MCP clients to manage a self-hosted RPort fleet by listing and inspecting connected devices, opening and closing SSH tunnels, and executing commands through RPort agents.
      10
      MIT
    • PocketShell MCP by PocketShell-io

      PocketShell MCPofficial

      PocketShell-io
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables remote MCP clients to perform host, file, process, and DataOps operations through a persistent gateway without locally storing CLI logins, SSH keys, or host pins, using standard Streamable HTTP and OAuth.
      MIT

    • Technitium DNS MCP

      X1pheR
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables managing and observing Technitium DNS Server through MCP, including read-only or read-write tool surfaces, scoped bearer authentication, audit logging, and confirmation gates for destructive operations.
      MIT
    • @nexalware/mcp by nexalware

      @nexalware/mcpofficial

      nexalware
      A
      license
      A
      quality
      A
      maintenance
      Enables MCP-aware hosts to discover and call tools for listing authorized devices, sending commands, reading telemetry, managing sub-devices, and creating, updating, or deleting device schedules through the API.
      17
      17 npm
      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

    B3.4/5.0

    Scored across 14 tools

    Disambiguation4/5

    Most tools target distinct resources (devices, connections, streams, activity, history), and the parameter-reading family (list_parameters, get_parameters, get_value, get_structure) is differentiated by descriptions. However, the four parameter tools plus the topology trio (get_protocols, get_streams, list_connections) require careful reading to avoid misselection.

    Naming Consistency4/5

    All tools share the idm_ prefix and follow a mostly consistent verb_noun pattern (list_devices, get_parameters, read_stream, get_history). Minor deviations: idm_gateway_info and idm_device_status are noun-only, and get vs read both appear but are used sensibly.

    Tool Count5/5

    14 tools is well-scoped for a gateway/device management server, covering topology, parameters, streams, and history without obvious redundancy. Each tool earns its place.

    Completeness3/5

    The read surface is thorough (info, devices, connections, streams, parameters, history), but the descriptions reference write tools and idm_open_stream that are not present in the tool list, implying missing write capability. The surface is read-only despite describing a read/write parameter workflow.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources