updated 2026-10-16 16:07 UTC

Ros2 MCP

Repository Website

ROS2 MCP: the MCP server that lets AI agents see, understand and operate ROS 2 robots. MPL-2.0.

MCP Servers Python Listed MPL-2.0

Is Ros2 MCP safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 4.4 / 10
Provenance None
Signed commits 70%
Last push 2d ago
Compare Ros2 MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →
Suggest a correction

In detail: Ros2 MCP scores 56.0/100 (Grade C), ranked #806 of 1378 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 4.4/10; 70% of recent commits are signed; last pushed 2026-10-14. Every point is earned from checkable signals — never paid placement. How scoring works →

How Ros2 MCP could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Already done? Suggest a correctionAdd the trust badge

Chain of custody

Scanners check what the code says. This traces who ships Ros2 MCP and whether that has changed: from the source repository, through how changes are reviewed and released, to the code you run. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

  1. Source Partly signed

    github.com/wise-vision/ros2_mcp, MPL-2.0, last pushed 2026-10-14. 70% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.

  2. Review and release Mixed

    OpenSSF Scorecard rates the repository's practices 4.4/10 (scanned Oct 15, 2026). The checks that decide who can get a change released:

    • Code Review0
    • Branch Protection0
    • Signed Releasesn/a
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies0
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 0
    CI-Tests 10
    CII-Best-Practices 0
    Code-Review 0
    Contributors 3
    Dangerous-Workflow 10
    Dependency-Update-Tool 0
    Fuzzing 0
    License 10
    Maintained 10
    Packaging 10
    Pinned-Dependencies 0
    SAST 0
    Security-Policy 0
    Signed-Releases -1
    Token-Permissions 0
    Vulnerabilities 9

  3. Published packages None

    No registry package. Ros2 MCP is used from its repository, so what you run is whatever you check out: pin a release tag or commit.

Changes to this chain

  • 2026-09-07 OSSF Scorecard: 3.7/10

Evidence behind this score

Coverage C: 2 of 5 independent evidence types found.

  • GitHub repository data
  • Package downloads (missing)
  • Supply-chain checks
  • Public actions (missing)
  • Community mentions (missing)

Verify this score yourself

Every build re-issues Ros2 MCP’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

Signed credential (JSON) How to verify

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.

How Ros2 MCP compares in MCP Servers

  1. #433 MCP Server Motherduck 56.1 +0.1
  2. #434 Fr24api MCP 56.1 +0.1
  3. #435 Ros2 MCP 56.0 this agent
  4. #436 MCPfinder - MCP Server Discovery 56.0 ±0
  5. #437 Git MCP Server 56.0 ±0

Bars show each HVTrust score; the tick marks Ros2 MCP’s 56.0.

Where the 56.0 comes from

HVTrust dimensions vs the MCP Servers average

56.0 / 100 · 100.0% confidence

