OpenSTAAD MCP Server
openstaad-mcp is an MCP Server enabling AI Agents to interact with STAAD.Pro
Is OpenSTAAD MCP Server safe? Promising trust profile, but some evidence still deserves review.
Compare OpenSTAAD MCP Server
How does it stack up against its MCP Servers neighbours?
Pick any agent to compare →In detail: OpenSTAAD MCP Server scores 55.3/100 (Grade C), ranked #768 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.7/10; 96% of recent commits are signed; last pushed 2026-09-25. Every point is earned from checkable signals — never paid placement. How scoring works →
How OpenSTAAD MCP Server compares in MCP Servers
- #423 Wc26 MCP 55.5 +0.2
- #424 MCP Neo4j 55.4 +0.1
- #425 OpenSTAAD MCP Server 55.3 this agent
- #426 Localstack MCP Server 55.3 ±0
- #427 Gemini Cloud Assist MCP 55.3 ±0
Bars show each HVTrust score; the tick marks OpenSTAAD MCP Server’s 55.3.
Where the 55.3 comes from
HVTrust dimensions vs the MCP Servers average
55.3 / 100 · 100.0% confidenceOpenSTAAD MCP Server MCP Servers average (775 agents)
Quick Trust Read
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 →
Rank Trend
Activity & Reach
Analysis
Activity Inputs
49.0 / 100Supply Chain Trust
Common questions about OpenSTAAD MCP Server
Does OpenSTAAD MCP Server publish package provenance?
Does OpenSTAAD MCP Server have an OpenSSF Scorecard?
Is OpenSTAAD MCP Server actively maintained?
What license does OpenSTAAD MCP Server use?
Are OpenSTAAD MCP Server's commits signed?
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
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 signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
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.
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.
Reputation Timeline
Signal history
Embed Badge Badge guide for maintainers →
For maintainers
[](https://hvtracker.net/agents/openstaad-mcp-server)
<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
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