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.

Gretl MCP

NPM · GRETL-MCP

Run Hansl/Gretl econometrics workflows via MCP with GUI launch and artifacts.

Available components

0 this week 76 Trust /100

Last scanned (15 hours ago)

Scores higher than 53% of npm servers

Category Data and Analytics

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 Security81
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 31 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 189 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability60
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 2115 tokens (~176/item across 12 items; 12 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage89
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 67% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

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.

  • 19 Nov 26 +1
    • Stability: 0.97 → pass security
  • 18 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 12 Nov 26 +1
    • Stability: 0.97 → pass security
  • 10 Nov 26 −1
    • Stability: pass → 0.93 functional
  • 4 Nov 26 +1
    • Stability: 0.97 → pass security
  • 3 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 28 Oct 26 +1
    • Stability: 0.97 → pass security
  • 27 Oct 26 −1
    • Stability: pass → 0.97 functional
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 21 Nov 2026 · Analysed npm/gretl-mcp@0.2.1

Provenance No attestation

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

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Vulnerabilities 1 finding
ID CVE Severity Vector Fix available
GHSA-mrhx-c7xc-m3w5 CVE-2023-54404 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 93 packages
Packages resolved 93
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 12 exposed · ~2,115 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
gretl_capabilities ~126

List Gretl commands, built-in functions, and package-management help from the installed Gretl version.

NameTypeReqDescription
displayInGretlboolean–Open the generated help script in Gretl GUI. Defaults to false for this reference tool.
gretlCliPathstring––
gretlGuiPathstring––
includeFunctionsboolean–Include Gretl's built-in accessors and functions from help functions.
includePackageHelpboolean–Include help for pkg and makepkg.
timeoutSecondsinteger––

No output schema declared.

No examples provided.

gretl_dataset_summary ~165

Open a Gretl-supported dataset file, return summary statistics, and open the same workflow in Gretl GUI by default.

NameTypeReqDescription
datasetPathstringyesPath to a CSV, gdt, Excel, Stata, SPSS, or other Gretl-supported dataset.
displayInGretlboolean–Open a visible Gretl GUI script window for this workflow. Defaults to true outside CI.
gretlCliPathstring––
gretlGuiPathstring––
guiNewInstanceboolean––
requireGuiboolean–Require the visible Gretl GUI to open for this workflow. Defaults to true outside CI.
safeModeboolean––
timeoutSecondsinteger––

No output schema declared.

No examples provided.

gretl_gui_launch ~201

Launch the visible Gretl desktop GUI, optionally opening a local dataset/script or running a provided script on startup.

NameTypeReqDescription
englishboolean–Force Gretl GUI to use English.
filePathstring–Optional local dataset or script file to open in the Gretl GUI.
gretlGuiPathstring–Optional explicit path to gretl or gretl.exe.
newInstanceboolean–Launch a new Gretl GUI instance instead of reusing an existing one.
runScriptboolean–When filePath points to a script, launch Gretl with --run filePath.
safeModeboolean–When script is provided, block shell-like commands and absolute file reads/writes.
scriptstring–Optional Gretl/Hansl script to write and open with --run in the GUI.
workspaceRootstring–Optional directory where GUI script workspaces are created.

No output schema declared.

No examples provided.

gretl_gui_version ~75

Return the installed Gretl GUI version by running gretl.exe --version.

NameTypeReqDescription
gretlGuiPathstring–Optional explicit path to gretl or gretl.exe.
timeoutSecondsinteger–Maximum time to wait for gretl.exe --version. Defaults to 10 seconds.

No output schema declared.

No examples provided.

gretl_help ~138

Ask Gretl for command help, for example ols, summary, open, arima, or gnuplot. By default this also requires opening the help workflow in the visible Gretl GUI.

NameTypeReqDescription
commandNamestringyesGretl command name.
displayInGretlboolean–Open a visible Gretl GUI script window for this help request. Defaults to true outside CI.
gretlCliPathstring––
gretlGuiPathstring––
requireGuiboolean–Require the visible Gretl GUI to open for this workflow. Defaults to true outside CI.

No output schema declared.

No examples provided.

gretl_make_package ~214

Build a Gretl function package (.gfn or .zip) using the native makepkg command. By default this also requires opening the generated workflow in the visible Gretl GUI.

NameTypeReqDescription
displayInGretlboolean–Open the generated makepkg script in Gretl GUI. Defaults to true outside CI.
gretlCliPathstring––
gretlGuiPathstring––
guiNewInstanceboolean––
indexboolean–Write the auxiliary package XML index file.
keepWorkspaceboolean––
packagePathstringyesOutput path ending in .gfn or .zip.
quietboolean–Use makepkg --quiet.
requireGuiboolean–Require the visible Gretl GUI to open for this workflow. Defaults to true outside CI.
timeoutSecondsinteger––
translationsboolean–Write the auxiliary i18n C strings file.
workspaceRootstring––

No output schema declared.

No examples provided.

gretl_ols ~179

Open a dataset, estimate an OLS model, and open the same workflow in Gretl GUI by default.

NameTypeReqDescription
datasetPathstringyesPath to a Gretl-supported dataset.
dependentVariablestringyesDependent variable name.
displayInGretlboolean–Open a visible Gretl GUI script window for this workflow. Defaults to true outside CI.
gretlCliPathstring––
gretlGuiPathstring––
guiNewInstanceboolean––
includeConstantboolean––
independentVariablesarrayyesIndependent variable names.
requireGuiboolean–Require the visible Gretl GUI to open for this workflow. Defaults to true outside CI.
safeModeboolean––
timeoutSecondsinteger––

No output schema declared.

No examples provided.

gretl_package ~262

Install, query, run samples for, unload, remove, or index Gretl function/data packages using the native pkg command. By default this also requires opening the generated workflow in the visible Gretl GUI.

NameTypeReqDescription
actionstringyesGretl pkg action to perform.
displayInGretlboolean–Open the generated package command script in Gretl GUI. Defaults to true outside CI.
gretlCliPathstring––
gretlGuiPathstring––
guiNewInstanceboolean––
keepWorkspaceboolean––
localboolean–Use pkg --local for a local .gfn or .zip package file.
packageNamestring–Package name, local package path, URL, or addons for index. Required except index defaults to addons.
quietboolean–Use pkg --quiet.
requireGuiboolean–Require the visible Gretl GUI to open for this workflow. Defaults to true outside CI.
stagingboolean–Use pkg --staging for package installs from Gretl staging.
timeoutSecondsinteger––
verboseboolean–Use pkg --verbose.
workspaceRootstring––

No output schema declared.

No examples provided.

gretl_run_commands ~246

Run one or more raw Gretl command lines. By default this also requires opening the same workflow in the visible Gretl GUI.

NameTypeReqDescription
commandsarrayyesGretl command lines to run in order.
displayInGretlboolean–Open the generated command script in the visible Gretl GUI. Defaults to true outside CI.
gretlCliPathstring–Optional explicit path to gretlcli or gretlcli.exe.
gretlGuiPathstring–Optional explicit path to gretl or gretl.exe.
guiNewInstanceboolean–Open a new Gretl GUI instance for the visible script.
keepWorkspaceboolean–Keep the run workspace so generated artifacts remain available.
requireGuiboolean–Require the visible Gretl GUI to open for this workflow. Defaults to true outside CI.
safeModeboolean–When true, blocks shell-like commands and absolute file writes.
timeoutSecondsinteger–Maximum runtime in seconds. Defaults to 30, max 300.
workspaceRootstring–Optional directory where run workspaces are created.

No output schema declared.

No examples provided.

gretl_run_script ~250

Run any Gretl/Hansl script through gretlcli. By default this also requires opening the same workflow in the visible Gretl GUI.

NameTypeReqDescription
displayInGretlboolean–Open a visible Gretl GUI script window for this run. Defaults to true outside CI.
gretlCliPathstring–Optional explicit path to gretlcli or gretlcli.exe.
gretlGuiPathstring–Optional explicit path to gretl or gretl.exe.
guiNewInstanceboolean–Open a new Gretl GUI instance for the visible script.
keepWorkspaceboolean–Keep the run workspace so generated artifacts remain available.
requireGuiboolean–Require the visible Gretl GUI to open for this workflow. Defaults to true outside CI.
safeModeboolean–When true, blocks shell-like commands and absolute file writes.
scriptstringyesGretl/Hansl script to run.
timeoutSecondsinteger–Maximum runtime in seconds. Defaults to 30, max 300.
workspaceRootstring–Optional directory where run workspaces are created.

No output schema declared.

No examples provided.

gretl_run_script_file ~211

Run an existing local Gretl .inp script file with gretlcli. By default this also requires opening the same workflow in the visible Gretl GUI.

NameTypeReqDescription
displayInGretlboolean–Open the script file in the visible Gretl GUI after running. Defaults to true outside CI.
gretlCliPathstring––
gretlGuiPathstring––
guiNewInstanceboolean––
requireGuiboolean–Require the visible Gretl GUI to open for this workflow. Defaults to true outside CI.
safeModeboolean–When true, validates the script before running it.
scriptOptnumber–Optional numeric value passed to Gretl as --scriptopt.
scriptPathstringyesPath to an existing local Gretl .inp script.
timeoutSecondsinteger––
workingDirectorystring–Working directory for the script. Defaults to the script file directory.

No output schema declared.

No examples provided.

gretl_version ~48

Return the installed Gretl version by running gretlcli.

NameTypeReqDescription
gretlCliPathstring–Optional explicit path to gretlcli or gretlcli.exe.

No output schema declared.

No examples provided.

Install

How do I install the Gretl MCP server?

Gretl MCP runs locally as an npm package, launched with npx -y gretl-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · gretl-mcp

# add to Claude Code
claude mcp add ondrejlapes-gretl-mcp -- npx -y gretl-mcp
Common questions

What is the Gretl MCP server?

Gretl MCP is listed in the public MCP registry as io.github.OndrejLapes/gretl-mcp. Run Hansl/Gretl econometrics workflows via MCP with GUI launch and artifacts. This page covers its npm package (gretl-mcp).

Is the Gretl MCP server safe to use?

Gretl MCP scores 76 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 21 November 2026. It declares no install or post-install scripts. 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 Gretl MCP server expose?

Gretl MCP exposes 12 tools: gretl_version, gretl_gui_version, gretl_gui_launch, gretl_run_script, gretl_run_commands, and 7 more. Their descriptions and schemas cost roughly 2,115 tokens of context every time the server is loaded.

Is the Gretl MCP server still maintained?

Gretl MCP is still listed as active in the MCP registry. We last reached this channel on 21 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 Gretl MCP server under?

Gretl MCP declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the Gretl MCP server?

VerifyMCP ran 16 checks on Gretl MCP, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.