updated 2026-11-10 04:07 UTC

MCP Klever Vm

Repository

MCP server for Klever blockchain smart contract development

MCP Servers TypeScript Listed MIT

Is MCP Klever Vm safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 3.1 / 10
Provenance Attested
Signed commits 100%
Last push 175d ago
Advisories None known
Compare MCP Klever Vm

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →
Suggest a correction

In detail: MCP Klever Vm scores 56.7/100 (Grade C), ranked #799 of 1374 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; no published advisory affects its latest release (@klever/mcp-server); last pushed 2026-05-19. Every point is earned from checkable signals — never paid placement. How scoring works →

How MCP Klever Vm could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Already done? Suggest a correctionAdd the trust badge

Chain of custody

Scanners check what the code says. This traces who ships MCP Klever Vm and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

  1. Source Signed

    github.com/klever-io/mcp-klever-vm, MIT, last pushed 2026-05-19. 100% of the last 100 commits carry a verified signature, so changes trace to a verified account.

  2. Review and release Weak

    OpenSSF Scorecard rates the repository's practices 3.1/10 (scanned Nov 7, 2026). The checks that decide who can get a change released:

    • Code Review1
    • Branch Protection2
    • Signed Releasesn/a
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies0
    All 18 Scorecard checks
    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

  3. Published packages Linked and attested

  4. What you install today No known advisories

    Latest release checked: @klever/mcp-server 1.3.0. No published advisory affects it (OSV, checked 2026-11-10).

Changes to this chain

  • 2026-09-23 Package provenance attestation detected
  • 2026-08-28 OSSF Scorecard: 3.1/10

Evidence behind this score

Coverage B: 3 of 5 independent evidence types found.

  • GitHub repository data
  • Package downloads
  • Supply-chain checks
  • Public actions (missing)
  • Community mentions (missing)

Verify this score yourself

Every build re-issues MCP Klever Vm’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

Signed credential (JSON) How to verify

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.

How MCP Klever Vm compares in MCP Servers

  1. #434 MediaWiki 56.8 +0.1
  2. #435 MCP Abap Adt 56.8 +0.1
  3. #436 MCP Klever Vm 56.7 this agent
  4. #437 Cesium MCP 56.7 ±0
  5. #438 SAS MCP Server 56.6 −0.1

Bars show each HVTrust score; the tick marks MCP Klever Vm’s 56.7.

Where the 56.7 comes from

HVTrust dimensions vs the MCP Servers average

56.7 / 100 · 100.0% confidence

MCP Klever Vm MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
16.4 / 25
5.6 above avg 10.8
Identity / Provenance60% listing status · 40% build provenance
18.0 / 18
4.3 above avg 13.7
Transparency50% declared license · 50% OSSF Scorecard
11.1 / 17
1.2 below avg 12.3
Maintenance60% last-push freshness · 40% commit activity
0.3 / 20
11.9 below avg 12.2
AdoptionLog-scaled stars · package downloads
6.2 / 20
1.4 below avg 7.6

Quick Trust Read

What Would Improve It
Improve maintenance to lift the weakest part of the trust profile.
Recent Changes
2026-11-07
Rank Moved
Rank rose 26 spots (#814 → #788)
2026-10-12
Rank Moved
Rank dropped 11 spots (#713 → #724)
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 175 days ago. Fresh activity helps separate stable projects from stale ones.
Compare with another agent
View MCP Servers Report missing data
13.4
Activity sub-score · out of 100
#436
In MCP Servers

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-11-10 04:07 UTC · Repo last pushed 175 days ago

Rank Trend

2026-09-29 2026-11-10

Activity & Reach

Stars
31
Forks
5
Last Push
2026-05-19
175 days ago
Commits (4 wk)
0
Downloads (7d)
91
npm
HN mentions (30d)
—
Open Issues
0
Rank Change
▼1
was #798

Analysis

Activity Inputs

13.4 / 100
StarsRepository reach
9.0 / 30
FreshnessLast push recency
0.7 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
3.6 / 20

Common questions about MCP Klever Vm

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 175 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-09-23
Provider Added
Runtime surface grew — new detected provider dependency: Redis
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Provenance Added
Package provenance attestation detected
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.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history
Rank 19HVTrust 3Grade 2Stale 1Scorecard 1Delisted 1Listed 1Provenance 1MCP 1Surface 1
2026-11-07
Rank Moved
Rank rose 26 spots (#814 → #788)
2026-10-12
Rank Moved
Rank dropped 11 spots (#713 → #724)
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependency: Redis
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Provenance Added
Package provenance attestation detected
2026-09-23
Grade Changed
Trust grade D → C
2026-09-23
Rank Moved
Rank rose 592 spots (#1239 → #647)
2026-09-23
HVTrust Changed
HVTrust up 43.0pts (16.3 → 59.3)
2026-09-22
Newly Listed
First tracked at rank #1239
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-20
Rank Moved
Rank dropped 10 spots (#624 → #634)
2026-09-11
Rank Moved
Rank dropped 17 spots (#585 → #602)
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)
GitHub → npm: @klever/mcp-server

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 56.7 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.4 · Raw JSON