_ registry / mcp http-sse · checked 59m ago

klever-vm-mcp

https://mcp.klever.org

Registry code: ad39b26b48acad3e

api record

MCP server for Klever blockchain smart contract development.

from a public catalogue that lists it, not from the operator

endpoint
https://mcp.klever.org/mcp
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is klever-vm-mcp live?
Yes — it answered the hub's last check (checked 59m ago). It answered 99% of checks over the last 30 days.
Is klever-vm-mcp free to use?
Yes — the hub reached it with no key and no payment.
What tools does klever-vm-mcp have?
16 tools: add_helper_scripts, get_asset_info, search_documentation, get_balance, get_knowledge_stats, get_transaction, init_klever_project, enhance_with_context, ….
Is klever-vm-mcp safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
99.1%

90 days 98.9%· all time 98.9%

latency
180ms

last good check

priced tools
0

of 16 tools

_ answered our checks, 90 days 366 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
topic
developer tools code & repositories
used for
  • scaffold a klever smart contract project
  • analyze smart contract code
  • search klever vm docs
  • get klever account balance
  • query a smart contract
takes → gives
text, code → data, code, text
tools
14 reads2 changes data
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 16 tools
14 open 2 never probed 14 of 16 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • search_documentation reads open 8h ago

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "query"
  ],
  "properties": {
    "query": {
      "type": "string",
      "description": "Search query in natural language (e.g. \"how to use storage mappers\", \"deploy contract to testnet\", \"handle KDA token transfers\")."
    },
    "category": {
      "enum": [
        "core",
        "storage",
        "events",
        "tokens",
        "modules",
        "tools",
        "scripts",
        "examples",
        "errors",
        "best-practices",
        "documentation"
      ],
      "type": "string",
      "description": "Narrow results to a specific knowledge category. Available: core, storage, events, tokens, modules, tools, scripts, examples, errors, best-practices, documentation."
    }
  }
}
    arguments 29 lines
  • get_balance reads open 58m ago

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "address"
  ],
  "properties": {
    "address": {
      "type": "string",
      "description": "Klever address (klv1... bech32 format)."
    },
    "assetId": {
      "type": "string",
      "description": "Optional KDA token ID (e.g. \"USDT-A1B2\", \"LPKLVKFI-3I0N\"). Omit for KLV balance."
    },
    "network": {
      "enum": [
        "mainnet",
        "testnet",
        "devnet",
        "local"
      ],
      "type": "string",
      "description": "Network to query. Options: \"mainnet\", \"testnet\", \"devnet\", \"local\". Defaults to server default (mainnet)."
    }
  }
}
    arguments 26 lines
  • get_knowledge_stats reads open 15h ago

    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.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • get_transaction reads open 12h ago

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "hash"
  ],
  "properties": {
    "hash": {
      "type": "string",
      "description": "Transaction hash (hex string)."
    },
    "network": {
      "enum": [
        "mainnet",
        "testnet",
        "devnet",
        "local"
      ],
      "type": "string",
      "description": "Network to query. Options: \"mainnet\", \"testnet\", \"devnet\", \"local\". Defaults to server default (mainnet)."
    }
  }
}
    arguments 22 lines
  • init_klever_project changes data open 12h ago

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "name"
  ],
  "properties": {
    "name": {
      "type": "string",
      "description": "The contract project name in kebab-case (e.g. \"my-token\", \"nft-marketplace\"). Used as the Cargo package name and directory name."
    },
    "noMove": {
      "type": "boolean",
      "default": false,
      "description": "When true, keeps the project in the SDK output directory instead of moving it to the current working directory. Default: false."
    },
    "template": {
      "enum": [
        "empty",
        "adder"
      ],
      "type": "string",
      "default": "empty",
      "description": "Project template to scaffold from. \"empty\" creates a blank contract with just an init function. \"adder\" creates a simple counter example. Default: \"empty\"."
    }
  }
}
    arguments 26 lines
  • enhance_with_context reads open 12h ago

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "query"
  ],
  "properties": {
    "query": {
      "type": "string",
      "description": "The user's natural-language question or prompt to enhance (e.g. \"How do I handle KLV payments in my contract?\")."
    },
    "autoInclude": {
      "type": "boolean",
      "default": true,
      "description": "When true (default), automatically appends the most relevant knowledge base entries to the response. Set to false to only return metadata without injecting context."
    }
  }
}
    arguments 17 lines
  • get_context reads open 58m ago

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string",
      "description": "The unique context ID (UUID format). Obtain IDs from query_context or find_similar results."
    }
  }
}
    arguments 12 lines
  • analyze_contract reads open 3h ago

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "sourceCode"
  ],
  "properties": {
    "sourceCode": {
      "type": "string",
      "description": "The full Rust source code of the Klever smart contract to analyze. Must be valid Rust code using klever_sc imports."
    },
    "contractName": {
      "type": "string",
      "description": "Human-readable name for the contract (used in output labeling). Defaults to \"contract\" if omitted."
    }
  }
}
    arguments 16 lines
  • find_similar reads open 3h ago

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string",
      "description": "The context ID to find similar entries for. Obtain from query_context or get_context results."
    },
    "limit": {
      "type": "integer",
      "default": 5,
      "minimum": 1,
      "description": "Maximum number of similar entries to return. Typical range is 1-20; higher values may be slower. Default: 5."
    }
  }
}
    arguments 18 lines
  • get_account reads open 3h ago

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "address"
  ],
  "properties": {
    "address": {
      "type": "string",
      "description": "Klever address (klv1... bech32 format)."
    },
    "network": {
      "enum": [
        "mainnet",
        "testnet",
        "devnet",
        "local"
      ],
      "type": "string",
      "description": "Network to query. Options: \"mainnet\", \"testnet\", \"devnet\", \"local\". Defaults to server default (mainnet)."
    }
  }
}
    arguments 22 lines
  • get_block reads open 15h ago

    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.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "nonce": {
      "type": "integer",
      "minimum": 0,
      "description": "Block number (nonce). Omit to get the latest block."
    },
    "network": {
      "enum": [
        "mainnet",
        "testnet",
        "devnet",
        "local"
      ],
      "type": "string",
      "description": "Network to query. Options: \"mainnet\", \"testnet\", \"devnet\", \"local\". Defaults to server default (mainnet)."
    }
  }
}
    arguments 20 lines
  • list_validators reads open 15h ago

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

    mcp-tool

    {
  "type": "object",
  "properties": {
    "network": {
      "enum": [
        "mainnet",
        "testnet",
        "devnet",
        "local"
      ],
      "type": "string",
      "description": "Network to query. Options: \"mainnet\", \"testnet\", \"devnet\", \"local\". Defaults to server default (mainnet)."
    }
  }
}
    arguments 15 lines
  • query_context reads open 8h ago

    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.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "tags": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Filter by tags (e.g. [\"storage\", \"mapper\"], [\"tokens\", \"KLV\"], [\"events\"]). Tags are matched with OR logic — any matching tag includes the entry."
    },
    "limit": {
      "type": "integer",
      "default": 10,
      "maximum": 100,
      "minimum": 1,
      "description": "Maximum number of results to return (1-100). Default: 10."
    },
    "query": {
      "type": "string",
      "description": "Free-text search query. Use Klever-specific terms for best results (e.g. \"storage mapper SingleValueMapper\", \"payable endpoint KLV\", \"deploy contract testnet\")."
    },
    "types": {
      "type": "array",
      "items": {
        "enum": [
          "code_example",
          "best_practice",
          "security_tip",
          "optimization",
          "documentation",
          "error_pattern",
          "deployment_tool",
          "runtime_behavior"
        ],
        "type": "string"
      },
      "description": "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": {
      "type": "integer",
      "default": 0,
      "minimum": 0,
      "description": "Number of results to skip for pagination. Use with limit to page through results. Default: 0."
    },
    "contractType": {
      "type": "string",
      "description": "Filter by contract type (e.g. \"token\", \"nft\", \"defi\", \"dao\"). Only returns entries tagged for this contract category."
    }
  }
}
    arguments 50 lines
  • query_sc reads open 8h ago

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "scAddress",
    "funcName"
  ],
  "properties": {
    "args": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Optional base64-encoded arguments. For addresses, encode the hex-decoded bech32 bytes. For numbers, use big-endian byte encoding."
    },
    "caller": {
      "type": "string",
      "description": "Optional caller address (klv1... bech32 format). Some view functions use the caller to look up address-keyed storage mappers."
    },
    "network": {
      "enum": [
        "mainnet",
        "testnet",
        "devnet",
        "local"
      ],
      "type": "string",
      "description": "Network to query. Options: \"mainnet\", \"testnet\", \"devnet\", \"local\". Defaults to server default (mainnet)."
    },
    "funcName": {
      "type": "string",
      "description": "Function name to call (must be a #[view] function on the contract)."
    },
    "scAddress": {
      "type": "string",
      "description": "Smart contract address (klv1... bech32 format)."
    }
  }
}
    arguments 38 lines
  • add_helper_scripts changes data unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "contractName": {
      "type": "string",
      "description": "The contract name to embed in scripts (e.g. \"my-token\"). If omitted, auto-detected from the `name` field in Cargo.toml."
    }
  }
}
    arguments 9 lines
  • get_asset_info reads unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "assetId"
  ],
  "properties": {
    "assetId": {
      "type": "string",
      "description": "Asset identifier (e.g. \"KLV\", \"KFI\", \"USDT-A1B2\", \"MYNFT-XY78\")."
    },
    "network": {
      "enum": [
        "mainnet",
        "testnet",
        "devnet",
        "local"
      ],
      "type": "string",
      "description": "Network to query. Options: \"mainnet\", \"testnet\", \"devnet\", \"local\". Defaults to server default (mainnet)."
    }
  }
}
    arguments 22 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id ad39b26b48acad3e.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/ad39b26b48acad3e/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/ad39b26b48acad3e/badge.svg)](https://brick.blue/agent/ad39b26b48acad3e?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.