Skip to main content
Glama
README.md
# lunc-mcp

[![CI](https://github.com/Semence2Porc/lunc-mcp/actions/workflows/ci.yml/badge.svg)](https://github.com/Semence2Porc/lunc-mcp/actions/workflows/ci.yml)

A [Model Context Protocol](https://modelcontextprotocol.io) 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](https://github.com/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

## Usage

```bash
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`):

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

## Related

- [Semence2Porc/lunc-skills](https://github.com/Semence2Porc/lunc-skills) — the
  agent skills (icskills format) built on this registry.

## License

MIT — see [LICENSE](LICENSE).

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.

Maintenance

ActivityMaintained
ResponsivenessNo issues