io.github.wise-vision/mcp_server_ros_2

Is the io.github.wise-vision/mcp_server_ros_2 MCP server down? It gave no valid answer in the probe of 2026-11-11: crashed on start. One failed probe is not an outage.

View ROS 2 nodes and topics, and call services and actions via MCP

crashed on start no valid answer since 2026-11-11 · probed 2026-11-14 · unchanged since 2026-11-11

MCP error -32000: Connection closed
  ├─▶ client error (Connect)
  ├─▶ dns error
  ╰─▶ failed to lookup address information: Temporary failure in name
      res

Run it: docker run -i --rm docker.io/mcp/ros2:latest (stdio, probed in a container with the network off)
Host: docker.io
Repository: https://github.com/wise-vision/mcp_server_ros_2
Registry: active, updated 2025-11-26 · registry entry

Compare this server with others.

More servers

Other registry entries on docker.io, the ones next to this name; all of them.

io.github.tuananh/hyper-mcp · crashed on start
TypeDB io.github.typedb/typedb-mcp · not probed
Inkwell io.github.veronchenko/inkwell-memory · crashed on start
io.github.vipulsutar11/mst-mcp · alive
SAP SuccessFactors io.github.wudaoyou/successfactors-toolkit · crashed on start
YouTrack (ymcp) io.github.xlsft/ymcp · needs env
io.github.zenml-io/mcp-zenml · crashed on start
Ailimu net.ailimu/ailimu · not probed

Servers that mention vision.

Contabo (VPS) MCP Server ai.com.mcp/contabo · alive
ai.inflowpay.app/inflow · needs auth
ai.oddsockets/remote-mcp · alive
ai.primateintelligence/mcp · needs auth
Reka ai.reka/mcp · alive
ai.syntheticbrew/syntheticbrew · needs auth
ai.roc/mcp · timeout
Contendeo app.contendeo/contendeo · needs auth

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.

Atom feed

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-11. 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.