---
name: feedback-rhino-connection-check
description: "is_server_available checks the Grasshopper socket server, not Rhino — use get_scene_info or get_layers to verify the Rhino connection instead"
metadata: 
  node_type: memory
  type: feedback
  originSessionId: 63928af6-71fe-4cd0-ac03-4b5401fe375c
  modified: 2026-09-21T23:41:14.343Z
---

`mcp__rhino__is_server_available` checks whether the **Grasshopper** socket server is running (see `rhino_mcp/rhino_mcp/grasshopper_tools.py:280` — `GrasshopperTools.is_server_available`), not the Rhino RhinoScript connection. It returns `False` whenever Grasshopper itself isn't open, even when Rhino (`rhino_mcp_client.py`) is running fine and fully connected.

**Why:** user reported "라이노 연결이 안 된다" (Rhino won't connect) after confirming `rhino_mcp_client.py` was on; `is_server_available` returned `False` but `get_scene_info` succeeded immediately after — the tool name is misleading (sounds like a general Rhino MCP check) but is Grasshopper-specific.

**How to apply:** to verify the Rhino connection (not Grasshopper), call `get_scene_info` or `get_layers` directly instead of `is_server_available`. Only use `is_server_available` when actually checking Grasshopper's server.