takanarishimbo-rosbridge-mcp-server

A Model Context Protocol (MCP) server intended to expose ROS (Robot Operating System) capabilities through tools that connect to a ROS bridge via WebSocket, enabling AI assistants to monitor and publish ROS topics.

Evaluated Apr 04, 2026 (20d ago)
Homepage ↗ Repo ↗ Infrastructure mcp ros rosbridge robotics websocket tooling automation
⚙ Agent Friendliness
39
/ 100
Can an agent use this?
🔒 Security
36
/ 100
Is it safe for agents?
⚡ Reliability
26
/ 100
Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality
45
Documentation
40
Error Messages
0
Auth Simplicity
80
Rate Limits
0

🔒 Security

TLS Enforcement
40
Auth Strength
20
Scope Granularity
20
Dep. Hygiene
60
Secret Handling
50

Security posture cannot be confirmed from the provided manifest/metadata. Likely relies on rosbridge WebSocket connectivity; ensure HTTPS/WSS, firewalling, and authentication/authorization at the proxy/network level. Dependency hygiene appears moderate (roslibpy and mcp), but no CVE/lockfile data is provided here, and no secret-handling or auth details are observable from the supplied content.

⚡ Reliability

Uptime/SLA
0
Version Stability
45
Breaking Changes
35
Error Recovery
25
AF Security Reliability

Best When

You already have rosbridge running and want to integrate ROS topic-level control into an MCP-capable agent environment.

Avoid When

You cannot ensure transport security and strong access control for robot operations; you also lack visibility into the server’s tool schemas and failure modes.

Use Cases

  • Create an AI-assistant “control plane” for ROS systems through MCP tools
  • Publish ROS topics from an LLM-driven workflow via rosbridge WebSocket
  • Bridge robot/ROS telemetry or control actions into agent tool calls

Not For

  • Securing remote robot control over untrusted networks without additional network/auth layers
  • Production deployments requiring clearly documented operational guarantees (SLA, robust error semantics)

Interface

REST API
No
GraphQL
No
gRPC
No
MCP Server
Yes
SDK
No
Webhooks
No

Authentication

OAuth: No Scopes: No

No authentication mechanisms are described in the provided package metadata/manifest snippet. For robot control integrations, assume no built-in auth unless documentation/source confirms otherwise; plan to secure at the network/proxy layer if needed.

Pricing

Free tier: No
Requires CC: No

Open-source Python package; no pricing information in provided data.

Agent Metadata

Pagination
none
Idempotent
False
Retry Guidance
Not documented

Known Gotchas

  • ROS/rosbridge integrations often involve stateful connections; agents may need explicit connect/disconnect handling
  • Topic publishing is usually not inherently idempotent; repeated tool calls can change robot state
  • Without documented MCP tool schemas and error codes, agents may struggle to decide when to retry vs fail

Alternatives

Full Evaluation Report

Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for takanarishimbo-rosbridge-mcp-server.

AI-powered analysis · PDF + markdown · Delivered within 30 minutes

$99

Package Brief

Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.

Delivered within 10 minutes

$3

Score Monitoring

Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.

Continuous monitoring

$3/mo

Scores are editorial opinions as of 2026-04-04.

8642
Packages Evaluated
17761
Need Evaluation
586
Need Re-evaluation
Community Powered