OpenROAD MCP

Model Context Protocol (MCP) server for OpenROAD

MCP Servers TypeScript Listed BSD-3-Clause

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

OSSF Scorecard 5.3 / 10
Provenance None
Signed commits 70%
Last push 3d ago
Compare OpenROAD MCP
Suggest a correction

In detail: OpenROAD MCP scores 55.1/100 (Grade C), ranked #781 of 1325 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 5.3/10; 70% of recent commits are signed; last pushed 2026-09-23. Every point is earned from checkable signals — never paid placement. How scoring works →

How OpenROAD MCP compares in MCP Servers

  1. #432 Zotero MCP (kujenga) 55.2 +0.1
  2. #433 FAOSTAT MCP 55.2 +0.1
  3. #434 OpenROAD MCP 55.1 this agent
  4. #435 MCP NixOS 55.0 −0.1
  5. #436 Miro 54.9 −0.2

Bars show each HVTrust score; the tick marks OpenROAD MCP’s 55.1.

Where the 55.1 comes from

HVTrust dimensions vs the MCP Servers average

55.1 / 100 · 100.0% confidence

OpenROAD MCP MCP Servers average (775 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
10.1 / 25
in line with avg 10.3
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.6 below avg 13.4
Transparency50% declared license · 50% OSSF Scorecard
13.0 / 17
0.8 above avg 12.2
Maintenance60% last-push freshness · 40% commit activity
16.0 / 20
3.9 above avg 12.1
AdoptionLog-scaled stars · package downloads
3.2 / 20
4.0 below avg 7.2

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-09-25
Rank Moved
Rank dropped 17 spots (#769 → #786)
2026-09-24
Mcp Status Changed
Detected MCP server support changed: declared → implemented
2026-09-24
Rank Moved
Rank rose 66 spots (#835 → #769)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 5.3/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.
50.7
Activity sub-score · out of 100
#434

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-09-26 06:32 UTC · Repo last pushed 3 days ago

Rank Trend

2026-08-11 2026-09-26

Activity & Reach

Stars
21
Forks
11
Last Push
2026-09-23
3 days ago
Commits (4 wk)
10
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
1
Rank Change
▲5
was #786

Analysis

Activity Inputs

50.7 / 100
StarsRepository reach
8.1 / 30
FreshnessLast push recency
24.6 / 25
ActivityRecent commits
13.0 / 25
CommunityFork signal
5.0 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
5.3 / 10
OpenSSF Scorecard · scanned Sep 26, 2026
Signed Commits
70%
of last 100 commits verified
Binary-Artifacts 10
Branch-Protection 8
CI-Tests 10
CII-Best-Practices 0
Code-Review 9
Contributors 3
Dangerous-Workflow 0
Dependency-Update-Tool 10
Fuzzing 0
License 10
Maintained 10
Packaging 10
Pinned-Dependencies 5
SAST 0
Security-Policy 4
Signed-Releases 0
Token-Permissions 0
Vulnerabilities 7

Common questions about OpenROAD MCP

OpenROAD 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 OpenROAD MCP publish package provenance?
No published build provenance is currently detected for OpenROAD 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 OpenROAD MCP have an OpenSSF Scorecard?
OpenROAD MCP has an OpenSSF Scorecard score of 5.3/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 OpenROAD MCP actively maintained?
Actively maintained. The repository was pushed to within the last 3 day(s).
What license does OpenROAD MCP use?
OpenROAD MCP ships under BSD-3-Clause. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are OpenROAD MCP's commits signed?
70% of the last 100 commits to OpenROAD 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
high confidence
Implemented
OpenROAD 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 OpenROAD 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-24
Mcp Status Changed
Detected MCP server support changed: declared → implemented
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → declared
2026-09-03
Provider Removed
Runtime surface shrank — no longer detected: Google Gemini

Maintain OpenROAD MCP?

For maintainers

HVTrust scores OpenROAD 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.

Reputation Timeline

Signal history
Rank 21Listed 2HVTrust 2Grade 2MCP 2Scorecard 1Surface 1Delisted 1
2026-09-25
Rank Moved
Rank dropped 17 spots (#769 → #786)
2026-09-24
Mcp Status Changed
Detected MCP server support changed: declared → implemented
2026-09-24
Rank Moved
Rank rose 66 spots (#835 → #769)
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → declared
2026-09-23
Grade Changed
Trust grade D → C
2026-09-23
Rank Moved
Rank dropped 345 spots (#490 → #835)
2026-09-23
HVTrust Changed
HVTrust up 11.9pts (41.5 → 53.4)
2026-09-22
Newly Listed
First tracked at rank #490
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-19
Rank Moved
Rank dropped 23 spots (#742 → #765)
2026-09-15
Rank Moved
Rank rose 16 spots (#749 → #733)
2026-09-14
Rank Moved
Rank rose 12 spots (#761 → #749)
2026-09-11
Rank Moved
Rank dropped 16 spots (#748 → #764)
2026-09-10
Rank Moved
Rank dropped 43 spots (#705 → #748)
2026-09-07
Rank Moved
Rank dropped 41 spots (#652 → #693)
2026-09-05
Rank Moved
Rank dropped 83 spots (#560 → #643)
2026-09-04
Rank Moved
Rank dropped 13 spots (#547 → #560)
2026-09-03
Provider Removed
Runtime surface shrank — no longer detected: Google Gemini
2026-09-02
Rank Moved
Rank dropped 13 spots (#531 → #544)
2026-08-31
Rank Moved
Rank dropped 33 spots (#494 → #527)
2026-08-30
Rank Moved
Rank rose 11 spots (#505 → #494)
2026-08-29
Rank Moved
Rank dropped 31 spots (#474 → #505)
2026-08-28
Rank Moved
Rank dropped 12 spots (#462 → #474)
2026-08-27
Rank Moved
Rank dropped 14 spots (#448 → #462)
2026-08-26
Scorecard Added
OSSF Scorecard: 5.4/10
2026-08-26
Grade Changed
Trust grade D → C
2026-08-26
Rank Moved
Rank rose 458 spots (#906 → #448)
2026-08-26
HVTrust Changed
HVTrust up 32.7pts (23.4 → 56.1)
2026-08-20
Rank Moved
Rank rose 10 spots (#913 → #903)
2026-08-16
Rank Moved
Rank dropped 21 spots (#895 → #916)
2026-08-10
Rank Moved
Rank dropped 52 spots (#852 → #904)
2026-08-08
Newly Listed
First tracked at rank #847

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 55.1 Grade C
Markdown:
[![HVTrust](https://hvtracker.net/badge/openroad-mcp.svg)](https://hvtracker.net/agents/openroad-mcp)
HTML:
<a href="https://hvtracker.net/agents/openroad-mcp"><img src="https://hvtracker.net/badge/openroad-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.3 · Raw JSON