Sato Hub
MCP

Klever MCP

Official MCP server for the Klever blockchain — smart contract development, account/asset queries, and transaction analysis.

  • Sato Score76
ActiveUnverifiedQuiet · 5mo ago

Klever MCP is an open-source MCP server, with last code activity on 2026-05-19 (Quiet). Latest release on 2026-03-19. Sato Score 76/100 (how open, active and verifiable it is, not a safety grade), as of 2026-10-21. How the score works →

See how to install Klever MCP →

Last commit May 19, 2026 · Last release Mar 19, 2026 · ★ 31

Listed from klever.org on 2026-07-19. Install: reproduced by Sato Hub on 2026-09-21. Evidence →

Next step

Watch Klever MCP

One email if what we observe changes — its repo goes quiet or disappears, or the listing is retired. Nothing else.

Check it from your agent

Add Sato Hub’s MCP server (no key), then ask:

https://satohub.ai/api/mcp
Run Sato Hub Preflight on klever-io/mcp-klever-vm before I use it.
Full setup: Claude Code, Cursor, others →

Your project?

Prove you control the domain and correct this page — description, links, tags, chains. A claim proves control, not verification: it never changes the Sato Score.

Claim this listing →

Overview

Klever's official MCP server gives coding agents tools to write and deploy Klever VM smart contracts, query accounts and assets, and inspect transactions directly from an MCP-aware client. Maintained by Klever (klever-io), with 32 GitHub stars and commits as recent as May 2026.

Sato Score

76/100· High

How open, active & verifiable — not a safety or returns grade.

Maintenance & liveness
35/35
Code transparency
18/20
Interface verifiability
10/10
Docs & demo
0/10
Listing transparency & provenance
10/15
Independent verification
3/10

Deploy path reproduced — install verified in an isolated container (proves installability, not runtime safety).

Sato Check

v1.3.0 · as of 2026-10-02
Does it take your key?
No key read found
Does your key leave?
Not observed
Can it move funds on its own?
None found
Full profile, evidence and limits →

A profile describes what we read and ran, with dates. It is not a safety rating, an audit or an endorsement, and "not found" is not "not there".

Evidence — listed vs checked · what the words mean

Listed from klever.org on 2026-07-19. Install: reproduced by Sato Hub on 2026-09-21.

ClaimValueEvidenceSourceChecked
Chains supportednot statedself-reportedklever.orgas of 2026-10-21
Verification statusUnverified — not independently reviewedself-reportedklever.orgas of 2026-10-21
Recent activitylast release 2026-03-19 · last commit 2026-05-19observedgithub.com/klever-io/mcp-klever-vm2026-10-21
Install worksreproduced — install and entry both completedshows the install path works as written; not a statement about runtime behaviour✓ reproducedraw.githubusercontent.com2026-09-21
MCP endpoint answersanswered — 16 tools listedobservedmcp.klever.org2026-10-21
Daily check record90 of 90 daily checks since 2026-07-23 succeededa success rate of our checks, not uptime; the source is this listing's own historyobserved—2026-10-20
Takes your keyno private-key read found in what we readtracedsatohub.ai2026-10-02
Key leaves the machinenot observed during install and start-uplater or triggered code paths are not coveredobservedsatohub.ai2026-10-02
Moves funds on its ownno action that signs or sends funds foundtracedsatohub.ai2026-10-02
Deploys asnpm package, Docker, self-hosted, hosted serviceconfidence 0.85self-reportedgithub.com/klever-io/mcp-klever-vmas of 2026-08-03
Works withClaude Code, Claude Desktop, Cursor, VS Code (GitHub Copilot)confidence 0.85self-reportedgithub.com/klever-io/mcp-klever-vmas of 2026-08-03
Sato Score76/100 (High)how open, active and verifiable — not a safety or quality gradecomputedsatohub.ai2026-10-21

Self-reported rows are the project’s own words, dated when we recorded them — not a check. Only reproduced and reviewed rows carry a mark. None of these rows is a safety or quality rating.

