# io.github.LakeLogic/lakelogic-mcp (pypi · lakelogic-mcp)

Validate, lint, test-run and explain Open Lakehouse Contracts with LakeLogic, from any AI assistant.

- Trust score: 86/100 (high trust)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-04

## Components

- pypi · `lakelogic-mcp`: 86/100 (this document), [markdown](https://verifymcp.io/servers/lakelogic-lakelogic-mcp/lakelogic-mcp.md), [page](https://verifymcp.io/servers/lakelogic-lakelogic-mcp/lakelogic-mcp)

## Channel facts

- Registry: `pypi`
- Package: `lakelogic-mcp`
- Version: `0.1.4`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-04.

- **Supply Chain Security**: 99/100
  - No malware found by supply-chain analysis.
  - Known CVEs were checked across the 58 of 59 dependencies we could resolve, so this covers what we could see, not the whole tree.
  - Runs hatchling.build at install time, a recognised build step with no custom scripting around it.
  - Dependency health was assessed across the 58 of 59 dependencies we could resolve, so this covers what we could see, not the whole tree.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to LakeLogic/lakelogic-mcp).
  - Clear OSI-approved license (Apache-2.0).
  - Actively maintained (last published 7 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 63/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 595 tokens (~85/item across 7 items; 7 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 67/100
  - Stability observed for 20 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the io.github.LakeLogic/lakelogic-mcp server?

io.github.LakeLogic/lakelogic-mcp runs locally as a PyPI package, launched with uvx lakelogic-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add lakelogic-lakelogic-mcp -- uvx lakelogic-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "lakelogic-lakelogic-mcp": {
      "command": "uvx",
      "args": [
        "lakelogic-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "lakelogic-lakelogic-mcp": {
      "command": "uvx",
      "args": [
        "lakelogic-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add lakelogic-lakelogic-mcp -- uvx lakelogic-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "lakelogic-lakelogic-mcp": {
      "type": "local",
      "command": [
        "uvx",
        "lakelogic-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add lakelogic-lakelogic-mcp --command uvx --arg lakelogic-mcp
```

### Hermes

```yaml
mcp_servers:
  lakelogic-lakelogic-mcp:
    command: "uvx"
    args: ["lakelogic-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "lakelogic-lakelogic-mcp": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "lakelogic-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add lakelogic-lakelogic-mcp -t stdio -c uvx -a lakelogic-mcp
```

### Other

```json
{
  "mcpServers": {
    "lakelogic-lakelogic-mcp": {
      "command": "uvx",
      "args": [
        "lakelogic-mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 86, +16)

- [security improvement] Malware scan: unverified → pass

### 2026-11-03 (score 70, −15)

- [security regression] Malware scan: pass → unverified

### 2026-11-02 (score 85, +1)

No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-31 (score 84, +16)

- [security improvement] Malware scan: unverified → pass

### 2026-10-30 (score 68, −15)

- [security regression] Malware scan: pass → unverified

### 2026-10-29 (score 83, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-28 (score 82, +15)

- [security improvement] Malware scan: unverified → pass
- [functional] Package version: 0.1.3 → 0.1.4

### 2026-10-27 (score 67, −14)

- [security regression] Malware scan: pass → unverified

## MCP tools (7)

### `validate_contract` (~90 tokens)

Check whether a contract is LEGAL Open Lakehouse Contract (OLC): known keys, right shapes, required
fields. Use it after writing or editing a contract. Give `path` (a file in this project) or
\`contract_yaml` (the text). Returns `valid` and, if not, each error's location and problem.

Input parameters:

- `contract_yaml`
- `path`

Output parameters:

- `result` (object)

### `lint_contract` (~80 tokens)

Check whether a contract is a GOOD one: governance gaps such as a merge with no key, unordered
deduplication, untagged personal data, a step no engine runs. Use it after validate_contract passes.
Returns `clean` and findings, each with its rule code, severity and fix.

Input parameters:

- `contract_yaml`
- `path`

Output parameters:

- `result` (object)

### `explain_rule` (~53 tokens)

Explain one lint rule (e.g. KEY-002): what it checks, why it matters, a failing contract and the
fixed contract. Use it when a lint finding is unclear.

Input parameters:

- `code` (string, required)

Output parameters:

- `result` (object)

### `contract_reference` (~50 tokens)

Read the OLC reference for one part of a contract. Topics include anatomy (every key),
quality, transformation, materialization, ingestion, security, slo, execution-order.

Input parameters:

- `topic` (string, required)

Output parameters:

- `result` (object)

### `export_odcs` (~35 tokens)

Convert a contract file in this project to an Open Data Contract Standard (ODCS) document.

Input parameters:

- `path` (string, required)

Output parameters:

- `result` (object)

### `generate_test_data` (~90 tokens)

Write synthetic test data for a contract (default test_data/<contract>.csv): right types,
accepted values and ranges, with `invalid_ratio` of rows deliberately breaking the quality rules
so a run shows quarantine working. Follow with run_contract.

Input parameters:

- `invalid_ratio` (number)
- `output`
- `path` (string, required)
- `rows` (integer)
- `seed`

Output parameters:

- `result` (object)

### `run_contract` (~102 tokens)

Run a contract on a local data file (CSV/Parquet) with Polars or DuckDB: good rows,
quarantined rows, and each quarantine reason with its count. Writes nothing to the contract's
target. `write_outputs` saves good/bad rows under runs/.

Input parameters:

- `engine` (string)
- `path` (string, required)
- `sample` (integer)
- `source` (string, required)
- `write_outputs` (boolean)

Output parameters:

- `result` (object)

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/lakelogic-lakelogic-mcp/lakelogic-mcp#diagnostics

## Score history

- 2026-11-04: 86
- 2026-11-03: 70
- 2026-11-02: 85
- 2026-11-01: 84
- 2026-10-31: 84
- 2026-10-30: 68
- 2026-10-29: 83
- 2026-10-28: 82
- 2026-10-27: 67
- 2026-10-26: 81
- 2026-10-25: 66
- 2026-10-24: 80
- 2026-10-23: 80
- 2026-10-22: 79
- 2026-10-21: 64
- 2026-10-20: 79
- 2026-10-19: 63
- 2026-10-18: 78
- 2026-10-17: 76
- 2026-10-16: 59
- 2026-10-15: 61

## Common questions

### What is the io.github.LakeLogic/lakelogic-mcp server?

io.github.LakeLogic/lakelogic-mcp is listed in the public MCP registry as io.github.LakeLogic/lakelogic-mcp. Validate, lint, test-run and explain Open Lakehouse Contracts with LakeLogic, from any AI assistant. This page covers its PyPI package (lakelogic-mcp).

### Is the io.github.LakeLogic/lakelogic-mcp server safe to use?

io.github.LakeLogic/lakelogic-mcp scores 86 out of 100 on VerifyMCP. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the io.github.LakeLogic/lakelogic-mcp server expose?

io.github.LakeLogic/lakelogic-mcp exposes 7 tools: validate_contract, lint_contract, explain_rule, contract_reference, export_odcs, and 2 more. Their descriptions and schemas cost roughly 500 tokens of context every time the server is loaded.

### Is the io.github.LakeLogic/lakelogic-mcp server still maintained?

io.github.LakeLogic/lakelogic-mcp is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the io.github.LakeLogic/lakelogic-mcp server under?

io.github.LakeLogic/lakelogic-mcp declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- PyPI project: https://pypi.org/project/lakelogic-mcp/
- Socket report: https://socket.dev/pypi/package/lakelogic-mcp
- Repository: https://github.com/LakeLogic/lakelogic-mcp
- Changelog RSS feed: https://verifymcp.io/servers/lakelogic-lakelogic-mcp/lakelogic-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/lakelogic-lakelogic-mcp/lakelogic-mcp.json
- HTML version of this page: https://verifymcp.io/servers/lakelogic-lakelogic-mcp/lakelogic-mcp