B+

npm:gretl-mcp

https://www.npmjs.com/package/gretl-mcp
87/100 · MCP Trust Grade · checked 3h ago · MCP 0.2.1

What it offers — 12 tools · Developer Tools

gretl_version

Return the installed Gretl version by running gretlcli.

gretl_gui_version

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

gretl_gui_launch

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

gretl_run_script

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

gretl_run_commands

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

gretl_run_script_file

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

gretl_capabilities

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

gretl_package

Install, query, run samples for, unload, remove, or index Gretl function/data packages using the native pkg command. By default this also requires ope

gretl_make_package

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

gretl_help

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_dataset_summary

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

gretl_ols

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

Spec / packaging20%100
Security (OWASP MCP)30%70
Maintenance / popularity20%92
Tool hygiene15%95
Transparency / provenance15%90

Findings

INFO Static analysis of npm package gretl-mcp@0.2.1 (stdio server — no remote endpoint). Reliability/behavioral signals require running it; not measured.
Grade another server

We re-grade npm:gretl-mcp on a schedule and alert your Slack/webhook the moment its tools change or its grade drops — rug-pull insurance for the connection.

Share this report card

A 1200×630 card with the grade + audit — drop it in a post, Slack, or your repo.

MCP Trust report card — npm:gretl-mcp grade B+
Share on X Open card image

Embed this grade

A live badge — it re-verifies itself and shows current stability. Static scorecards can't. Paste it in your README or site to show users you're independently audited.

MCP Trust Grade B+ · wmcp.sh
[![MCP Trust Grade B+](https://wmcp.sh/mcp/grade/npm%3Agretl-mcp/badge.svg)](https://wmcp.sh/mcp/grade/npm%3Agretl-mcp)
<a href="https://wmcp.sh/mcp/grade/npm%3Agretl-mcp"><img src="https://wmcp.sh/mcp/grade/npm%3Agretl-mcp/badge.svg" alt="MCP Trust Grade B+ · wmcp.sh"></a>

Agents: check this before connecting

Add the wmcp.sh trust oracle as an MCP server and call grade_mcp_server / check_mcp_drift in your agent's pre-connection gate:

https://wmcp.sh/mcp/trust
How this grade is computed. An open, independent rubric — Spec conformance (20%), Security mapped to the OWASP MCP Top 10 (30%), Reliability (20%), Tool hygiene (15%), Transparency (15%) — run by connecting to the server and inspecting its real MCP surface. The grade is free and identical whether or not the operator pays. v1 uses static + spec signals from a single connection; continuous uptime, real latency, and annotation-truthing (declared readOnly vs observed behavior) layer on via the wmcp.sh proxy.