MCP Klever Vm

MCP server for Klever blockchain smart contract development

MCP Servers TypeScript Grade C Listed MIT
60.3/100
Rank #577 of 1328
Compare MCP Klever Vm

Promising trust profile, but some evidence still deserves review.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade B · 3/5 signals
Last push
2026-05-19 · 112d ago
Recent change
Grade Changed +8

Is MCP Klever Vm safe? MCP Klever Vm scores 60.3/100 (Grade C), ranked #577 of 1328 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 3.1/10; 100% of recent commits are signed; last pushed 2026-05-19. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in MCP Servers

Quick Trust Read

What Would Improve It
Improve maintenance to lift the weakest part of the trust profile.
Recent Changes
2026-09-07
Grade Changed
Trust grade D → C
2026-09-07
Rank Moved
Rank rose 525 spots (#1096 → #571)
2026-09-07
HVTrust Changed
HVTrust up 19.8pts (40.6 → 60.4)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 3.1/10. Tighten the weakest checks to improve public safety evidence.
Refresh maintenance signals The repo was last pushed 112 days ago. Fresh activity helps separate stable projects from stale ones.
21.7
Activity sub-score · out of 100
#313

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 B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-09-08 15:03 UTC · Repo last pushed 112 days ago

Rank Trend

2026-08-11 2026-09-08

Activity & Reach

Stars
31
Forks
4
Last Push
2026-05-19
112 days ago
Commits (4 wk)
0
Downloads (7d)
31
npm
HN mentions (30d)
Open Issues
0
Rank Change
▼6
was #571

Analysis

HVTrust Dimensions vs MCP Servers

60.3 / 100 · 100.0% confidence

MCP Klever Vm MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
16.4 / 25
6.5 above avg 9.9
Identity / Provenance60% listing status · 40% build provenance
18.0 / 18
4.6 above avg 13.4
Transparency50% declared license · 50% OSSF Scorecard
11.1 / 17
0.9 below avg 12.0
Maintenance60% last-push freshness · 40% commit activity
4.5 / 20
7.7 below avg 12.2
AdoptionLog-scaled stars · package downloads
5.6 / 20
1.3 below avg 6.9

Activity Inputs

21.7 / 100
StarsRepository reach
9.0 / 30
FreshnessLast push recency
9.4 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
3.3 / 20

Supply Chain Trust

Package Provenance
Verified
npm attestation
OSSF Scorecard
3.1 / 10
OpenSSF Scorecard · scanned Sep 4, 2026
Signed Commits
100%
of last 100 commits verified
Binary-Artifacts 10
Branch-Protection 2
CI-Tests 10
CII-Best-Practices 0
Code-Review 1
Contributors 3
Dangerous-Workflow 10
Dependency-Update-Tool 0
Fuzzing 0
License 10
Maintained 0
Packaging 10
Pinned-Dependencies 0
SAST 0
Security-Policy 0
Signed-Releases -1
Token-Permissions 0
Vulnerabilities 0

Is MCP Klever Vm safe?

MCP Klever Vm 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 Klever Vm publish package provenance?
Yes. MCP Klever Vm's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.
Does MCP Klever Vm have an OpenSSF Scorecard?
MCP Klever Vm has an OpenSSF Scorecard score of 3.1/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 Klever Vm actively maintained?
Slowing down. Last push was 112 days ago — keep an eye on whether activity resumes.
What license does MCP Klever Vm use?
MCP Klever Vm ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are MCP Klever Vm's commits signed?
100% of the last 100 commits to MCP Klever Vm 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
MCP Klever Vm appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
1 detected
Public provider/service dependencies detected.
Credential signal: API keys or service config markers documented.
Tool / Plugin Surface
high confidence
1 tags
Broad capability areas detected.
  • database
Detailed evidence is not shown in the public view.
Package Provenance Drift
high confidence
Match
Published package metadata matches the tracked repo
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 MCP Klever Vm'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-08-17
Activity Went Stale
No commits for 90 days

Maintain MCP Klever Vm?

For maintainers

HVTrust scores MCP Klever Vm 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
Rank 15HVTrust 2Listed 1Stale 1Scorecard 1Grade 1
2026-09-07
Grade Changed
Trust grade D → C
2026-09-07
Rank Moved
Rank rose 525 spots (#1096 → #571)
2026-09-07
HVTrust Changed
HVTrust up 19.8pts (40.6 → 60.4)
2026-09-06
Rank Moved
Rank dropped 14 spots (#1082 → #1096)
2026-09-05
Rank Moved
Rank dropped 41 spots (#1041 → #1082)
2026-09-04
Rank Moved
Rank dropped 24 spots (#1017 → #1041)
2026-09-03
Rank Moved
Rank dropped 57 spots (#960 → #1017)
2026-09-02
Rank Moved
Rank dropped 54 spots (#906 → #960)
2026-09-01
Rank Moved
Rank dropped 35 spots (#871 → #906)
2026-08-31
Rank Moved
Rank dropped 27 spots (#844 → #871)
2026-08-30
Rank Moved
Rank dropped 36 spots (#808 → #844)
2026-08-29
Rank Moved
Rank dropped 48 spots (#760 → #808)
2026-08-28
Scorecard Added
OSSF Scorecard: 3.1/10
2026-08-28
Rank Moved
Rank rose 54 spots (#814 → #760)
2026-08-28
HVTrust Changed
HVTrust up 4.4pts (36.6 → 41.0)
2026-08-27
Rank Moved
Rank dropped 25 spots (#789 → #814)
2026-08-26
Rank Moved
Rank dropped 103 spots (#686 → #789)
2026-08-17
Activity Went Stale
No commits for 90 days
2026-08-16
Rank Moved
Rank dropped 15 spots (#664 → #679)
2026-08-10
Rank Moved
Rank dropped 29 spots (#633 → #662)
2026-08-08
Newly Listed
First tracked at rank #632

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 60.3 Grade C
Markdown:
[![HVTrust](https://hvtracker.net/badge/mcp-klever-vm.svg)](https://hvtracker.net/agents/mcp-klever-vm)
HTML:
<a href="https://hvtracker.net/agents/mcp-klever-vm"><img src="https://hvtracker.net/badge/mcp-klever-vm.svg" alt="HVTrust"></a>

Other agents in MCP Servers

Data sources
GitHub REST API (repo, commits, stars, forks, license) · npm Registry (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON