MCP Klever Vm
MCP server for Klever blockchain smart contract development
Is MCP Klever Vm safe? Promising trust profile, but some evidence still deserves review.
Compare MCP Klever Vm
How does it stack up against its MCP Servers neighbours?
Pick any agent to compare →In detail: MCP Klever Vm scores 59.1/100 (Grade C), ranked #657 of 1325 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 →
How MCP Klever Vm compares in MCP Servers
- #364 Drawio MCP 59.2 +0.1
- #365 Google Surf MCP 59.2 +0.1
- #366 MCP Klever Vm 59.1 this agent
- #367 JS Reverse MCP 58.9 −0.2
- #368 E Arveldaja MCP 58.9 −0.2
Bars show each HVTrust score; the tick marks MCP Klever Vm’s 59.1.
Where the 59.1 comes from
HVTrust dimensions vs the MCP Servers average
59.1 / 100 · 100.0% confidenceMCP Klever Vm 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 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 →
Rank Trend
Activity & Reach
Analysis
Activity Inputs
19.7 / 100Supply Chain Trust
Common questions about MCP Klever Vm
Does MCP Klever Vm publish package provenance?
Does MCP Klever Vm have an OpenSSF Scorecard?
Is MCP Klever Vm actively maintained?
What license does MCP Klever Vm use?
Are MCP Klever Vm'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 →
- database
- MCP signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
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.
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
Embed Badge Badge guide for maintainers →
For maintainers
[](https://hvtracker.net/agents/mcp-klever-vm)
<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
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