Install — reproduced in a container Sep 21, 2026

Runtime: Node.js (npm package) or self-hosted via pnpm

npx -y @klever/mcp-server
{"mcpServers": {"klever-vm": {"command": "npx", "args": ["-y", "@klever/mcp-server"]}}}

MCP invocation: npx -y @klever/mcp-server (stdio); hosted alternative: claude mcp add -t http klever-vm https://mcp.klever.org/mcp

Read from the project’s own docs as of 2026-09-21. What a deploy spec is →

Tool inventory — 16 tools, probed live 2026-10-21

  • query_context — Search the Klever VM knowledge base for smart contract development context. Returns structured JSON with matching entries, scores, and pagination. Use this for precise filtering by type or tags; use s
  • get_context — Retrieve a single knowledge base entry by its unique ID. Returns the full entry including content, metadata, tags, and related context IDs. Use this after query_context or find_similar to get complete
  • find_similar — Find knowledge base entries similar to a given entry by comparing tags and content. Returns related contexts ranked by similarity score. Useful for discovering related patterns, examples, or documenta
  • get_knowledge_stats — Get summary statistics of the Klever VM knowledge base. Returns total entry count, counts broken down by context type (code_example, best_practice, security_tip, etc.), and a sample entry title for ea
  • enhance_with_context — Augment a natural-language query with relevant Klever VM knowledge base context. Extracts Klever-specific keywords, finds matching entries, and returns the original query combined with relevant code e
  • search_documentation — Search Klever VM documentation and knowledge base. Returns human-readable markdown with titles, descriptions, and code snippets. Optimized for "how do I..." questions. Use this instead of query_contex
  • analyze_contract — Analyze Klever smart contract Rust source code for common issues. Checks for missing imports, missing #[klever_sc::contract] macro, missing endpoint annotations, payable handlers without call_value us
  • get_balance — Get the KLV or KDA token balance for a Klever blockchain address. Returns the balance in the smallest unit (for KLV: 1 KLV = 1,000,000 units with 6 decimal places). Optionally specify an asset ID to q
  • get_account — Get full account details for a Klever blockchain address including nonce, balance, frozen balance, allowance, and permissions. Use this when you need comprehensive account state beyond just the balanc
  • get_asset_info — Get complete properties and configuration for any asset on the Klever blockchain (KLV, KFI, KDA tokens, NFT collections). Returns supply info, permissions (CanMint, CanBurn, etc.), roles, precision, a
  • query_sc — Execute a read-only query against a Klever smart contract (VM view call). Returns the contract function result as base64-encoded return data. Arguments must be base64-encoded. Use this to read contrac
  • get_transaction — Get transaction details by hash from the Klever blockchain. Returns sender, receiver, status, block info, contracts, and receipts. Uses the API proxy for indexed data.
  • get_block — Get block information from the Klever blockchain by nonce (block number). If no nonce is provided, returns the latest block. Returns hash, timestamp, proposer, number of transactions, and other block
  • list_validators — List active validators on the Klever blockchain network. Returns validator addresses, names, commission rates, delegation info, and staking amounts.
  • init_klever_project — Scaffold a new Klever smart contract project using the SDK. Creates the Rust project structure via `ksc new` and generates automation scripts (build, deploy, upgrade, query, test, interact). Requires
  • add_helper_scripts — Add build, deploy, upgrade, query, test, and interact automation scripts to an existing Klever smart contract project. Creates a scripts/ directory with bash scripts and updates .gitignore. Run this f
Answers a handshake
yes · 2026-10-21
Answers a call
yes — get_knowledge_stats returned in 140 ms

Live probe verifies the interface responds — not what the tools do, their safety, or their output quality. The call is one read-only tool named by this server's own list (list_/get_/search_, no mutating verb anywhere in the name, no required arguments and none that look like a key, an address or an amount), asked once a day with no arguments. Not asked is not a failure.

Observed record — 91 daily checks since 2026-07-23

100%of 91 checks since 2026-07-23 succeeded
Currently responding for 91 days
Succeeded
91
Failed
0
Their error
0
Unattributed
0

