# io.github.klever-io/mcp-klever-vm (remote · mcp.klever.org)

MCP server for Klever blockchain smart contract development.

- Trust score: 77/100 (medium)
- Change this week: +7
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `mcp.klever.org`: 77/100 (this document), [markdown](https://verifymcp.io/servers/klever-io-mcp-klever-vm/mcp.md), [page](https://verifymcp.io/servers/klever-io-mcp-klever-vm/mcp)
- npm · `@klever/mcp-server`: 80/100, [markdown](https://verifymcp.io/servers/klever-io-mcp-klever-vm/klever-mcp-server.md), [page](https://verifymcp.io/servers/klever-io-mcp-klever-vm/klever-mcp-server)

## Channel facts

- Endpoint: `https://mcp.klever.org/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.3.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 79/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 2151 tokens (~126/item across 17 items; 16 tools + 1 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http klever-io-mcp-klever-vm https://mcp.klever.org/mcp
```

### Codex

```toml
[mcp_servers.klever-io-mcp-klever-vm]
url = "https://mcp.klever.org/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "klever-io-mcp-klever-vm": {
      "type": "remote",
      "url": "https://mcp.klever.org/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add klever-io-mcp-klever-vm --url https://mcp.klever.org/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  klever-io-mcp-klever-vm:
    url: "https://mcp.klever.org/mcp"
```

### Other

```json
{
  "mcpServers": {
    "klever-io-mcp-klever-vm": {
      "type": "http",
      "url": "https://mcp.klever.org/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-01 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 75, +3)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 72, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-28 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 70, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 70)

First indexed and scored.

## MCP tools (16)

### `query_context` (~281 tokens)

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.

Input parameters:

- `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…

### `get_context` (~78 tokens)

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.

Input parameters:

- `id` (string, required): The unique context ID (UUID format). Obtain IDs from query_context or find_similar results.

### `find_similar` (~105 tokens)

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.

Input parameters:

- `id` (string, required): 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.

### `get_knowledge_stats` (~64 tokens)

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.

### `enhance_with_context` (~132 tokens)

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.

Input parameters:

- `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, required): The user's natural-language question or prompt to enhance (e.g. "How do I handle KLV payments in my contract?").

### `search_documentation` (~132 tokens)

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.

Input parameters:

- `category` (string): Narrow results to a specific knowledge category. Available: core, storage, events, tokens, modules, tools, scripts, examples, errors, best-practices, documentation.
- `query` (string, required): Search query in natural language (e.g. "how to use storage mappers", "deploy contract to testnet", "handle KDA token transfers").

### `analyze_contract` (~136 tokens)

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.

Input parameters:

- `contractName` (string): Human-readable name for the contract (used in output labeling). Defaults to "contract" if omitted.
- `sourceCode` (string, required): The full Rust source code of the Klever smart contract to analyze. Must be valid Rust code using klever_sc imports.

### `get_balance` (~170 tokens)

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.

Input parameters:

- `address` (string, required): 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).

### `get_account` (~98 tokens)

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.

Input parameters:

- `address` (string, required): Klever address (klv1... bech32 format).
- `network` (string): Network to query. Options: "mainnet", "testnet", "devnet", "local". Defaults to server default (mainnet).

### `get_asset_info` (~149 tokens)

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.

Input parameters:

- `assetId` (string, required): 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).

### `query_sc` (~204 tokens)

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.

Input parameters:

- `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, required): 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, required): Smart contract address (klv1... bech32 format).

### `get_transaction` (~89 tokens)

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.

Input parameters:

- `hash` (string, required): Transaction hash (hex string).
- `network` (string): Network to query. Options: "mainnet", "testnet", "devnet", "local". Defaults to server default (mainnet).

### `get_block` (~103 tokens)

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.

Input parameters:

- `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.

### `list_validators` (~70 tokens)

List active validators on the Klever blockchain network. Returns validator addresses, names, commission rates, delegation info, and staking amounts.

Input parameters:

- `network` (string): Network to query. Options: "mainnet", "testnet", "devnet", "local". Defaults to server default (mainnet).

### `init_klever_project` (~199 tokens)

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. NOTE: In public profile, this tool returns a project template JSON and does not perform any filesystem changes.

Input parameters:

- `name` (string, required): 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".

### `add_helper_scripts` (~122 tokens)

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). NOTE: In public profile, this tool returns a project template JSON and does not perform any filesystem changes.

Input parameters:

- `contractName` (string): The contract name to embed in scripts (e.g. "my-token"). If omitted, auto-detected from the `name` field in Cargo.toml.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/klever-io-mcp-klever-vm/mcp#diagnostics

## Score history

- 2026-08-03: 77
- 2026-08-02: 76
- 2026-08-01: 76
- 2026-07-31: 75
- 2026-07-30: 72
- 2026-07-29: 72
- 2026-07-28: 71
- 2026-07-27: 70
- 2026-07-26: 70

## Links

- Remote endpoint: https://mcp.klever.org/mcp
- Repository: https://github.com/klever-io/mcp-klever-vm
- Changelog RSS feed: https://verifymcp.io/servers/klever-io-mcp-klever-vm/mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/klever-io-mcp-klever-vm/mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/klever-io-mcp-klever-vm/mcp