MCPNews

The Model Context Protocol ecosystem, verified

Current spec 2026-07-28

WiseVision

Confidence: High (0.90)

WiseVision publishes 1 cataloged MCP entry: 1 server and 0 clients.

Robotics and IoT company publishing an open-source ROS 2 and LoRaWAN stack. Its repositories include the ROS 2 MCP server that bridges MCP clients to ROS 2 nodes, topics, services and actions.

Which MCP software does WiseVision publish?

1 cataloged entry is published by WiseVision: 1 MCP server and 0 MCP clients. Each carries its own verification date and sources.

Does WiseVision publish a first-party MCP server?

Not confirmed. No first-party MCP server from WiseVision is verified in this catalog yet.

WiseVision is a robotics and IoT company whose public work is an open-source ROS 2 and LoRaWAN stack: a one-command project bootstrapper, a plugin loader, a LoRaWAN bridge, an InfluxDB-backed recorder, and a dashboard. Its ROS 2 MCP server exposes ROS 2 nodes, topics, services and actions to MCP clients.

The company builds on ROS 2 rather than publishing it; ROS 2 itself is maintained by Open Robotics and the Open Source Robotics Alliance, so WiseVision's MCP server is a community implementation against ROS 2 rather than a first-party server for it.

The organization's declared website, www.wisevision.tech, did not resolve when checked on 2026-09-03. The GitHub organization stands as the verifiable publisher surface.

MCP software published by WiseVision

Name Type Spec status Authority Last verified
ROS 2 MCP Server server Spec Support Unverified Community

How was this verified, and what are the sources?

Verified · method: repo-readme · confidence 0.90 (High).

  1. GitHub organization wise-vision, fetched 2026-09-03 - type Organization, name "WiseVision", bio "Open-source ROS 2 & IoT stack. Connect, analyse, automate.", 29 public repositories including wisevision_core, wisevision_lorawan_bridge and wisevision_dashboard - accessed
  2. Declared website https://www.wisevision.tech did not resolve when checked 2026-09-03 (DNS failure on both the apex and www hosts), so the GitHub organization page is used as the publisher URL - accessed