This is the share of our daily checks that succeeded — not an availability guarantee. A check can fail because the host was down, because our runner timed out, or because the network in between dropped it, and only the first of those is a fact about this project. Failures are split by what we can attribute; anything we cannot attribute is counted, not hidden. 40 of these checks predate 2026-09-01, when the probe counted a bot-block (HTTP 403) as a failure and recorded no reason for any failure. Every one of them passed, so the rate covers them too.

Last 30 days — to 2026-10-21, one point per UTC day

Share of OUR checks that succeeded
100%
7-day rolling; unattributable days are gaps · 30/30 days
Tools listed
16
from the server's own tools/list · 29/30 days
Sato Score
76
as snapshotted that day · 29/30 days

A gap is a day we have no attributable observation — never a zero. Thirty points is the whole shape the free layer carries; the daily rows behind it stay in the snapshot series.

Details

Chains
Unknown
Agent types
MCP server
Open source
Yes
Deploys as
npm package, Docker, self-hosted, hosted service
Works with
Claude Code, Claude Desktop, Cursor, VS Code (GitHub Copilot)
Last checked
2026-10-21

Marketplace Signals

No marketplace signals recorded for this resource yet.

Verification status reflects evidence reviewed by Sato Hub. Self-reported claims are never presented as verified.

#mcp#smart-contracts#klever#developer-tool
See something inaccurate or outdated?Submit a correction →

Listing History

Recorded changes to Klever MCP's listing — status, verification, Sato Score, and recent releases. Full history is kept in the listing record.

  1. Sep 21, 2026
    Verified: deploy spec
  2. Aug 3, 2026
    Auto-enriched: deployment options, supported integrations
  3. Aug 3, 2026
    Sato Score tier: Medium → High
    Score 69 → 73.
  4. Jul 24, 2026
    Sato Hub began tracking this listing
  5. Jul 20, 2026
    Edited: mcp endpoint url
  6. Jul 19, 2026
    Listed on Sato Hub

Compared with

Appears in

Related Resources

Reference

QuestionsShowHide

Questions people ask about Klever MCP

Is Klever MCP open source?
Yes. Klever MCP is open source under the MIT license; the repository is https://github.com/klever-io/mcp-klever-vm. Checked as of 2026-10-21.
Which chains does Klever MCP support?
Sato Hub has no confirmed chain list for Klever MCP as of 2026-10-21; treat chain support as unknown.
Is Klever MCP still maintained?
The most recent code activity Sato Hub observed was on 2026-05-19 (last commit 2026-05-19, last release 2026-03-19), which Sato Hub labels "Quiet". Posts on X are not counted as maintenance. Activity is a recency signal, not a quality judgment.
How do I install or run Klever MCP?
Node.js (npm package) or self-hosted via pnpm. Install: npx -y @klever/mcp-server. Entry: {"mcpServers": {"klever-vm": {"command": "npx", "args": ["-y", "@klever/mcp-server"]}}}. Sato Hub reproduced this install in a container on 2026-09-21. It runs as an MCP server (npx -y @klever/mcp-server (stdio); hosted alternative: claude mcp add -t http klever-vm https://mcp.klever.org/mcp).
Is Klever MCP verified on Sato Hub?
Sato Hub holds one earned check for Klever MCP: Deploy path reproduced — install verified in an isolated container (proves installability, not runtime safety). Its Sato Score is 76 of 100, a measure of how open, active and verifiable the project is, not a safety, quality or returns grade.
Cite this pageShowHide

Cite this page

Sato Hub. "Klever MCP — Sato Hub." Sato Hub, updated 2026-10-21, accessed 2026-10-21. https://satohub.ai/resources/klever-mcp

Data last refreshed 2026-10-21; this page is rebuilt daily. Citations carry the date so a reader can tell which snapshot a claim came from. Catalog data is licensed CC-BY-4.0.

Join the Sato Hub Briefing

Sign up for the Briefing: the agents, tools, and infrastructure that actually shipped, and why they matter.