Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/hieutachi/rosbridge-mcpWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/hieutachi/rosbridge-mcp/rosbridge)<a href="https://agentmods.dev/mcp/hieutachi/rosbridge-mcp/rosbridge"><img src="https://agentmods.dev/badge/mcp/hieutachi/rosbridge-mcp/rosbridge/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/hieutachi/rosbridge-mcp/rosbridge"><img src="https://agentmods.dev/badge/mcp/hieutachi/rosbridge-mcp/rosbridge.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
rosbridge scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 10d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"rosbridge": {
"command": "rosbridge-mcp",
"env": {
"ROSBRIDGE_URL": "ws://192.168.1.42:9090",
"ROSBRIDGE_MCP_READONLY": "true"
}
}
}What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 10d ago First seen · 9 lines scan A 771e65d7fd5c
rosbridge is an MCP server published in the GitHub repository hieutachi/rosbridge-mcp (2 stars, last pushed 23d ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other mcp servers, from other repositories
ros2-workspace-mcp
MCP server "ros2-workspace-mcp" as configured in doer0312/ros2-workspace-mcp. Runs locally from the ros2-workspace-mcp Python package.
operandi
MCP server — let any LLM agent identify an appliance and pull its grounded, safety-checked, robot-executable operation package from OPERANDI. Runs locally from the operandi-mcp Python package. Needs 2 environment variables to run.
ros-mcp-server
Connect AI Language Models with Robots on ROS using MCP. Runs locally from the ros-mcp Python package.
bagel
MCP server "bagel", hosted remotely at localhost, as configured in Extelligence-ai/bagel.
agenticros
MCP server "agenticros" as configured in agenticros/agenticros. Launched with sh -c node packages/agenticros-claude-code/dist/index.js 2>>/tmp/agenticros-mcp.. Needs 1 environment variable to run.
ninjaone-mcp
MCP server "ninjaone-mcp" as configured in WYRE-AI/ninjaone-mcp. Runs in Docker (ghcr.io/wyre-ai/ninjaone-mcp:v2.3.0). Needs 6 environment variables to run.