Ros2 MCP MCP Servers average (781 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
9.0 / 25
1.5 below avg 10.5
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.7 below avg 13.5
Transparency50% declared license · 50% OSSF Scorecard
12.2 / 17
in line with avg 12.3
Maintenance60% last-push freshness · 40% commit activity
17.3 / 20
5.0 above avg 12.3
AdoptionLog-scaled stars · package downloads
4.7 / 20
2.7 below avg 7.4

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-10-15
Rank Moved
Rank rose 17 spots (#819 → #802)
2026-10-14
Rank Moved
Rank rose 62 spots (#881 → #819)
2026-10-14
Activity Score Changed
Activity score up 6pts (54 → 59)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 4.4/10. Tighten the weakest checks to improve public safety evidence.
Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.
Compare with another agent Get email alerts for Ros2 MCP View MCP Servers Report missing data
59.1
Activity sub-score · out of 100
#435
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 C is separate — it grades how many independent signal types back the score (2 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-10-16 16:07 UTC · Repo last pushed 2 days ago

Rank Trend

2026-09-29 2026-10-16

Activity & Reach

Stars
90
Forks
15
Last Push
2026-10-14
2 days ago
Commits (4 wk)
22
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
3
Rank Change
▼4
was #802

Analysis

Activity Inputs

59.1 / 100
StarsRepository reach
11.8 / 30
FreshnessLast push recency
24.7 / 25
ActivityRecent commits
17.0 / 25
CommunityFork signal
5.6 / 20

Common questions about Ros2 MCP

Ros2 MCP 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 Ros2 MCP publish package provenance?
No published build provenance is currently detected for Ros2 MCP. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Ros2 MCP have an OpenSSF Scorecard?
Ros2 MCP has an OpenSSF Scorecard score of 4.4/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.
Is Ros2 MCP actively maintained?
Actively maintained. The repository was pushed to within the last 2 day(s).
What license does Ros2 MCP use?
Ros2 MCP ships under MPL-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Ros2 MCP's commits signed?
70% of the last 100 commits to Ros2 MCP 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
medium confidence
Implemented
Ros2 MCP 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
N/A
No package source configured
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live
How this surface has changed

Detected changes to Ros2 MCP's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.

2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented

Maintain Ros2 MCP?

For maintainers

HVTrust scores Ros2 MCP 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
Rank 32Listed 2Score 2HVTrust 2Scorecard 1Delisted 1Grade 1MCP 1
2026-10-15
Rank Moved
Rank rose 17 spots (#819 → #802)
2026-10-14
Rank Moved
Rank rose 62 spots (#881 → #819)
2026-10-14
Activity Score Changed
Activity score up 6pts (54 → 59)
2026-10-11
Rank Moved
Rank dropped 10 spots (#863 → #873)
2026-10-02
Rank Moved
Rank dropped 12 spots (#819 → #831)
2026-10-01
Rank Moved
Rank rose 63 spots (#882 → #819)
2026-09-30
Rank Moved
Rank rose 15 spots (#897 → #882)
2026-09-25
Rank Moved
Rank dropped 12 spots (#913 → #925)
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Grade Changed
Trust grade D → C
2026-09-23
Rank Moved
Rank dropped 352 spots (#557 → #909)
2026-09-23
HVTrust Changed
HVTrust up 14.4pts (36.4 → 50.8)
2026-09-22
Newly Listed
First tracked at rank #557
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-20
Rank Moved
Rank rose 62 spots (#995 → #933)
2026-09-15
Rank Moved
Rank dropped 10 spots (#985 → #995)
2026-09-12
Rank Moved
Rank dropped 10 spots (#973 → #983)
2026-09-09
Rank Moved
Rank dropped 14 spots (#949 → #963)
2026-09-08
Rank Moved
Rank dropped 11 spots (#938 → #949)
2026-09-07
Scorecard Added
OSSF Scorecard: 3.7/10
2026-09-07
Rank Moved
Rank rose 365 spots (#1303 → #938)
2026-09-07
HVTrust Changed
HVTrust up 26.9pts (21.4 → 48.3)
2026-09-05
Rank Moved
Rank dropped 10 spots (#1289 → #1299)
2026-09-03
Rank Moved
Rank dropped 23 spots (#1258 → #1281)
2026-09-02
Rank Moved
Rank dropped 27 spots (#1231 → #1258)
2026-09-01
Rank Moved
Rank dropped 26 spots (#1205 → #1231)
2026-08-31
Rank Moved
Rank dropped 25 spots (#1180 → #1205)
2026-08-30
Rank Moved
Rank dropped 32 spots (#1148 → #1180)
2026-08-29
Rank Moved
Rank dropped 32 spots (#1116 → #1148)
2026-08-28
Rank Moved
Rank dropped 25 spots (#1091 → #1116)
2026-08-27
Rank Moved
Rank dropped 18 spots (#1073 → #1091)
2026-08-26
Rank Moved
Rank dropped 79 spots (#994 → #1073)
2026-08-24
Rank Moved
Rank dropped 14 spots (#981 → #995)
2026-08-22
Rank Moved
Rank rose 12 spots (#990 → #978)
2026-08-17
Rank Moved
Rank rose 63 spots (#1042 → #979)
2026-08-16
Rank Moved
Rank dropped 35 spots (#1007 → #1042)
2026-08-15
Rank Moved
Rank dropped 25 spots (#982 → #1007)
2026-08-13
Rank Moved
Rank dropped 10 spots (#972 → #982)
2026-08-12
Rank Moved
Rank dropped 48 spots (#924 → #972)
2026-08-12
Activity Score Changed
Activity score down 8pts (50 → 42)
2026-08-10
Rank Moved
Rank dropped 53 spots (#868 → #921)
2026-08-08
Newly Listed
First tracked at rank #855
GitHub → Website →

Embed Badge Badge guide for maintainers →

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

Other agents in MCP Servers

Data sources
GitHub REST API (repo, commits, stars, forks, license) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON