io.github.klever-io/mcp-klever-vm

Est-ce que io.github.klever-io/mcp-klever-vm est sûr ?

Au dernier audit MCP Hub, le serveur MCP « io.github.klever-io/mcp-klever-vm » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 16 outils

• add_helper_scripts≈ 198 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.

  Paramètres, retour & exemple (1)

  Paramètres

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

  Exemple d'appel

  {"name": "add_helper_scripts", "arguments": {"contractName": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• analyze_contract≈ 242 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.

  Paramètres, retour & exemple (2)

  Paramètres

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

  Exemple d'appel

  {"name": "analyze_contract", "arguments": {"sourceCode": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• enhance_with_context≈ 248 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.

  Paramètres, retour & exemple (2)

  Paramètres

  • query · string · requis
    The user's natural-language question or prompt to enhance (e.g. "How do I handle KLV payments in my contract?").
  • autoInclude · boolean · optionnel
    When true (default), automatically appends the most relevant knowledge base entries to the response. Set to false to only return metadata without injecting context.

  Exemple d'appel

  {"name": "enhance_with_context", "arguments": {"query": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• find_similar≈ 206 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.

  Paramètres, retour & exemple (2)

  Paramètres

  • id · string · requis
    The context ID to find similar entries for. Obtain from query_context or get_context results.
  • limit · integer · optionnel
    Maximum number of similar entries to return. Typical range is 1-20; higher values may be slower. Default: 5.

  Exemple d'appel

  {"name": "find_similar", "arguments": {"id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_account≈ 190 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.

  Paramètres, retour & exemple (2)

  Paramètres

  • address · string · requis
    Klever address (klv1... bech32 format).
  • network · string · optionnel · mainnet | testnet | devnet | local
    Network to query. Options: "mainnet", "testnet", "devnet", "local". Defaults to server default (mainnet).

  Exemple d'appel

  {"name": "get_account", "arguments": {"address": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_asset_info≈ 222 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.

  Paramètres, retour & exemple (2)

  Paramètres

  • assetId · string · requis
    Asset identifier (e.g. "KLV", "KFI", "USDT-A1B2", "MYNFT-XY78").
  • network · string · optionnel · mainnet | testnet | devnet | local
    Network to query. Options: "mainnet", "testnet", "devnet", "local". Defaults to server default (mainnet).

  Exemple d'appel

  {"name": "get_asset_info", "arguments": {"assetId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_balance≈ 235 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.

  Paramètres, retour & exemple (3)

  Paramètres

  • address · string · requis
    Klever address (klv1... bech32 format).
  • assetId · string · optionnel
    Optional KDA token ID (e.g. "USDT-A1B2", "LPKLVKFI-3I0N"). Omit for KLV balance.
  • network · string · optionnel · mainnet | testnet | devnet | local
    Network to query. Options: "mainnet", "testnet", "devnet", "local". Defaults to server default (mainnet).

  Exemple d'appel

  {"name": "get_balance", "arguments": {"address": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_block≈ 190 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.

  Paramètres, retour & exemple (2)

  Paramètres

  • nonce · integer · optionnel
    Block number (nonce). Omit to get the latest block.
  • network · string · optionnel · mainnet | testnet | devnet | local
    Network to query. Options: "mainnet", "testnet", "devnet", "local". Defaults to server default (mainnet).

  Exemple d'appel

  {"name": "get_block", "arguments": {"nonce": 1, "network": "mainnet"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_context≈ 156 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.

  Paramètres, retour & exemple (1)

  Paramètres

  • id · string · requis
    The unique context ID (UUID format). Obtain IDs from query_context or find_similar results.

  Exemple d'appel

  {"name": "get_context", "arguments": {"id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_knowledge_stats≈ 132 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.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "get_knowledge_stats", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_transaction≈ 179 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.

  Paramètres, retour & exemple (2)

  Paramètres

  • hash · string · requis
    Transaction hash (hex string).
  • network · string · optionnel · mainnet | testnet | devnet | local
    Network to query. Options: "mainnet", "testnet", "devnet", "local". Defaults to server default (mainnet).

  Exemple d'appel

  {"name": "get_transaction", "arguments": {"hash": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• init_klever_project≈ 324 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.

  Paramètres, retour & exemple (3)

  Paramètres

  • name · string · requis
    The contract project name in kebab-case (e.g. "my-token", "nft-marketplace"). Used as the Cargo package name and directory name.
  • noMove · boolean · optionnel
    When true, keeps the project in the SDK output directory instead of moving it to the current working directory. Default: false.
  • template · string · optionnel · empty | adder
    Project template to scaffold from. "empty" creates a blank contract with just an init function. "adder" creates a simple counter example. Default: "empty".

  Exemple d'appel

  {"name": "init_klever_project", "arguments": {"name": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• list_validators≈ 150 tokens

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

  Paramètres, retour & exemple (1)

  Paramètres

  • network · string · optionnel · mainnet | testnet | devnet | local
    Network to query. Options: "mainnet", "testnet", "devnet", "local". Defaults to server default (mainnet).

  Exemple d'appel

  {"name": "list_validators", "arguments": {"network": "mainnet"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• query_context≈ 472 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.

  Paramètres, retour & exemple (6)

  Paramètres

  • tags · array · optionnel
    Filter by tags (e.g. ["storage", "mapper"], ["tokens", "KLV"], ["events"]). Tags are matched with OR logic — any matching tag includes the entry.
  • limit · integer · optionnel
    Maximum number of results to return (1-100). Default: 10.
  • query · string · optionnel
    Free-text search query. Use Klever-specific terms for best results (e.g. "storage mapper SingleValueMapper", "payable endpoint KLV", "deploy contract testnet").
  • types · array · optionnel
    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 · integer · optionnel
    Number of results to skip for pagination. Use with limit to page through results. Default: 0.
  • contractType · string · optionnel
    Filter by contract type (e.g. "token", "nft", "defi", "dao"). Only returns entries tagged for this contract category.

  Exemple d'appel

  {"name": "query_context", "arguments": {"tags": [], "limit": 1, "query": "texte", "types": [], "offset": 1, "contractType": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• query_sc≈ 328 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.

  Paramètres, retour & exemple (5)

  Paramètres

  • args · array · optionnel
    Optional base64-encoded arguments. For addresses, encode the hex-decoded bech32 bytes. For numbers, use big-endian byte encoding.
  • caller · string · optionnel
    Optional caller address (klv1... bech32 format). Some view functions use the caller to look up address-keyed storage mappers.
  • network · string · optionnel · mainnet | testnet | devnet | local
    Network to query. Options: "mainnet", "testnet", "devnet", "local". Defaults to server default (mainnet).
  • funcName · string · requis
    Function name to call (must be a #[view] function on the contract).
  • scAddress · string · requis
    Smart contract address (klv1... bech32 format).

  Exemple d'appel

  {"name": "query_sc", "arguments": {"funcName": "texte", "scAddress": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• search_documentation≈ 264 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.

  Paramètres, retour & exemple (2)

  Paramètres

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

  Exemple d'appel

  {"name": "search_documentation", "arguments": {"query": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

https://mcp.klever.org/mcp