Rust MCP Sdk
Pragmatic AI Labs MCP SDK
Is Rust MCP Sdk safe? Promising trust profile, but some evidence still deserves review.
Compare Rust MCP Sdk
How does it stack up against its MCP Servers neighbours?
Pick any agent to compare →In detail: Rust MCP Sdk scores 57.7/100 (Grade C), ranked #695 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 4.9/10; 100% of recent commits are signed; last pushed 2026-09-24. Every point is earned from checkable signals — never paid placement. How scoring works →
How Rust MCP Sdk compares in MCP Servers
- #383 MCP File Tools 57.8 +0.1
- #384 MCP For Stata 57.8 +0.1
- #385 Rust MCP Sdk 57.7 this agent
- #386 RPG Maker MV Ultimate MCP 57.7 ±0
- #387 Local Memory 57.6 −0.1
Bars show each HVTrust score; the tick marks Rust MCP Sdk’s 57.7.
Where the 57.7 comes from
HVTrust dimensions vs the MCP Servers average
57.7 / 100 · 100.0% confidenceRust MCP Sdk 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
55.4 / 100Supply Chain Trust
Common questions about Rust MCP Sdk
Does Rust MCP Sdk publish package provenance?
Does Rust MCP Sdk have an OpenSSF Scorecard?
Is Rust MCP Sdk actively maintained?
What license does Rust MCP Sdk use?
Are Rust MCP Sdk'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 Rust MCP Sdk'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 Rust MCP Sdk?
For maintainers
HVTrust scores Rust MCP Sdk 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/rust-mcp-sdk)
<a href="https://hvtracker.net/agents/rust-mcp-sdk"><img src="https://hvtracker.net/badge/rust-mcp-sdk.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