How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade D reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Full methodology →
Signals refreshed2026-06-06 16:20 UTC·Repo last pushed 132 days ago
Activity & Reach
Stars
8.4k
Forks
851
Last Push
2026-01-25
132 days ago
Commits (4 wk)
0
Downloads (7d)
6,090
pypi
HN mentions (30d)
—
Open Issues
133
Rank Change
NEW
Analysis
HVTrust Dimensions
27.1 / 100 · 67.0% confidence
Safety / IntegrityOSSF, provenance, signatures
3.6 / 25
Identity / ProvenanceListing and build link
10.8 / 18
TransparencyLicense and public checks
8.5 / 17
MaintenanceFreshness and commits
3.2 / 20
AdoptionStars and downloads
14.5 / 20
Activity Inputs
43.9 / 100
StarsRepository reach
23.5 / 30
FreshnessLast push recency
6.7 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
13.6 / 20
Supply Chain Trust
Package Provenance
None
No package attestations found
OSSF Scorecard
—
Not available
Signed Commits
72%
of last 100 commits verified
Is mcp-agent safe?
Public trust evidence for mcp-agent is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.
Does mcp-agent publish package provenance?
No published build provenance is currently detected for mcp-agent. 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-agent have an OpenSSF Scorecard?
No OpenSSF Scorecard data is currently published for mcp-agent. Maintainers can enable the Scorecard GitHub Action to get a public score; without it, automated supply-chain hygiene is harder for outsiders to verify.
Is mcp-agent actively maintained?
Slowing down. Last push was 132 days ago — keep an eye on whether activity resumes.
What license does mcp-agent use?
mcp-agent ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are mcp-agent's commits signed?
72% of the last 100 commits to mcp-agent 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.
Runtime trust
HVTrust currently does not score runtime-trust fields yet. This public view shows a compact runtime snapshot from repo docs and manifests. An experimental ranking preview is available in Score Lab →, and progress is tracked on the roadmap →
MCP Server Support
high confidence
Implemented
mcp-agent appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
4 detected
Public provider/service dependencies detected.
Amazon Bedrock
Anthropic
OpenAI
Redis
Credential signal:
API keys or service config markers documented.
Tool / Plugin Surface
high confidence
Declared
Declared plugin/integration surface detected.
code
database
filesystem
Detailed evidence is not shown in the public view.
Package Provenance Drift
low confidence
Unknown
Package source metadata is missing or inconclusive
Detailed evidence is not shown in the public view.
MCP support live
External deps live
Tool / plugin surface live
Package provenance drift live
Maintain mcp-agent?
HVTrust scores mcp-agent 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.
