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.

BACH CodeCommander

NPM · BACH-CODECOMMANDER-MCP

17 tools for code analysis, JSON repair, encoding fix, format conversion, diff, and regex.

0 this week 71 Trust /100

Last scanned (19 hours ago)

Scores higher than 42% 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 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 104 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency13
  • Repository check failed: the declared repository URL redirects; it must resolve directly. See how to fix → View diagnostics → Fail
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • Clear OSI-approved license (MIT).Pass
  • Maintenance check failed: the publisher has marked this version as deprecated on the registry, telling users to stop installing it. See how to fix → Fail
  • Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability68
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 1706 tokens (~94/item across 18 items; 18 tools + 0 resources), lean.Pass
  • 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 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 18 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 18 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 (15)

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

Checks we could not complete (1)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Security disclosure in Provenance & TransparencySecurity-disclosure policy not yet verified: we couldn't inspect the source repository.

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 0
    • Stability: 0.97 → pass security
  • 19 Nov 26 0
    • Stability: pass → 0.97 functional
  • 13 Nov 26 0
    • Stability: 0.97 → pass security
  • 12 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.

  • 11 Nov 26 −1
    • Stability: pass → 0.93 functional
  • 6 Nov 26 −1
    • Security disclosure: pass → unverified ▼ functional
  • 5 Nov 26 +1
    • Stability: 0.97 → pass security
  • 4 Nov 26 +1
    • Security disclosure: unverified → pass ▲ 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/bach-codecommander-mcp@1.3.0

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 104 packages
Packages resolved 104
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 18 exposed · ~1,706 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
cc_analyze_code ~68

Analyzes a Python file: classes, functions, imports, metrics. Args: - path (string): Path to the Python file Returns: - Classes with methods, functions, import analysis, LOC, complexity

NameTypeReqDescription
pathstringyesPath to the Python file

No output schema declared.

No examples provided.

cc_analyze_methods ~86

Detailed method analysis of a Python file. Args: - path (string): Path to the Python file - class_name (string, optional): Only methods of this class Returns: - Methods with parameters, decorators, complexity, data flow

NameTypeReqDescription
class_namestring–Only analyze this class
pathstringyesPath to the Python file

No output schema declared.

No examples provided.

cc_cleanup_file ~178

Cleans up source code files: BOM, NUL bytes, trailing whitespace, line endings. Args: - path (string): Path to the file - remove_bom (boolean): Remove BOM - remove_trailing_whitespace (boolean): Trailing whitespace - normalize_line_endings (string): "lf" | "crlf" - remove_nul_bytes (boolean): Remove NUL bytes - dry_run (boolean): Preview only

NameTypeReqDescription
dry_runboolean–Preview only
normalize_line_endingsstring–Line endings
pathstringyesPath to the file
remove_bomboolean–Remove BOM
remove_nul_bytesboolean–NUL bytes
remove_trailing_whitespaceboolean–Trailing whitespace

No output schema declared.

No examples provided.

cc_convert_format ~182

Converts between JSON, CSV, INI, YAML, TOML, XML, and TOON formats. Args: - input_path (string): Source file - output_path (string): Target file - input_format (string): "json" | "csv" | "ini" | "yaml" | "toml" | "xml" | "toon" - output_format (string): "json" | "csv" | "ini" | "yaml" | "toml" | "xml" | "toon" - json_indent (number): JSON indentation

NameTypeReqDescription
input_formatstringyesInput format
input_pathstringyesSource file
json_indentinteger–JSON indentation
output_formatstringyesOutput format
output_pathstringyesTarget file

No output schema declared.

No examples provided.

cc_diagnose_imports ~65

Diagnoses import issues: missing modules, circular imports, unused imports. Args: - path (string): Path to the Python file Detects: Missing modules, suspected circular imports, import issues

NameTypeReqDescription
pathstringyesPath to the Python file

No output schema declared.

No examples provided.

cc_diff_files ~64

Vergleicht zwei Dateien und zeigt Unterschiede im Unified-Diff-Format

NameTypeReqDescription
context_linesinteger–Number of context lines (default: 3)
file_astringyesPath to first file
file_bstringyesPath to second file

No output schema declared.

No examples provided.

cc_extract_classes ~82

Extracts Python classes and functions from a file as separate text blocks. Args: - path (string): Path to the Python file - output_dir (string, optional): Output directory (otherwise display only) Useful for code review and documentation.

NameTypeReqDescription
output_dirstring–Output directory
pathstringyesPath to the Python file

No output schema declared.

No examples provided.

cc_fix_encoding ~103

Repairs encoding errors (Mojibake, double UTF-8). Args: - path (string): Path to the file - dry_run (boolean): Preview only - create_backup (boolean): Create backup Repairs 27+ Mojibake patterns (German, French, Spanish).

NameTypeReqDescription
create_backupboolean–Create backup
dry_runboolean–Preview only
pathstringyesPath to the file

No output schema declared.

No examples provided.

