io.github.CloudStudioIoT/gear-mcp
Cloud Studio Gear
Is the Cloud Studio Gear MCP server down? It gave no valid answer in the probe of 2026-11-13: crashed on start. One failed probe is not an outage.
Read-only MCP access to Cloud Studio Gear IoT: sites, devices, live values, history and alarms.
crashed on start no valid answer since 2026-11-13 · probed 2026-11-15 · unchanged since 2026-11-13
MCP error -32000: Connection closed Set GEAR_URL to your Gear instance, e.g. GEAR_URL=https://gear.example.com
- Run it
- npx -y @cloudstudioiot/gear-mcp@0.1.0 (stdio, probed in a container with the network off)
- Host
- npmjs.com
- Repository
- https://github.com/CloudStudioIoT/gear-mcp
- Website
- https://cloudstudioiot.com
- Registry
- active, updated 2026-11-12 · registry entry
Compare this server with others.
More servers
Other registry entries on npmjs.com, the ones next to this name; all of them.
- io.github.CloudCorpRecords/wattprice · alive
- io.github.CloudCorpRecords/weatherport · alive
- io.github.CloudCorpRecords/worktrack-port · alive
- io.github.CloudCorpRecords/yelpdata · alive
- io.github.Coalesce-Software-Inc/coalesce-transform · not found
- SAP ABAP MCP io.github.Coaspe/sap-abap-mcp · alive
- io.github.CodeCraftersLLC/local-voice-mcp · alive
- io.github.CodesWhat/portkey-admin-mcp · error
Servers that mention gear.
- Mahonia app.mahonia/mahonia · alive
- Camping Australia au.com.trip-planner/camping-australia · alive
- Entogo power-equipment knowledge & tools ca.entogo/knowledge · alive
- DTMFRAME com.dtmframe/dtmframe · alive
- klengnest com.klengnest/catalogue · alive
- Lowtoxgear Storefront com.lowtoxgear/storefront · alive
- Lowtoxgear Scanner com.lowtoxgear/scanner · alive
- MyBoatGuru Boat Advisor com.myboatguru/boat-advisor · alive
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- The package did not start as an MCP server at its probe on 2026-11-13. One failed probe is not an outage: the board calls a package down when it fails again at its next probe, a week later.
- The process exited on start before it answered initialize. The error output is above.