Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

letin: Power Query (M)

PYPI · LETIN · SCANNED SEP 22

Inspect, refactor, lint, run and version Power Query (M) in Excel workbooks and Power BI projects.

Available components

49 Trust /100
Trust breakdown (7 categories)

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 Security50
  • Malware scan not yet available for this package.Unverified
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
  • 1 of 29 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency32
Schema Quality & AI Usability73
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 2726 tokens (~87/item across 31 items; 31 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage67
  • 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
Tool Safety88
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 1 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "remove_step" implies "remove" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Partial
  • An AI judge read all 32 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

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

Install

How do I install the letin: Power Query (M) MCP server?

letin: Power Query (M) runs locally as a PyPI package, launched with uvx letin. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · letin

# add to Claude Code
claude mcp add s-curvelabs-letin -- uvx letin
// .cursor/mcp.json
{
  "mcpServers": {
    "s-curvelabs-letin": {
      "command": "uvx",
      "args": [
        "letin"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "s-curvelabs-letin": {
      "command": "uvx",
      "args": [
        "letin"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add s-curvelabs-letin -- uvx letin
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "s-curvelabs-letin": {
      "type": "local",
      "command": [
        "uvx",
        "letin"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add s-curvelabs-letin --command uvx --arg letin
# ~/.hermes/config.yaml
mcp_servers:
  s-curvelabs-letin:
    command: "uvx"
    args: ["letin"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "s-curvelabs-letin": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "letin"
      ]
    }
  }
}
# add to Vellum
assistant mcp add s-curvelabs-letin -t stdio -c uvx -a letin
// mcp.json
{
  "mcpServers": {
    "s-curvelabs-letin": {
      "command": "uvx",
      "args": [
        "letin"
      ]
    }
  }
}
Changelog

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.

  • 22 Sept 26 49

    First indexed and scored.

Diagnostics

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 22 Sept 2026 · Analysed pypi/letin@0.2.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem pypi

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 29 packages
Packages resolved 29
No linked repository 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 31 exposed · ~2,372 tokens

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 →

Tool Tokens
apply_transform ~164

Add a standard Power Query step without hand-writing M. `action` and `params` come from list_transforms, e.g. action='unpivot_other_columns', params={'keep_columns': ['Region']}; or action='group_by', params={'group_columns': ['Region'], 'aggregations': [{'name': 'Total', 'operation': 'sum', 'column': 'Amount'}]}. The step is appended to the end unless after_step names an earlier step (the next step is rewired, as the editor does).

NameTypeReqDescription
actionstringyes
after_step
dry_runboolean
paramsobjectyes
querystringyes
sourcestringyes
step_name

No output schema declared.

No examples provided.

copy_queries ~72

Copy queries between workbooks / projects / folders, bringing the queries they depend on along.

NameTypeReqDescription
dry_runboolean
from_sourcestringyes
include_dependenciesboolean
namesarrayyes
overwriteboolean
to_sourcestringyes

No output schema declared.

No examples provided.

delete_query ~52

Delete a query. Refuses when other queries reference it unless force=true.

NameTypeReqDescription
dry_runboolean
forceboolean
namestringyes
sourcestringyes

No output schema declared.

No examples provided.

dependency_graph ~71

Query-to-query lineage. With `query`, only its upstream and downstream. format: 'json' or 'mermaid'. Also reports roots (read external data), leaves (final outputs), orphans and cyclic references.

NameTypeReqDescription
formatstring
query
sourcestringyes

No output schema declared.

No examples provided.

diff_queries ~68

Compare the queries of two sources (workbook vs workbook, workbook vs exported folder, PBIP vs PBIP ...). Line endings are ignored. To compare against a snapshot pass its `path` from list_snapshots.

NameTypeReqDescription
source_astringyes
source_bstringyes

No output schema declared.

No examples provided.

evaluate_m ~199

Run any M expression and get the result as data. Tables come back with column names, types and the first `rows` rows (cell errors shown as #ERROR); lists, records, scalars and functions (with signature) are described too; an M error comes back as reason + message. With `source`, the expression can reference that source's queries by name (e.g. Table.RowCount(Sales)), including unsaved edits of an open workbook. count_rows and profile (Table.Profile: min/max/nulls/distinct per column) scan the whole result, so they can be slow. ignore_privacy_levels=true disables the privacy firewall for this throwaway evaluation only.

NameTypeReqDescription
count_rowsboolean
expressionstringyes
ignore_privacy_levelsboolean
profileboolean
rowsinteger
source
timeout_secondsinteger

No output schema declared.

No examples provided.

evaluate_query ~131

Freshly evaluate a query, or the query only up to `step`, and return columns, types and sample rows. Use it to get real column names before apply_transform, to see what a step does to the data, or to find the step where an error first appears (evaluate step by step).

NameTypeReqDescription
count_rowsboolean
ignore_privacy_levelsboolean
profileboolean
querystringyes
rowsinteger
sourcestringyes
step
timeout_secondsinteger

No output schema declared.

No examples provided.

evaluate_steps ~109

Evaluate EVERY step of a query in one engine call and describe each one (columns, types, first `rows` rows, or the error). The fastest way to see how a query transforms its data and to find the step where an error first appears: one call instead of evaluate_query once per step.

NameTypeReqDescription
ignore_privacy_levelsboolean
querystringyes
rowsinteger
sourcestringyes
timeout_secondsinteger

No output schema declared.

No examples provided.

export_queries ~62

Write every query to `folder` as one .pq file each plus pq-manifest.json: ready to commit to git and diff in a PR. Existing .pq files in the folder are replaced.

NameTypeReqDescription
folderstringyes
sourcestringyes

No output schema declared.

No examples provided.

extract_parameter ~102

Turn a hard-coded text value (path, server, URL) into a Power Query parameter and reference it everywhere. With match_prefix, "C:\Data" also rewrites "C:\Data\sales.csv" to SourceFolder & "\sales.csv".

NameTypeReqDescription
dry_runboolean
match_prefixboolean
parameter_namestringyes
queries
sourcestringyes
valuestringyes

No output schema declared.

No examples provided.

find_in_queries ~64

Search the M of every query. scope: all | code | strings | comments. Returns query, step and line for each hit.

NameTypeReqDescription
patternstringyes
regexboolean
scopestring
sourcestringyes

No output schema declared.

No examples provided.

format_m ~58

Pretty-print M (an expression or a section document): one step per line, long calls broken at their arguments, comments kept. The output is verified token-for-token against the input, so meaning can never change.

NameTypeReqDescription
formulastringyes

No output schema declared.

No examples provided.

format_queries ~45

Format one query, or every query, in place (same guarantees as format_m).

NameTypeReqDescription
dry_runboolean
query
sourcestringyes

No output schema declared.

No examples provided.

get_query ~41

Full M code of one query plus its parsed steps, data sources, dependencies and dependents.

NameTypeReqDescription
namestringyes
sourcestringyes

No output schema declared.

No examples provided.

import_queries ~74

Load .pq files from `folder` back into `source`. mode='update' changes/adds queries; mode='sync' also deletes queries that are not in the folder.

NameTypeReqDescription
dry_runboolean
folderstringyes
modestring
sourcestringyes

No output schema declared.

No examples provided.

lint_queries ~78

Audit queries for folding breakers, hard-coded paths/servers, dead steps, brittle column lists, untyped columns, duplicated logic, orphans and cycles. Each finding carries a concrete suggestion. min_severity: info | warning | error.

NameTypeReqDescription
min_severitystring
query
sourcestringyes

No output schema declared.

No examples provided.

list_data_sources ~44

Inventory of every external source (files, folders, servers, URLs) each query reads, and whether it is hard-coded or parameterised.

NameTypeReqDescription
sourcestringyes

No output schema declared.

No examples provided.

list_queries ~42

Every query with its kind (query/function/parameter), step count, load destination, and what it depends on / is used by.

NameTypeReqDescription
sourcestringyes

No output schema declared.

No examples provided.

list_snapshots ~30

Snapshots taken automatically before each write to this source, newest first.

NameTypeReqDescription
sourcestringyes

No output schema declared.

No examples provided.

list_sources ~36

List workbooks open in Excel and models open in Power BI Desktop (both usable as `source`), and explain the other source forms.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_transforms ~36

Catalog of guided actions for apply_transform (unpivot, pivot, group_by, merge, filter, types, ...) with their params.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

m_function_help ~96

Look up the M standard library (generated from the real engine: 850+ members). Give an exact name ('Table.Group') for its signature and description, a namespace ('Table.' or 'List') to list its members, or words to search names and descriptions ('unpivot', 'split text delimiter'). Use it instead of guessing signatures.

NameTypeReqDescription
limitinteger
name_or_searchstringyes

No output schema declared.

No examples provided.

preview_query ~61

Column names and first rows of a query that is loaded to a worksheet table (open Excel workbook only). Use it to get real column names before apply_transform.

NameTypeReqDescription
namestringyes
rowsinteger
sourcestringyes

No output schema declared.

No examples provided.

refresh_query ~47

Refresh one query in an open Excel workbook and wait for it; returns the mashup engine's error text if it fails.

NameTypeReqDescription
namestringyes
sourcestringyes

No output schema declared.

No examples provided.

remove_step ~55

Delete a step and rewire the steps that used it to the step it read from.

NameTypeReqDescription
dry_runboolean
querystringyes
sourcestringyes
stepstringyes

No output schema declared.

No examples provided.

rename_query ~69

Rename a query and rewrite every reference to it in all other queries (token-aware: strings, comments and same-named columns are left alone).

NameTypeReqDescription
dry_runboolean
new_namestringyes
old_namestringyes
sourcestringyes

No output schema declared.

No examples provided.

rename_step ~58

Rename a step inside a query and every reference to it.

NameTypeReqDescription
dry_runboolean
new_namestringyes
old_namestringyes
querystringyes
sourcestringyes

No output schema declared.

No examples provided.

replace_in_queries ~118

Find and replace across all (or the listed) queries in one go, e.g. repoint a server or folder. scope: 'strings' (only inside text literals; safest, the default), 'code' (outside strings and comments), 'all'.

NameTypeReqDescription
dry_runboolean
findstringyes
ignore_caseboolean
queries
regexboolean
replacestringyes
scopestring
sourcestringyes

No output schema declared.

No examples provided.

restore_snapshot ~77

Roll back to a snapshot. With `queries`, only those are restored; otherwise the whole query set is put back (queries created since are deleted). 'latest' undoes the most recent write.

NameTypeReqDescription
dry_runboolean
queries
snapshot_idstring
sourcestringyes

No output schema declared.

No examples provided.

set_query ~94

Replace a query's M (or create it with create_if_missing). Rejects unbalanced brackets/strings before writing. For standard actions prefer apply_transform; for renames prefer rename_query / rename_step.

NameTypeReqDescription
create_if_missingboolean
descriptionstring
dry_runboolean
formulastringyes
namestringyes
sourcestringyes

No output schema declared.

No examples provided.

validate_m ~119

Check M before using it: syntax errors with line/column and a plain-English cause (missing comma between steps, unquoted step name, if without else ...), unknown steps/queries/functions with did-you-mean, and wrong argument counts for library functions. Pass `formula` (an expression or a whole section document); add `source` so its query names are known. Or pass `source` (+ optional `query`) alone to validate what is already there.

NameTypeReqDescription
formula
query
source

No output schema declared.

No examples provided.

Common questions

What is the letin: Power Query (M) MCP server?

letin: Power Query (M) is an MCP server listed in the public MCP registry as io.github.S-CurveLabs/letin. Inspect, refactor, lint, run and version Power Query (M) in Excel workbooks and Power BI projects. This page covers its PyPI package (letin).

Is the letin: Power Query (M) MCP server safe to use?

letin: Power Query (M) scores 49 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 22 September 2026. 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 letin: Power Query (M) MCP server expose?

letin: Power Query (M) exposes 31 tools: list_sources, list_queries, get_query, dependency_graph, list_data_sources, and 26 more. Their descriptions and schemas cost roughly 2,372 tokens of context every time the server is loaded.

Is the letin: Power Query (M) MCP server still maintained?

letin: Power Query (M) is still listed as active in the MCP registry. We last reached this channel on 22 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.