updated 2026-08-12 05:02 UTC

Ros MCP Server

robotmcp/ros-mcp-server

Connect AI models like Claude & GPT with robots using MCP and ROS.

MCP Servers Python Grade C Listed Apache-2.0
62.5/100
Rank #285 of 1283
Compare Ros MCP Server

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Promising trust profile, but some evidence still deserves review.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade B · 3/5 signals
Last push
2026-08-11 · 1d ago
Recent change
Rank +1

Is Ros MCP Server safe? Ros MCP Server scores 62.5/100 (Grade C), ranked #285 of 1283 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; no OSSF Scorecard result yet; 82% of recent commits are signed; last pushed 2026-08-11. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in MCP Servers

#92 Automox MCP Server — 62.6 (C) → #93 ZulipChat MCP Server — 62.6 (C) → #95 Companies House MCP — 62.4 (C) → #96 Anki MCP Server — 62.4 (C) →

Quick Trust Read

What Would Improve It
Add or improve OSSF Scorecard coverage so safety checks are easier to verify.
Recent Changes
2026-08-10
Rank Moved
Rank dropped 17 spots (#266 → #283)
2026-08-08
Newly Listed
First tracked at rank #264
Maintainer Checklist
Add Scorecard coverage Expose the repository to OpenSSF Scorecard checks so supply-chain posture is easier to verify.
Compare with another agent Get email alerts for Ros MCP Server View MCP Servers Report missing data
54.6
Activity sub-score · out of 100
#94
In MCP Servers

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade C reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-08-12 05:02 UTC · Repo last pushed yesterday

Rank Trend

2026-08-11 2026-08-12

Activity & Reach

Stars
1.4k
Forks
204
Last Push
2026-08-11
yesterday
Commits (4 wk)
0
Downloads (7d)
165
pypi
HN mentions (30d)
—
Open Issues
22
Rank Change
=
was #285

Analysis

HVTrust Dimensions vs MCP Servers

62.5 / 100 · 100.0% confidence

Ros MCP Server MCP Servers average (761 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
11.6 / 25
6.6 above avg 5.0
Identity / Provenance60% listing status · 40% build provenance
18.0 / 18
4.7 above avg 13.3
Transparency50% declared license · 50% OSSF Scorecard
8.5 / 17
in line with avg 8.8
Maintenance60% last-push freshness · 40% commit activity
11.9 / 20
0.5 below avg 12.4
AdoptionLog-scaled stars · package downloads
10.5 / 20
4.7 above avg 5.8

Activity Inputs

54.6 / 100
StarsRepository reach
18.9 / 30
FreshnessLast push recency
24.9 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
10.7 / 20

Supply Chain Trust

Package Provenance
Verified
pypi attestation
OSSF Scorecard
—
Not available
Signed Commits
82%
of last 100 commits verified

Is Ros MCP Server safe?

Ros MCP Server has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.
Does Ros MCP Server publish package provenance?
Yes. Ros MCP Server's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.
Does Ros MCP Server have an OpenSSF Scorecard?
No OpenSSF Scorecard data is currently published for Ros MCP Server. Maintainers can enable the Scorecard GitHub Action to get a public score; without it, automated supply-chain hygiene is harder for outsiders to verify.
Is Ros MCP Server actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does Ros MCP Server use?
Ros MCP Server ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Ros MCP Server's commits signed?
82% of the last 100 commits to Ros MCP Server are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

AI agent surface

MCP, providers, tool surface
Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support
high confidence
Implemented
Ros MCP Server appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
None detected
No clear third-party provider dependency detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
None detected
No clear plugin system or broad tool surface detected.
Detailed evidence is not shown in the public view.
Package Provenance Drift
low confidence
Unknown
Package source metadata is missing or inconclusive
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live

Maintain Ros MCP Server?

For maintainers

HVTrust scores Ros MCP Server from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history
Listed 1Rank 1
2026-08-10
Rank Moved
Rank dropped 17 spots (#266 → #283)
2026-08-08
Newly Listed
First tracked at rank #264
GitHub → PyPI: ros-mcp

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 62.5 Grade C
Markdown:
[![HVTrust](https://hvtracker.net/badge/ros-mcp-server.svg)](https://hvtracker.net/agents/ros-mcp-server)
HTML:
<a href="https://hvtracker.net/agents/ros-mcp-server"><img src="https://hvtracker.net/badge/ros-mcp-server.svg" alt="HVTrust"></a>

Other agents in MCP Servers

Data sources
GitHub REST API (repo, commits, stars, forks, license) · PyPI / pypistats (downloads, provenance)
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON