io.github.klever-io/mcp-klever-vm
NPM · @KLEVER/MCP-SERVER · 2 COMPONENTS · SCANNED SEP 20
MCP server for Klever blockchain smart contract development.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 34 of 115 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to klever-io/mcp-klever-vm). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 184 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability84
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 3188 tokens (~132/item across 24 items; 23 tools + 1 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
- Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety92
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 2 of 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "query_sc" implies "execute" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Partial
- An AI judge read all 24 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.klever-io/mcp-klever-vm server?
io.github.klever-io/mcp-klever-vm runs locally as an npm package, launched with npx -y @klever/mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @klever/mcp-server
claude mcp add klever-io-mcp-klever-vm -- npx -y @klever/mcp-server
{
"mcpServers": {
"klever-io-mcp-klever-vm": {
"command": "npx",
"args": [
"-y",
"@klever/mcp-server"
]
}
}
} {
"servers": {
"klever-io-mcp-klever-vm": {
"command": "npx",
"args": [
"-y",
"@klever/mcp-server"
]
}
}
} codex mcp add klever-io-mcp-klever-vm -- npx -y @klever/mcp-server
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"klever-io-mcp-klever-vm": {
"type": "local",
"command": [
"npx",
"-y",
"@klever/mcp-server"
],
"enabled": true
}
}
} openclaw mcp add klever-io-mcp-klever-vm --command npx --arg -y --arg @klever/mcp-server
mcp_servers:
klever-io-mcp-klever-vm:
command: "npx"
args: ["-y", "@klever/mcp-server"] {
"McpServers": {
"klever-io-mcp-klever-vm": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@klever/mcp-server"
]
}
}
} assistant mcp add klever-io-mcp-klever-vm -t stdio -c npx -a -y @klever/mcp-server
{
"mcpServers": {
"klever-io-mcp-klever-vm": {
"command": "npx",
"args": [
"-y",
"@klever/mcp-server"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 −2
- Stability: pass → 0.80 functional
- 16 Sept 26 0
- Stability: 0.97 → pass security
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 −3
- Stability: pass → 0.77 functional
- 8 Sept 26 0
- Stability: 0.97 → pass security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed npm/@klever/mcp-server@1.3.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | klever-io/mcp-klever-vm |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/klever-io/mcp-klever-vm/.github/workflows/release.yml@refs/tags/v1.3.0 |
| Rekor log index | 1139183777 |
| Predicate type | https://slsa.dev/provenance/v1 |
| Subject digest | sha512:e42304aabf25cd56abf7fc9caa3c63e5238916bdb250b652a0fed00c1ea65f31b05039687ca3165159a9d3b76a3d3a92d5fc2713320b7d585e4982f03 |
Background: How many MCP packages publish verified provenance →
Dependencies 115 packages
| Packages resolved | 115 |
|---|---|
| Stale | 34 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
add_context ~169
Add a new knowledge entry to the Klever VM context store. Use this to save code examples, best practices, security tips, or documentation that can later be retrieved via query_context or search_documentation. Returns the generated ID of the new entry.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | The main content body — typically Rust source code, a CLI command, or a detailed explanation. For code, include the full working snippet. |
| metadata | object | yes | Entry metadata including title, tags, and categorization. At minimum, provide a title. |
| type | string | yes | The category of this knowledge entry. Choose the most specific type: "code_example" for Rust snippets, "best_practice" for recommended patterns, "security_tip" for vulnerability guidance, "error_patt… |
No output schema declared.
No examples provided.
add_helper_scripts ~101
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 from the project root directory (where Cargo.toml is located).
| Name | Type | Req | Description |
|---|---|---|---|
| contractName | string | – | The contract name to embed in scripts (e.g. "my-token"). If omitted, auto-detected from the `name` field in Cargo.toml. |
No output schema declared.
No examples provided.
analyze_contract ~136
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 usage, storage mappers without #[storage_mapper], and missing event definitions. Returns findings with severity (error/warning/info) and links to relevant knowledge base entries.
| Name | Type | Req | Description |
|---|---|---|---|
| contractName | string | – | Human-readable name for the contract (used in output labeling). Defaults to "contract" if omitted. |
| sourceCode | string | yes | The full Rust source code of the Klever smart contract to analyze. Must be valid Rust code using klever_sc imports. |
No output schema declared.
No examples provided.
check_sdk_status ~78
Check whether the Klever SDK is installed and report the status of each component. Returns JSON with installation state and versions for: ksc (smart contract compiler), koperator (blockchain CLI), VM library (libvmexeccapi), and wallet key file. Run this before init_klever_project or install_klever_sdk to verify prerequisites.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
deploy_sc ~185
Build an unsigned smart contract deployment transaction for the Klever blockchain. Provide either wasmPath (preferred — reads the file server-side) or wasmHex. Returns the unsigned transaction for client-side signing. The MCP server NEVER handles private keys.
| Name | Type | Req | Description |
|---|---|---|---|
| initArgs | array | – | Optional base64-encoded init arguments for the contract constructor. |
| network | string | – | Network to use. Options: "mainnet", "testnet", "devnet", "local". Defaults to server default (mainnet). |
| sender | string | yes | Deployer address (klv1... bech32 format). |
| wasmHex | string | – | Smart contract WASM bytecode as a hex-encoded string. Use wasmPath instead for large contracts. |
| wasmPath | string | – | Absolute path to the compiled WASM file (preferred over wasmHex to avoid loading large binaries into AI context). |
No output schema declared.
No examples provided.
enhance_with_context ~132
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 examples and documentation in markdown. Use this to enrich a user prompt before answering Klever development questions.
| Name | Type | Req | Description |
|---|---|---|---|
| autoInclude | boolean | – | When true (default), automatically appends the most relevant knowledge base entries to the response. Set to false to only return metadata without injecting context. |
| query | string | yes | The user's natural-language question or prompt to enhance (e.g. "How do I handle KLV payments in my contract?"). |
No output schema declared.
No examples provided.
find_similar ~105
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 documentation after finding one relevant entry.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The context ID to find similar entries for. Obtain from query_context or get_context results. |
| limit | integer | – | Maximum number of similar entries to return. Typical range is 1-20; higher values may be slower. Default: 5. |
No output schema declared.
No examples provided.
freeze_klv ~133
Build an unsigned Freeze KLV transaction on the Klever blockchain. Freezing KLV provides energy/bandwidth for network operations and enables staking rewards. Returns the unsigned transaction for client-side signing.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | integer | yes | Amount of KLV to freeze in the smallest unit (1 KLV = 1,000,000 units). |
| network | string | – | Network to use. Options: "mainnet", "testnet", "devnet", "local". Defaults to server default (mainnet). |
| sender | string | yes | Address to freeze from (klv1... bech32 format). |
No output schema declared.
No examples provided.
get_account ~98
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 balance.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Klever address (klv1... bech32 format). |
| network | string | – | Network to query. Options: "mainnet", "testnet", "devnet", "local". Defaults to server default (mainnet). |
No output schema declared.
No examples provided.
get_asset_info ~149
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, and metadata. Note: string fields like ID, Name, Ticker are base64-encoded in the raw response.
| Name | Type | Req | Description |
|---|---|---|---|
| assetId | string | yes | Asset identifier (e.g. "KLV", "KFI", "USDT-A1B2", "MYNFT-XY78"). |
| network | string | – | Network to query. Options: "mainnet", "testnet", "devnet", "local". Defaults to server default (mainnet). |
No output schema declared.
No examples provided.
get_balance ~170
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 query a specific KDA token balance instead of KLV.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Klever address (klv1... bech32 format). |
| assetId | string | – | Optional KDA token ID (e.g. "USDT-A1B2", "LPKLVKFI-3I0N"). Omit for KLV balance. |
| network | string | – | Network to query. Options: "mainnet", "testnet", "devnet", "local". Defaults to server default (mainnet). |
No output schema declared.
No examples provided.
get_block ~103
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 metadata.
| Name | Type | Req | Description |
|---|---|---|---|
| network | string | – | Network to query. Options: "mainnet", "testnet", "devnet", "local". Defaults to server default (mainnet). |
| nonce | integer | – | Block number (nonce). Omit to get the latest block. |
No output schema declared.
No examples provided.
get_context ~78
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 details for a specific entry.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique context ID (UUID format). Obtain IDs from query_context or find_similar results. |
No output schema declared.
No examples provided.
get_knowledge_stats ~64
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 each type. Useful for understanding what knowledge is available before querying.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_transaction ~89
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.
| Name | Type | Req | Description |
|---|---|---|---|
| hash | string | yes | Transaction hash (hex string). |
| network | string | – | Network to query. Options: "mainnet", "testnet", "devnet", "local". Defaults to server default (mainnet). |
No output schema declared.
No examples provided.
init_klever_project ~178
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 Klever SDK installed at ~/klever-sdk/. Run check_sdk_status first to verify.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | The contract project name in kebab-case (e.g. "my-token", "nft-marketplace"). Used as the Cargo package name and directory name. |
| noMove | boolean | – | When true, keeps the project in the SDK output directory instead of moving it to the current working directory. Default: false. |
| template | string | – | Project template to scaffold from. "empty" creates a blank contract with just an init function. "adder" creates a simple counter example. Default: "empty". |
No output schema declared.
No examples provided.
install_klever_sdk ~119
Download and install Klever SDK tools to ~/klever-sdk/. Fetches the latest versions from the Klever CDN, installs binaries, and downloads required VM library dependencies. Supports macOS (arm64/amd64) and Linux. Run check_sdk_status first to see what is already installed.
| Name | Type | Req | Description |
|---|---|---|---|
| tool | string | – | Which SDK component to install. "ksc" = smart contract compiler only, "koperator" = blockchain operator CLI + VM library, "all" = both ksc and koperator. Default: "all". |
No output schema declared.
No examples provided.
invoke_sc ~191
Build an unsigned smart contract invocation transaction on the Klever blockchain. Calls a state-changing endpoint on a deployed contract. Returns the unsigned transaction for client-side signing. For read-only calls, use query_sc instead.
| Name | Type | Req | Description |
|---|---|---|---|
| args | array | – | Optional base64-encoded arguments. |
| callValue | object | – | Optional token amounts to send with the call, as a map of token ID to amount (e.g. {"KLV": 1000000}). Required for payable endpoints. |
| funcName | string | yes | Endpoint function name to invoke. |
| network | string | – | Network to use. Options: "mainnet", "testnet", "devnet", "local". Defaults to server default (mainnet). |
| scAddress | string | yes | Smart contract address (klv1... bech32 format). |
| sender | string | yes | Caller address (klv1... bech32 format). |
No output schema declared.
No examples provided.
list_validators ~70
List active validators on the Klever blockchain network. Returns validator addresses, names, commission rates, delegation info, and staking amounts.
| Name | Type | Req | Description |
|---|---|---|---|
| network | string | – | Network to query. Options: "mainnet", "testnet", "devnet", "local". Defaults to server default (mainnet). |
No output schema declared.
No examples provided.
query_context ~281
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 search_documentation for human-readable "how do I..." answers.
| Name | Type | Req | Description |
|---|---|---|---|
| contractType | string | – | Filter by contract type (e.g. "token", "nft", "defi", "dao"). Only returns entries tagged for this contract category. |
| limit | integer | – | Maximum number of results to return (1-100). Default: 10. |
| offset | integer | – | Number of results to skip for pagination. Use with limit to page through results. Default: 0. |
| query | string | – | Free-text search query. Use Klever-specific terms for best results (e.g. "storage mapper SingleValueMapper", "payable endpoint KLV", "deploy contract testnet"). |
| tags | array | – | Filter by tags (e.g. ["storage", "mapper"], ["tokens", "KLV"], ["events"]). Tags are matched with OR logic — any matching tag includes the entry. |
| types | array | – | Filter results by context type. Omit to search all types. Common combinations: ["code_example", "documentation"] for learning, ["error_pattern"] for debugging, ["security_tip", "best_practice"] for r… |
No output schema declared.
No examples provided.
query_sc ~204
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 contract state without modifying it.
| Name | Type | Req | Description |
|---|---|---|---|
| args | array | – | Optional base64-encoded arguments. For addresses, encode the hex-decoded bech32 bytes. For numbers, use big-endian byte encoding. |
| caller | string | – | Optional caller address (klv1... bech32 format). Some view functions use the caller to look up address-keyed storage mappers. |
| funcName | string | yes | Function name to call (must be a #[view] function on the contract). |
| network | string | – | Network to query. Options: "mainnet", "testnet", "devnet", "local". Defaults to server default (mainnet). |
| scAddress | string | yes | Smart contract address (klv1... bech32 format). |
No output schema declared.
No examples provided.
search_documentation ~132
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_context when you need formatted developer documentation.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Narrow results to a specific knowledge category. Available: core, storage, events, tokens, modules, tools, scripts, examples, errors, best-practices, documentation. |
| query | string | yes | Search query in natural language (e.g. "how to use storage mappers", "deploy contract to testnet", "handle KDA token transfers"). |
No output schema declared.
No examples provided.
send_transfer ~204
Build an unsigned KLV or KDA token transfer transaction on the Klever blockchain. Returns the unsigned transaction data and hash for client-side signing. The MCP server NEVER handles private keys — signing must be done externally.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | integer | yes | Amount in the smallest unit. For KLV: 1 KLV = 1,000,000 units (6 decimals). Example: to send 10 KLV, use 10000000. |
| assetId | string | – | Optional KDA token ID for non-KLV transfers (e.g. "USDT-A1B2"). Omit for KLV. |
| network | string | – | Network to use. Options: "mainnet", "testnet", "devnet", "local". Defaults to server default (mainnet). |
| receiver | string | yes | Receiver address (klv1... bech32 format). |
| sender | string | yes | Sender address (klv1... bech32 format). |
No output schema declared.
No examples provided.
What is the io.github.klever-io/mcp-klever-vm server?
io.github.klever-io/mcp-klever-vm is listed in the public MCP registry as io.github.klever-io/mcp-klever-vm. MCP server for Klever blockchain smart contract development. This page covers its npm package (@klever/mcp-server).
Is the io.github.klever-io/mcp-klever-vm server safe to use?
io.github.klever-io/mcp-klever-vm scores 94 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.klever-io/mcp-klever-vm server expose?
io.github.klever-io/mcp-klever-vm exposes 23 tools: query_context, get_context, find_similar, get_knowledge_stats, enhance_with_context, and 18 more. Their descriptions and schemas cost roughly 3,169 tokens of context every time the server is loaded.
Is the io.github.klever-io/mcp-klever-vm server still maintained?
io.github.klever-io/mcp-klever-vm is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.klever-io/mcp-klever-vm server under?
io.github.klever-io/mcp-klever-vm declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.