Skip to main content
Glama

lunc-mcp

CI

A Model Context Protocol server for the Terra Classic blockchain — gives MCP-capable agents a verified, structured corpus of Terra Classic engineering findings, plus the companion agent skills published at Semence2Porc/lunc-skills.

Every finding in the registry originates from a shipped, peer-reviewable PR with a reproducing test — not folklore. Skills fetched from lunc-skills cross-link into this registry for machine-readable detail and runnable freshness checks.

Status: v0.1.0 — early, testnet-oriented. Interfaces may change.

Requirements

  • Node.js ≥ 22

Related MCP server: engineering-knowledge-mcp

Usage

npm start            # run the MCP server (stdio)
npm run self-test    # built-in sanity check
npm test             # unit tests (node --test)

Register it with your MCP client (example, Claude Desktop claude_desktop_config.json):

{
  "mcpServers": {
    "lunc-mcp": {
      "command": "node",
      "args": ["/absolute/path/to/lunc-mcp/server/lunc-mcp.mjs"]
    }
  }
}

Layout

Path

Contents

server/

MCP stdio server (lunc-mcp.mjs), findings store, schema

registry/

Machine-readable finding registry (the skills' source of truth)

canister/

Internet Computer canister port of the registry access

test/

node --test unit tests

License

MIT — see LICENSE.

Available Tools

11 tools
balanceA

Native token balances for a terra1... address. Returns raw base-unit strings — never floats; unknown denoms must not be scaled (see terra-classic-indexing).

Inputs: address (required).

burn_snapshotA

Point-in-time burn economics: burn_tax_rate + uluna supply (raw base-unit string — BigInt in consumers, supply exceeds 2^53). The ICP canister accumulates these into a public time series.

Inputs: no named parameters.

contract_queryA

Generic CosmWasm contract query passthrough: run any {"smart":{...}} query against a terra1 contract and return raw JSON.

Inputs: query (required), contract (required).

explain_txA

Fetch a transaction by hash and decode it into human-readable summary lines (messages, amounts, fees, tax). Informational only — never authorization.

Inputs: hash (required).

findingsB

Query the attested audit finding registry (lunc-audit): verified findings with evidence, repro commands, and verdicts.

Inputs: repo, status.

ibc_denom_traceB

Resolve an IBC denom hash to its trace (path + base denom) when known.

Inputs: denom (required).

proposalsA

Governance proposals, newest first, with status filter. Uses gov/v1 (the v1beta1 list endpoint cannot encode modern multi-message proposals); includes verified tally params (quorum 0.40, threshold 0.50, veto 0.334).

Inputs: status.

simulate_txA

Simulate an unsigned tx (amino JSON) and report estimated gas plus the burn-tax impact at the current rate, computed in exact integer math.

Inputs: tx (required).

tax_paramsA

Terra Classic burn-tax parameters: burn_tax_rate (currently 0.015) and the gas-price table. Route is /terra/tax/v1beta1/params (NOT /cosmos/...).

Inputs: no named parameters.

validator_setA

Current active validator set with voting power (tokens are raw base-unit strings; rank is by integer power).

Inputs: no named parameters.

wallet_overviewB

Aggregate view of an address: native balances, delegations, unbonding, rewards, and any authz grants granted TO this address (agent-blast-radius check).

Inputs: address (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.8/5.0

    Scored across 11 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes, but balance and wallet_overview overlap since wallet_overview includes native balances. tax_params and burn_snapshot both surface burn_tax_rate, although their endpoints and broader intent differ.

    Naming Consistency4/5

    All names are lowercase snake_case and readable, but the pattern is mixed: some are plain nouns like balance/proposals/findings, while others use verb_noun like explain_tx/simulate_tx. The style is consistent enough to be predictable, but not perfectly uniform.

    Tool Count5/5

    Eleven tools is well within the ideal range and each tool maps to a distinct aspect of the Terra Classic domain. The count feels scoped rather than bloated or thin.

    Completeness4/5

    The surface covers balances, staking, rewards, governance, validators, transaction decode/simulation, burn economics, contract queries, IBC denom traces, and audit findings. Minor gaps exist like no block-height query or address transaction history, but core workflows are covered.

    Related MCP Connectors

    Related MCP Servers