cc_fix_json ~99

Automatically repairs common JSON errors. Args: - path (string): Path to the JSON file - dry_run (boolean): Only show issues - create_backup (boolean): Create backup Repairs: BOM, trailing commas, single quotes, comments, NUL bytes

NameTypeReqDescription
create_backupboolean–Create backup
dry_runboolean–Preview only
pathstringyesPath to the JSON file

No output schema declared.

No examples provided.

cc_fix_umlauts ~100

Repairs broken German umlauts in source code files. Args: - path (string): Path to the file - dry_run (boolean): Preview only - create_backup (boolean): Create backup Detects 70+ patterns of broken umlauts and replaces them correctly.

NameTypeReqDescription
create_backupboolean–Create backup
dry_runboolean–Preview only
pathstringyesPath to the file

No output schema declared.

No examples provided.

cc_generate_licenses ~104

Generates a third-party license file for an npm or Python project. Args: - project_dir (string): Project directory - output_path (string): Output file - format (string): "text" | "json" | "csv" Reads package.json (npm) or pip packages and collects license info.

NameTypeReqDescription
formatstring–Format
output_pathstringyesOutput file
project_dirstringyesProject directory

No output schema declared.

No examples provided.

cc_md_to_html ~102

Converts Markdown to formatted HTML (printable as PDF). Args: - input_path (string): Path to the Markdown file - output_path (string): Path to the HTML output - title (string, optional): Document title Produces standalone HTML with CSS styling, printable as PDF via browser.

NameTypeReqDescription
input_pathstringyesMarkdown file
output_pathstringyesHTML output
titlestring–Document title

No output schema declared.

No examples provided.

cc_md_to_pdf ~118

Converts Markdown to PDF using a headless browser (Edge/Chrome). Args: - input_path (string): Path to the Markdown file - output_path (string): Path to the PDF output - title (string, optional): Document title Uses the same Markdown parser as cc_md_to_html. Requires Edge or Chrome. Falls back to HTML if no browser is found.

NameTypeReqDescription
input_pathstringyesMarkdown file
output_pathstringyesPDF output
titlestring–Document title

No output schema declared.

No examples provided.

cc_organize_imports ~99

Organizes Python imports per PEP 8: sorted, deduplicated, grouped. Args: - path (string): Path to the Python file - dry_run (boolean): Preview only Groups: 1) __future__ 2) stdlib 3) third-party 4) local

NameTypeReqDescription
dry_runboolean–Preview only
pathstringyesPath to the Python file

No output schema declared.

No examples provided.

cc_regex_test ~96

Testet regulaere Ausdruecke gegen Text oder Dateiinhalt

NameTypeReqDescription
file_pathstring–File to test against (alternative to text)
flagsstring–Regex flags (g, i, m, s, u)
patternstringyesRegular expression pattern
replace_withstring–Optional replacement string
textstring–Text to test against (or use file_path)

No output schema declared.

No examples provided.

cc_scan_emoji ~88

Scans files for emojis and shows ASCII alternatives. Args: - path (string): Path to the file or directory - recursive (boolean): Scan recursively - extensions (string): Only certain extensions Useful for systems that don't support Unicode/Emoji.

NameTypeReqDescription
extensionsstring–Extensions
pathstringyesPath
recursiveboolean–Recursive

No output schema declared.

No examples provided.

cc_set_language ~27

Set the output language for CodeCommander tools

NameTypeReqDescription
languagestringyesLanguage code

No output schema declared.

No examples provided.

cc_validate_json ~45

Validates JSON with detailed error information and position. Args: - path (string): Path to the JSON file

NameTypeReqDescription
pathstringyesPath to the JSON file

No output schema declared.

No examples provided.

Install

How do I install the BACH CodeCommander MCP server?

BACH CodeCommander runs locally as an npm package, launched with npx -y bach-codecommander-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 · bach-codecommander-mcp

# add to Claude Code
claude mcp add lukisch-bach-codecommander-mcp -- npx -y bach-codecommander-mcp
Common questions

What is the BACH CodeCommander MCP server?

BACH CodeCommander is an MCP server listed in the public MCP registry as io.github.lukisch/bach-codecommander-mcp. 17 tools for code analysis, JSON repair, encoding fix, format conversion, diff, and regex. This page covers its npm package (bach-codecommander-mcp).

Is the BACH CodeCommander MCP server safe to use?

BACH CodeCommander scores 71 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 BACH CodeCommander MCP server expose?

BACH CodeCommander exposes 18 tools: cc_analyze_code, cc_analyze_methods, cc_extract_classes, cc_organize_imports, cc_diagnose_imports, and 13 more. Their descriptions and schemas cost roughly 1,706 tokens of context every time the server is loaded.

Is the BACH CodeCommander MCP server still maintained?

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

BACH CodeCommander 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 BACH CodeCommander MCP server?

VerifyMCP ran 15 checks on BACH CodeCommander, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about BACH CodeCommander: Security disclosure. 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.