How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade B reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Full methodology →
Signals refreshed2026-06-22 00:01 UTC·Repo last pushed 2 days ago
Rank Trend
2026-06-202026-06-21
Activity & Reach
Stars
23.4k
Forks
3.6k
Last Push
2026-06-20
2 days ago
Commits (4 wk)
56
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
563
Rank Change
=
was #80
Analysis
HVTrust Dimensions
70.1 / 100 · 100.0% confidence
Safety / IntegrityOSSF, provenance, signatures
14.8 / 25
Identity / ProvenanceListing and build link
10.8 / 18
TransparencyLicense and public checks
15.1 / 17
MaintenanceFreshness and commits
18.9 / 20
AdoptionStars and downloads
10.5 / 20
Activity Inputs
89.6 / 100
StarsRepository reach
26.2 / 30
FreshnessLast push recency
24.7 / 25
ActivityRecent commits
21.9 / 25
CommunityFork signal
16.5 / 20
Supply Chain Trust
Package Provenance
None
No package attestations found
OSSF Scorecard
7.8 / 10
OpenSSF Scorecard · scanned Jun 21, 2026
Signed Commits
100%
of last 100 commits verified
Binary-Artifacts10
Branch-Protection2
CI-Tests10
CII-Best-Practices0
Code-Review10
Contributors10
Dangerous-Workflow10
Dependency-Update-Tool10
Fuzzing0
License10
Maintained10
Packaging10
Pinned-Dependencies10
SAST10
Security-Policy10
Signed-Releases-1
Token-Permissions9
Vulnerabilities0
Is MCP Python SDK safe?
MCP Python SDK 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 MCP Python SDK publish package provenance?
No published build provenance is currently detected for MCP Python SDK. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does MCP Python SDK have an OpenSSF Scorecard?
MCP Python SDK has an OpenSSF Scorecard score of 7.8/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 MCP Python SDK actively maintained?
Actively maintained. The repository was pushed to within the last 2 day(s).
What license does MCP Python SDK use?
MCP Python SDK ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are MCP Python SDK's commits signed?
100% of the last 100 commits to MCP Python SDK 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
Profile context only
HVTrust currently ranks supply-chain and project-integrity trust only. This public view shows a compact AI-agent surface snapshot from repo docs and manifests. These fields are descriptive context and do not affect the production HVTrust rank. An experimental local preview remains available in Score Lab →, and the policy boundary is tracked on the roadmap →
MCP Server Support
high confidence
Implemented
MCP Python SDK appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
2 detected
Public provider/service dependencies detected.
Anthropic
Postgres
Credential signal:
No explicit API-key/config marker detected.
Tool / Plugin Surface
high confidence
Declared
Declared plugin/integration surface detected.
code
database
search
shell
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
Maintain MCP Python SDK?
HVTrust scores MCP Python 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.
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 v3.2 · Raw JSON
