F
licenseA
qualityD
maintenanceA comprehensive MCP server for MetaApp development, offering tools for project initialization, protocol exploration, and blockchain interaction.
Last updated
15
mcp-klever-vm
Server Details
MCP server for Klever blockchain smart contract development.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- klever-io/mcp-klever-vm
- GitHub Stars
- 32
- Server Listing
- Klever MCP Server
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
MCP client
Glama
MCP server
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
100% free. Your data is private.
Tool Definition Quality
A4.2/5.0
Tool DescriptionsA
Average 4.3/5 across 16 of 16 tools scored.
Server CoherenceA
Disambiguation4/5
Most tools have clearly distinct purposes, such as get_balance for token balances, analyze_contract for code analysis, and init_klever_project for project scaffolding. However, there is some overlap between query_context and search_documentation, both of which search the knowledge base, which could cause confusion about which to use for specific queries.
Naming Consistency4/5
The naming follows a consistent verb_noun pattern throughout, such as get_balance, analyze_contract, and init_klever_project. Minor deviations exist, like add_helper_scripts (verb_adjective_noun) and enhance_with_context (verb_preposition_noun), but overall, the pattern is clear and predictable.
Tool Count4/5
With 16 tools, the count is slightly high but reasonable for the Klever VM domain, which covers blockchain queries, smart contract development, and knowledge base management. It provides comprehensive coverage without being overwhelmingly large, though it could be streamlined by merging overlapping tools.
Completeness5/5
The tool set offers complete coverage for Klever VM development, including project setup (init_klever_project, add_helper_scripts), contract analysis and querying (analyze_contract, query_sc), blockchain data retrieval (get_balance, get_transaction, get_block), and knowledge base access (query_context, search_documentation). No obvious gaps are present for the intended scope.
Available Tools
16 toolsadd_helper_scriptsRead-onlyIdempotentInspect
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.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| contractName | No | The contract name to embed in scripts (e.g. "my-token"). If omitted, auto-detected from the `name` field in Cargo.toml. |
analyze_contractRead-onlyIdempotentInspect
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.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| sourceCode | Yes | The full Rust source code of the Klever smart contract to analyze. Must be valid Rust code using klever_sc imports. | |
| contractName | No | Human-readable name for the contract (used in output labeling). Defaults to "contract" if omitted. |
enhance_with_contextRead-onlyIdempotentInspect
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.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | The user's natural-language question or prompt to enhance (e.g. "How do I handle KLV payments in my contract?"). | |
| autoInclude | No | When true (default), automatically appends the most relevant knowledge base entries to the response. Set to false to only return metadata without injecting context. |
find_similarRead-onlyIdempotentInspect
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.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | The context ID to find similar entries for. Obtain from query_context or get_context results. | |
| limit | No | Maximum number of similar entries to return. Typical range is 1-20; higher values may be slower. Default: 5. |
get_accountRead-onlyIdempotentInspect
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.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| address | Yes | Klever address (klv1... bech32 format). | |
| network | No | Network to query. Options: "mainnet", "testnet", "devnet", "local". Defaults to server default (mainnet). |
get_asset_infoRead-onlyIdempotentInspect
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.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| assetId | Yes | Asset identifier (e.g. "KLV", "KFI", "USDT-A1B2", "MYNFT-XY78"). | |
| network | No | Network to query. Options: "mainnet", "testnet", "devnet", "local". Defaults to server default (mainnet). |
get_balanceRead-onlyIdempotentInspect
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.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| address | Yes | Klever address (klv1... bech32 format). | |
| assetId | No | Optional KDA token ID (e.g. "USDT-A1B2", "LPKLVKFI-3I0N"). Omit for KLV balance. | |
| network | No | Network to query. Options: "mainnet", "testnet", "devnet", "local". Defaults to server default (mainnet). |
get_blockRead-onlyIdempotentInspect
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.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| nonce | No | Block number (nonce). Omit to get the latest block. | |
| network | No | Network to query. Options: "mainnet", "testnet", "devnet", "local". Defaults to server default (mainnet). |
get_contextRead-onlyIdempotentInspect
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.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | The unique context ID (UUID format). Obtain IDs from query_context or find_similar results. |
get_knowledge_statsRead-onlyIdempotentInspect
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.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
get_transactionRead-onlyIdempotentInspect
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.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| hash | Yes | Transaction hash (hex string). | |
| network | No | Network to query. Options: "mainnet", "testnet", "devnet", "local". Defaults to server default (mainnet). |
init_klever_projectRead-onlyIdempotentInspect
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.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | The contract project name in kebab-case (e.g. "my-token", "nft-marketplace"). Used as the Cargo package name and directory name. | |
| noMove | No | When true, keeps the project in the SDK output directory instead of moving it to the current working directory. Default: false. | |
| template | No | Project template to scaffold from. "empty" creates a blank contract with just an init function. "adder" creates a simple counter example. Default: "empty". | empty |
list_validatorsRead-onlyIdempotentInspect
List active validators on the Klever blockchain network. Returns validator addresses, names, commission rates, delegation info, and staking amounts.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| network | No | Network to query. Options: "mainnet", "testnet", "devnet", "local". Defaults to server default (mainnet). |
query_contextRead-onlyIdempotentInspect
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.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| tags | No | Filter by tags (e.g. ["storage", "mapper"], ["tokens", "KLV"], ["events"]). Tags are matched with OR logic — any matching tag includes the entry. | |
| limit | No | Maximum number of results to return (1-100). Default: 10. | |
| query | No | Free-text search query. Use Klever-specific terms for best results (e.g. "storage mapper SingleValueMapper", "payable endpoint KLV", "deploy contract testnet"). | |
| types | No | 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 reviews. | |
| offset | No | Number of results to skip for pagination. Use with limit to page through results. Default: 0. | |
| contractType | No | Filter by contract type (e.g. "token", "nft", "defi", "dao"). Only returns entries tagged for this contract category. |
query_scRead-onlyIdempotentInspect
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.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| args | No | Optional base64-encoded arguments. For addresses, encode the hex-decoded bech32 bytes. For numbers, use big-endian byte encoding. | |
| caller | No | Optional caller address (klv1... bech32 format). Some view functions use the caller to look up address-keyed storage mappers. | |
| network | No | Network to query. Options: "mainnet", "testnet", "devnet", "local". Defaults to server default (mainnet). | |
| funcName | Yes | Function name to call (must be a #[view] function on the contract). | |
| scAddress | Yes | Smart contract address (klv1... bech32 format). |
search_documentationRead-onlyIdempotentInspect
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.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | Search query in natural language (e.g. "how to use storage mappers", "deploy contract to testnet", "handle KDA token transfers"). | |
| category | No | Narrow results to a specific knowledge category. Available: core, storage, events, tokens, modules, tools, scripts, examples, errors, best-practices, documentation. |
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Servers
- Alicense-qualityFmaintenanceA lightweight, fast MCP server that provides onchain capabilities for the LLMs and Agents.Last updated60250MIT
- Flicense-qualityDmaintenanceModel Context Protocol server for Kaspa operations using WASM SDK. Enables LLMs to interact with the Kaspa network through standardized MCP tools.Last updated11
- AlicenseAqualityCmaintenanceA MCP server do create and deploy backend applications using https://heim.devLast updated673MIT
Try in Browser
Your Connectors
Sign in to create a connector for this server.