updated 2026-10-16 16:07 UTC

OpenSTAAD MCP Server

Repository

openstaad-mcp is an MCP Server enabling AI Agents to interact with STAAD.Pro

MCP Servers Python Listed MIT

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

OSSF Scorecard 6.0 / 10
Provenance None
Signed commits 96%
Last push 9d ago
Compare OpenSTAAD MCP Server

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →
Suggest a correction

In detail: OpenSTAAD MCP Server scores 57.3/100 (Grade C), ranked #755 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 6.0/10; 96% of recent commits are signed; last pushed 2026-10-07. Every point is earned from checkable signals — never paid placement. How scoring works →

How OpenSTAAD MCP Server 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 OpenSTAAD MCP Server 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 Signed

    github.com/BentleySystems/openstaad-mcp, MIT, last pushed 2026-10-07. 96% of the last 100 commits carry a verified signature, so changes trace to a verified account.

  2. Review and release Mixed

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

    • Code Review9
    • Branch Protection6
    • Signed Releases0
    • Dangerous Workflow10
    • Token Permissions9
    • Pinned Dependencies0
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 6
    CI-Tests 10
    CII-Best-Practices 0
    Code-Review 9
    Contributors 6
    Dangerous-Workflow 10
    Dependency-Update-Tool 0
    Fuzzing 0
    License 10
    Maintained 7
    Packaging -1
    Pinned-Dependencies 0
    SAST 0
    Security-Policy 10
    Signed-Releases 0
    Token-Permissions 9
    Vulnerabilities 10

  3. Published packages None

    No registry package. OpenSTAAD MCP Server 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-09 OSSF Scorecard: 5.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 OpenSTAAD MCP Server’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 OpenSTAAD MCP Server compares in MCP Servers

  1. #406 Tradingview MCP 57.4 +0.1
  2. #407 OrangePro 57.4 +0.1
  3. #408 OpenSTAAD MCP Server 57.3 this agent
  4. #409 Gemini Cloud Assist MCP 57.3 ±0
  5. #410 OpenResearch MCP 57.3 ±0

Bars show each HVTrust score; the tick marks OpenSTAAD MCP Server’s 57.3.

Where the 57.3 comes from

HVTrust dimensions vs the MCP Servers average

57.3 / 100 · 100.0% confidence

OpenSTAAD MCP Server MCP Servers average (781 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
12.3 / 25
1.8 above 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
13.6 / 17
1.3 above avg 12.3
Maintenance60% last-push freshness · 40% commit activity
14.5 / 20
2.2 above avg 12.3
AdoptionLog-scaled stars · package downloads
4.1 / 20
3.3 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-16
Rank Moved
Rank rose 55 spots (#810 → #755)
2026-10-15
Rank Moved
Rank dropped 13 spots (#797 → #810)
2026-10-01
Rank Moved
Rank rose 12 spots (#759 → #747)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 6.0/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 OpenSTAAD MCP Server View MCP Servers Report missing data
49.2
Activity sub-score · out of 100
#408
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 9 days ago

Rank Trend

2026-09-29 2026-10-16

Activity & Reach

Stars
52
Forks
13
Last Push
2026-10-07
9 days ago
Commits (4 wk)
5
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
2
Rank Change
▲55
was #810

Analysis

Activity Inputs

49.2 / 100
StarsRepository reach
10.3 / 30
FreshnessLast push recency
23.8 / 25
ActivityRecent commits
9.7 / 25
CommunityFork signal
5.3 / 20

Common questions about OpenSTAAD MCP Server

OpenSTAAD 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 OpenSTAAD MCP Server publish package provenance?
No published build provenance is currently detected for OpenSTAAD MCP Server. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does OpenSTAAD MCP Server have an OpenSSF Scorecard?
OpenSTAAD MCP Server has an OpenSSF Scorecard score of 6.0/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 OpenSTAAD MCP Server actively maintained?
Maintained. Last push was 9 days ago.
What license does OpenSTAAD MCP Server use?
OpenSTAAD MCP Server ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are OpenSTAAD MCP Server's commits signed?
96% of the last 100 commits to OpenSTAAD 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
OpenSTAAD 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
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 OpenSTAAD MCP Server'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
2026-08-12
Tool Surface Changed
Detected tool/plugin surface changed: extension-based → none

Maintain OpenSTAAD MCP Server?

For maintainers

HVTrust scores OpenSTAAD 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
Rank 27Listed 2HVTrust 2Grade 2Surface 1Scorecard 1Delisted 1MCP 1
2026-10-16
Rank Moved
Rank rose 55 spots (#810 → #755)
2026-10-15
Rank Moved
Rank dropped 13 spots (#797 → #810)
2026-10-01
Rank Moved
Rank rose 12 spots (#759 → #747)
2026-09-30
Rank Moved
Rank rose 12 spots (#771 → #759)
2026-09-25
Rank Moved
Rank rose 18 spots (#785 → #767)
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 276 spots (#507 → #783)
2026-09-23
HVTrust Changed
HVTrust up 14.4pts (40.5 → 54.9)
2026-09-22
Newly Listed
First tracked at rank #507
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-18
Rank Moved
Rank dropped 14 spots (#779 → #793)
2026-09-17
Rank Moved
Rank dropped 11 spots (#768 → #779)
2026-09-10
Rank Moved
Rank rose 12 spots (#770 → #758)
2026-09-09
Scorecard Added
OSSF Scorecard: 5.7/10
2026-09-09
Grade Changed
Trust grade D → C
2026-09-09
Rank Moved
Rank rose 542 spots (#1312 → #770)
2026-09-09
HVTrust Changed
HVTrust up 32.3pts (22.5 → 54.8)
2026-09-05
Rank Moved
Rank dropped 13 spots (#1282 → #1295)
2026-09-03
Rank Moved
Rank dropped 28 spots (#1245 → #1273)
2026-09-02
Rank Moved
Rank dropped 28 spots (#1217 → #1245)
2026-09-01
Rank Moved
Rank dropped 29 spots (#1188 → #1217)
2026-08-31
Rank Moved
Rank dropped 32 spots (#1156 → #1188)
2026-08-30
Rank Moved
Rank dropped 40 spots (#1116 → #1156)
2026-08-29
Rank Moved
Rank dropped 31 spots (#1085 → #1116)
2026-08-28
Rank Moved
Rank dropped 33 spots (#1052 → #1085)
2026-08-27
Rank Moved
Rank dropped 16 spots (#1036 → #1052)
2026-08-26
Rank Moved
Rank dropped 81 spots (#955 → #1036)
2026-08-19
Rank Moved
Rank rose 10 spots (#967 → #957)
2026-08-18
Rank Moved
Rank rose 17 spots (#984 → #967)
2026-08-17
Rank Moved
Rank rose 18 spots (#1002 → #984)
2026-08-16
Rank Moved
Rank dropped 30 spots (#972 → #1002)
2026-08-13
Rank Moved
Rank dropped 13 spots (#962 → #975)
2026-08-12
Tool Surface Changed
Detected tool/plugin surface changed: extension-based → none
2026-08-12
Rank Moved
Rank rose 69 spots (#1031 → #962)
2026-08-10
Rank Moved
Rank dropped 59 spots (#971 → #1030)
2026-08-08
Newly Listed
First tracked at rank #930
GitHub →

Embed Badge Badge guide for maintainers →

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