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.

Lugh

NPM · LUGH-LANG

Write, check and dry-run Lugh agent programs, with policy, budgets and approvals enforced.

Available components

+18 this week 83 Trust /100

Last scanned (21 hours ago)

Scores higher than 73% of npm servers

Category Developer Tools

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 Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to Ashutosh3142857/lugh-lang). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 2 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability69
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 401 tokens (~80/item across 5 items; 5 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
  • Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 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.

  • 20 Nov 26 +1

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

  • 19 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 18 Nov 26 −13
    • Malware scan: pass → unverified ▼ security
    • Stability: unverified → 0.13 ▲ functional
    • Package version: 0.7.1 → 0.7.3 functional
    • Package version: 0.7.1 → 0.7.2 functional
  • 15 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 14 Nov 26 65

    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 21 Nov 2026 · Analysed npm/lugh-lang@0.7.3

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 npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo Ashutosh3142857/lugh-lang
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/Ashutosh3142857/lugh-lang/.github/workflows/release.yml@refs/heads/main
Rekor log index 3967155553
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:a3eec0cd23fc9a1ded48347edea7e6d3608dc36be576be69b5bf0121626da9c4e8dbeacff8d46c0ee94b634bb416aab0e68855a34ac9773e2d0af396b

Background: How many MCP packages publish verified provenance →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 5 exposed · ~321 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
lugh_check ~57

Compile a Lugh program without running it. Reports syntax errors, unknown functions and adapters, and counts goals, tests, routes and pages.

NameTypeReqDescription
codestringyesA complete Lugh program, starting with `agent <Name>`.

No output schema declared.

No examples provided.

lugh_reference ~44

Syntax and semantics of Lugh, a programming language for AI agents where permissions (policy), budgets and human approval are part of the code. Read this before writing a program.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

lugh_run ~131

Run a Lugh program's goals in a sandbox. fs, http, mcp and shell act on a simulated world (see lugh_sandbox), but every call passes the real policy gate and budgets. Returns the output and a policy log of every action and its decision (allowed, approved, declined, denied). Use it to show a person exactly what an agent would do before it runs for real.

NameTypeReqDescription
approvalsstring–How to answer `ask human` and policy approvals. Default approve.
codestringyesA complete Lugh program, starting with `agent <Name>`.

No output schema declared.

No examples provided.

lugh_sandbox ~40

List the simulated files, HTTP endpoints, MCP servers (with each tool's effect) and shell commands that programs run by lugh_run can use.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

lugh_test ~49

Run the `test` blocks of a Lugh program in the sandbox and report passes and failures.

NameTypeReqDescription
codestringyesA complete Lugh program, starting with `agent <Name>`.

No output schema declared.

No examples provided.

Install

How do I install the Lugh MCP server?

Lugh runs locally as an npm package, launched with npx -y lugh-lang 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 · lugh-lang

# add to Claude Code
claude mcp add ashutosh3142857-lugh -- npx -y lugh-lang mcp
Common questions

What is the Lugh MCP server?

Lugh is an MCP server listed in the public MCP registry as io.github.Ashutosh3142857/lugh. Write, check and dry-run Lugh agent programs, with policy, budgets and approvals enforced. This page covers its npm package (lugh-lang).

Is the Lugh MCP server safe to use?

Lugh scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. It declares no install or post-install scripts. 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 Lugh MCP server expose?

Lugh exposes 5 tools: lugh_reference, lugh_check, lugh_run, lugh_test, lugh_sandbox. Their descriptions and schemas cost roughly 321 tokens of context every time the server is loaded.

Is the Lugh MCP server still maintained?

Lugh 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 Lugh MCP server under?

Lugh 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 Lugh MCP server?

VerifyMCP ran 16 checks on Lugh, 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.