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 · SCANNED SEP 20

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

0 this week 94 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 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
  • 31 of 95 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 196 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability75
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 807 tokens (~89/item across 9 items; 9 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
  • Stability observed for 27 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 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 9 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
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
// .cursor/mcp.json
{
  "mcpServers": {
    "downatthebottomofthemolehole-megalinter": {
      "command": "npx",
      "args": [
        "-y",
        "@downatthebottomofthemolehole/megalinter-mcp-server"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "downatthebottomofthemolehole-megalinter": {
      "command": "npx",
      "args": [
        "-y",
        "@downatthebottomofthemolehole/megalinter-mcp-server"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add downatthebottomofthemolehole-megalinter -- npx -y @downatthebottomofthemolehole/megalinter-mcp-server
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "downatthebottomofthemolehole-megalinter": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@downatthebottomofthemolehole/megalinter-mcp-server"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add downatthebottomofthemolehole-megalinter --command npx --arg -y --arg @downatthebottomofthemolehole/megalinter-mcp-server
# ~/.hermes/config.yaml
mcp_servers:
  downatthebottomofthemolehole-megalinter:
    command: "npx"
    args: ["-y", "@downatthebottomofthemolehole/megalinter-mcp-server"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "downatthebottomofthemolehole-megalinter": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@downatthebottomofthemolehole/megalinter-mcp-server"
      ]
    }
  }
}
# add to Vellum
assistant mcp add downatthebottomofthemolehole-megalinter -t stdio -c npx -a -y @downatthebottomofthemolehole/megalinter-mcp-server
// mcp.json
{
  "mcpServers": {
    "downatthebottomofthemolehole-megalinter": {
      "command": "npx",
      "args": [
        "-y",
        "@downatthebottomofthemolehole/megalinter-mcp-server"
      ]
    }
  }
}
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 Sept 26 +1

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

  • 18 Sept 26 +1

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

  • 17 Sept 26 +1
    • Security disclosure: unverified → pass functional
  • 16 Sept 26 −4
    • Security disclosure: pass → unverified functional
    • Stability: pass → 0.77 functional
  • 15 Sept 26 +1
    • Stability: 0.97 → pass security
  • 12 Sept 26 +1

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

  • 10 Sept 26 +1
    • Security disclosure: unverified → pass functional
  • 9 Sept 26 −3
    • Security disclosure: pass → unverified functional
    • Stability: pass → 0.80 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 20 Sept 2026 · Analysed npm/@downatthebottomofthemolehole/megalinter-mcp-server@3.0.2

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 1058594916
Predicate type https://slsa.dev/provenance/v1
Subject digest sha512:51ffcce5fa119884260c545e521381294412e2f12c432a5bd0992caecbe5fbf00d3c18d10374064c5f057fb374d8b3095e280171036ba449d46c0c160

Background: How many MCP packages publish verified provenance →

Dependencies 95 packages
Packages resolved 95
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 9 exposed · ~807 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
megalinter_get_issue_summary ~86

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

NameTypeReqDescription
linterFilterstringFilter issues by specific linter name.
reportsPathstringPath to the reports directory. Defaults to megalinter-reports.
severityFilterstringFilter 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
autoFixOnlybooleanReturn only linters that support automatic fixes.
languagestringFilter by programming language (e.g., python, javascript, terraform).
securityOnlybooleanReturn 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
reportsPathstringPath to the reports directory. Defaults to megalinter-reports.

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
reportTypestringType of report to parse. Defaults to json.
reportsPathstringPath to the reports directory. Defaults to megalinter-reports.

No output schema declared.

No examples provided.

megalinter_run ~317

Run Ox Security MegaLinter using mega-linter-runner. Works locally or in any CI/CD environment.

NameTypeReqDescription
configFilestringPath to .mega-linter.yml file.
containerNamestringOptional Docker container name.
disableLintersstringComma-separated list of linters to disable.
envstringEnvironment variable string passed to --env (for example: DISABLE_LINTERS=SPELL_CSPELL,MARKDOWN_MARKDOWNLINT).
extraArgsarrayAdditional CLI arguments to append.
fixbooleanApply auto-fixes.
flavorstringMegaLinter flavor.
helpbooleanShow mega-linter-runner help.
imagestringOptional full Docker image override.
installbooleanGenerate MegaLinter starter config files.
lintChangedFilesOnlybooleanIf true, sets VALIDATE_ALL_CODEBASE=false to lint only changed files.
pathstringDirectory path to lint.
releasestringMegaLinter Docker image tag.
removeContainerbooleanRemove container after completion.
reportsPathstringDirectory where reports are written.
runnerVersionstringmega-linter-runner npm version. Use 'latest' or a specific version.
timeoutSecondsnumberCommand timeout in seconds.
workingDirectorystringDirectory 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
applyFixesstringValue for APPLY_FIXES (none, all, or linter list).
disableLintersarrayOptional list for DISABLE_LINTERS.
flavorSuggestionsbooleanSet FLAVOR_SUGGESTIONS.
showElapsedTimebooleanSet SHOW_ELAPSED_TIME.
targetPathstringOutput path for the MegaLinter config file. Defaults to .mega-linter.yml

No output schema declared.

No examples provided.

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 20 September 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 9 tools: megalinter_run, megalinter_write_config, megalinter_list_flavors, megalinter_get_linters, megalinter_get_security_info, and 4 more. Their descriptions and schemas cost roughly 807 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 20 September 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.