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.

io.github.DownAtTheBottomOfTheMoleHole/megalinter

NPM · @DOWNATTHEBOTTOMOFTHEMOLEHOLE/MEGALINTER-MCP-SERVER

MCP server for running Ox Security MegaLinter via mega-linter-runner

+4 this week 94 Trust /100

Last scanned (7 hours ago)

Scores higher than 97% of npm servers

Category Testing and QA

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 Security98
  • 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
  • 30 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to DownAtTheBottomOfTheMoleHole/megalinter-mcp). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 0 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability70
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 1462 tokens (~97/item across 15 items; 15 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
  • Stability observed for 29 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 15 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 15 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
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.

  • 5 Nov 26 +1

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

  • 4 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 3 Nov 26 −12
    • Malware scan: pass → unverified ▼ security
    • CVE-2026-118663 no longer affects this package ▲ security
    • CVE-2026-111767 no longer affects this package ▲ security
    • CVE-2026-104850 no longer affects this package ▲ security
    • CVE-2026-111768 no longer affects this package ▲ security
    • CVE-2026-111771 no longer affects this package ▲ security
    • CVE-2026-111769 no longer affects this package ▲ security
    • GHSA-f897-62hf-6gxq no longer affects this package ▲ security
    • Known CVEs: fail → pass ▲ security
    • Schema quality: 807 → 1462 ▼ functional
    • Stability: pass → 0.90 functional
    • Package version: 3.0.2 → 4.0.0 functional
  • 29 Oct 26 0
    • CVE-2026-118663 affects this package: high ▼ security
  • 28 Oct 26 +1
    • GHSA-f897-62hf-6gxq affects this package: high ▼ security
    • Stability: 0.97 → pass security
  • 27 Oct 26 −1
    • Stability: pass → 0.97 functional
  • 21 Oct 26 +1
    • CVE-2026-111771 affects this package: high ▼ security
    • CVE-2026-111768 affects this package: high ▼ security
    • CVE-2026-111769 affects this package: high ▼ security
    • CVE-2026-111767 affects this package: high ▼ security
    • Stability: 0.97 → pass security
  • 20 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 5 Nov 2026 · Analysed npm/@downatthebottomofthemolehole/megalinter-mcp-server@4.0.0

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 DownAtTheBottomOfTheMoleHole/megalinter-mcp
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/DownAtTheBottomOfTheMoleHole/megalinter-mcp/.github/workflows/publish-mcp.yml@refs/heads/main
Rekor log index 3664317287
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:ed2e59f1af816cc29aceadb06289d133490d199f8291f72232559ac7053f09c72707de5227fb5c29c177b906df8c8b26686543823284db1e47cb482af

Background: How many MCP packages publish verified provenance →

Dependencies 92 packages
Packages resolved 92
Stale 30
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 15 exposed · ~1,462 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
help_quick ~26

Ultra-short alias for context-aware help. Same as megalinter_help_quick.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

megalinter_get_issue_summary ~86

Analyze and summarize issues from MegaLinter reports by severity, linter, and category. Enables filtering and targeted remediation.

NameTypeReqDescription
linterFilterstring–Filter issues by specific linter name.
reportsPathstring–Path to the reports directory. Defaults to megalinter-reports.
severityFilterstring–Filter issues by severity level.

No output schema declared.

No examples provided.

megalinter_get_linters ~79

Discover available linters by language, security category, or auto-fix capability.

NameTypeReqDescription
autoFixOnlyboolean–Return only linters that support automatic fixes.
languagestring–Filter by programming language (e.g., python, javascript, terraform).
securityOnlyboolean–Return only security-focused linters.

No output schema declared.

No examples provided.

megalinter_get_reporters ~24

List all available MegaLinter reporters and their configuration options.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

megalinter_get_security_info ~36

Get comprehensive information about security-focused linters organized by category (SAST, secrets, supply-chain, container, infrastructure).

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

megalinter_get_security_recommendations ~58

Generate security-focused recommendations based on active linters and common threat categories (SAST, secrets, container, infrastructure).

NameTypeReqDescription
reportsPathstring–Path to the reports directory. Defaults to megalinter-reports.

No output schema declared.

No examples provided.

megalinter_help_quick ~34

Get context-aware help and examples based on your current repository. Suggests relevant commands for detected languages and frameworks.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

megalinter_list_flavors ~20

List commonly used MegaLinter flavors.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

megalinter_parse_reports ~70

Parse MegaLinter JSON or SARIF reports from the reports directory. Returns structured report data for analysis.

NameTypeReqDescription
reportTypestring–Type of report to parse. Defaults to json.
reportsPathstring–Path to the reports directory. Defaults to megalinter-reports.

No output schema declared.

No examples provided.

megalinter_quick_action ~382

Interactive shortcut tool for short requests (for example: quick scan, security scan, summarise errors, list python security linters).

NameTypeReqDescription
actionstring–Optional explicit action. Use this for deterministic quick workflows.
autoFixOnlyboolean–Filter linter-list requests to auto-fix linters.
fixboolean–Force auto-fix for scan requests.
flavorstring–Optional flavour override for scan requests (e.g., javascript, python, security).
languagestring–Language filter for linter-list requests. For scans, this maps to a flavor hint (e.g., python -> python, typescript -> javascript).
linterFilterstring–Linter filter for summary requests.
reportTypestring–Report format for parse requests. Defaults to json unless sarif is requested.
reportsPathstring–Report directory for parse, summary, and recommendation requests.
requeststring–Short instruction. Examples: quick scan, full scan, security scan, summarise errors, parse sarif report, write config.
scanModestring–Scan preset when action is scan (or request implies a scan).
securityOnlyboolean–Filter linter-list requests to security linters. For scans, forces security flavor.
severitystring–Severity filter for summary requests.
summaryOnlyboolean–Use concise output for scan requests. Set false for full logs.
targetstring–Directory to scan for run requests. Defaults to .
targetPathstring–Output file path for write-config requests. Defaults to .mega-linter.yml.
timeoutMinutesnumber–Run timeout in minutes for scan requests.
workingDirectorystring–Directory where commands run. Defaults to current process directory.

No output schema declared.

No examples provided.

megalinter_run ~343

Run Ox Security MegaLinter using mega-linter-runner with full low-level control. For short prompts, use megalinter_quick_action.

NameTypeReqDescription
configFilestring–Path to .mega-linter.yml file.
containerNamestring–Optional Docker container name.
disableLintersstring–Comma-separated list of linters to disable.
envstring–Environment variable string passed to --env (for example: DISABLE_LINTERS=SPELL_CSPELL,MARKDOWN_MARKDOWNLINT).
extraArgsarray–Additional CLI arguments to append.
fixboolean–Apply auto-fixes.
flavorstring–MegaLinter flavor.
helpboolean–Show mega-linter-runner help.
imagestring–Optional full Docker image override.
installboolean–Generate MegaLinter starter config files.
lintChangedFilesOnlyboolean–If true, sets VALIDATE_ALL_CODEBASE=false to lint only changed files.
pathstring–Directory path to lint.
releasestring–MegaLinter Docker image tag.
removeContainerboolean–Remove container after completion.
reportsPathstring–Directory where reports are written.
runnerVersionstring–mega-linter-runner npm version. Use 'latest' or a specific version.
summaryOnlyboolean–Return concise logs instead of full stdout/stderr output.
timeoutSecondsnumber–Command timeout in seconds.
workingDirectorystring–Directory where the command is executed. Defaults to current process directory.

No output schema declared.

No examples provided.

megalinter_write_config ~117

Generate a minimal .mega-linter.yml configuration file.

NameTypeReqDescription
applyFixesstring–Value for APPLY_FIXES (none, all, or linter list).
disableLintersarray–Optional list for DISABLE_LINTERS.
flavorSuggestionsboolean–Set FLAVOR_SUGGESTIONS.
showElapsedTimeboolean–Set SHOW_ELAPSED_TIME.
targetPathstring–Output path for the MegaLinter config file. Defaults to .mega-linter.yml

No output schema declared.

No examples provided.

parse ~51

Ultra-short alias for report parsing. Same as megalinter_quick_action with action='parse'.

NameTypeReqDescription
reportTypestring–Type of report to parse.
reportsPathstring–Reports directory path.

No output schema declared.

No examples provided.

scan ~73

Ultra-short alias for quick scan. Same as megalinter_quick_action with action='scan'.

NameTypeReqDescription
languagestring–Target language to map into a scan flavor (e.g., python, javascript, terraform).
scanModestring–Scan preset mode.
summaryOnlyboolean–Return concise output.

No output schema declared.

No examples provided.

summary ~63

Ultra-short alias for error summary. Same as megalinter_quick_action with action='summary'.

NameTypeReqDescription
linterFilterstring–Filter by linter name.
reportsPathstring–Reports directory path.
severitystring–Filter by severity level.

No output schema declared.

No examples provided.

Install

How do I install the io.github.DownAtTheBottomOfTheMoleHole/megalinter MCP server?

io.github.DownAtTheBottomOfTheMoleHole/megalinter runs locally as an npm package, launched with npx -y @downatthebottomofthemolehole/megalinter-mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @downatthebottomofthemolehole/megalinter-mcp-server

# add to Claude Code
claude mcp add downatthebottomofthemolehole-megalinter -- npx -y @downatthebottomofthemolehole/megalinter-mcp-server
Common questions

What is the io.github.DownAtTheBottomOfTheMoleHole/megalinter MCP server?

io.github.DownAtTheBottomOfTheMoleHole/megalinter is an MCP server listed in the public MCP registry as io.github.DownAtTheBottomOfTheMoleHole/megalinter. MCP server for running Ox Security MegaLinter via mega-linter-runner. This page covers its npm package (@downatthebottomofthemolehole/megalinter-mcp-server).

Is the io.github.DownAtTheBottomOfTheMoleHole/megalinter MCP server safe to use?

io.github.DownAtTheBottomOfTheMoleHole/megalinter scores 94 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 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 io.github.DownAtTheBottomOfTheMoleHole/megalinter MCP server expose?

io.github.DownAtTheBottomOfTheMoleHole/megalinter exposes 15 tools: megalinter_quick_action, megalinter_run, megalinter_write_config, megalinter_list_flavors, megalinter_get_linters, and 10 more. Their descriptions and schemas cost roughly 1,462 tokens of context every time the server is loaded.

Is the io.github.DownAtTheBottomOfTheMoleHole/megalinter MCP server still maintained?

io.github.DownAtTheBottomOfTheMoleHole/megalinter is still listed as active in the MCP registry. We last reached this channel on 5 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.DownAtTheBottomOfTheMoleHole/megalinter MCP server under?

io.github.DownAtTheBottomOfTheMoleHole/megalinter declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.