io.github.LakeLogic/lakelogic-mcp
PYPI · LAKELOGIC-MCP
Validate, lint, test-run and explain Open Lakehouse Contracts with LakeLogic, from any AI assistant.
Available components
Last scanned (17 hours ago)
Scores higher than 89% of PyPI servers
Category Testing and QA
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. How we score → Why this is hard to score →
Supply Chain Security99
- No malware found by supply-chain analysis.Pass
- Known CVEs were checked across the 58 of 59 dependencies we could resolve, so this covers what we could see, not the whole tree.Partial
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- Dependency health was assessed across the 58 of 59 dependencies we could resolve, so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to LakeLogic/lakelogic-mcp). View diagnostics → Pass
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 7 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability63
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 595 tokens (~85/item across 7 items; 7 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management67
- Stability observed for 20 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 +16
- Malware scan: unverified → pass ▲ security
- 3 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 2 Nov 26 +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.
- 31 Oct 26 +16
- Malware scan: unverified → pass ▲ security
- 30 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 29 Oct 26 +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.
- 28 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- Package version: 0.1.3 → 0.1.4 functional
- 27 Oct 26 −14
- Malware scan: pass → unverified ▼ security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Analysed pypi/lakelogic-mcp@0.1.4
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | LakeLogic/lakelogic-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/LakeLogic/lakelogic-mcp/.github/workflows/publish.yml@refs/tags/v0.1.4 |
| Rekor log index | 3535331575 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:d705f67c209ed1849fce2cd612b56fefd1e01878499590aecb788138ac60b3a9 |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 58 packages
| Packages resolved | 58 |
|---|---|
| Stale | 5 |
| No linked repository | 1 |
| Tree resolution | Partial |
The dependency tree was only partially resolved, so these counts may be incomplete.
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
contract_reference ~50
Read the OLC reference for one part of a contract. Topics include anatomy (every key), quality, transformation, materialization, ingestion, security, slo, execution-order.
| Name | Type | Req | Description |
|---|---|---|---|
| topic | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | object | yes | – |
No examples provided.
explain_rule ~53
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.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | object | yes | – |
No examples provided.
export_odcs ~35
Convert a contract file in this project to an Open Data Contract Standard (ODCS) document.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | object | yes | – |
No examples provided.
generate_test_data ~90
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.
| Name | Type | Req | Description |
|---|---|---|---|
| invalid_ratio | number | – | – |
| output | – | – | – |
| path | string | yes | – |
| rows | integer | – | – |
| seed | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | object | yes | – |
No examples provided.
lint_contract ~80
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.
| Name | Type | Req | Description |
|---|---|---|---|
| contract_yaml | – | – | – |
| path | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | object | yes | – |
No examples provided.
run_contract ~102
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/.
| Name | Type | Req | Description |
|---|---|---|---|
| engine | string | – | – |
| path | string | yes | – |
| sample | integer | – | – |
| source | string | yes | – |
| write_outputs | boolean | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | object | yes | – |
No examples provided.
validate_contract ~90
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.
| Name | Type | Req | Description |
|---|---|---|---|
| contract_yaml | – | – | – |
| path | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | object | yes | – |
No examples provided.
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.
pypi · lakelogic-mcp
claude mcp add lakelogic-lakelogic-mcp -- uvx lakelogic-mcp
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.