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.

ellmos CodeCommander

NPM · ELLMOS-CODECOMMANDER-MCP

Developer MCP server: code analysis, JSON repair, imports, diffs, regex, format conversion.

0 this week 78 Trust /100

Last scanned (22 hours ago)

Scores higher than 58% 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
  • 45 of 158 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 3 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability66
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 2678 tokens (~116/item across 23 items; 23 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • 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 23 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 23 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.

  • 4 Nov 26 +1
    • Stability: 0.97 → pass security
  • 3 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 1 Nov 26 +1
    • Security disclosure: unverified → pass ▲ functional
  • 31 Oct 26 −1
    • Security disclosure: pass → unverified ▼ functional
  • 28 Oct 26 +1
    • Stability: 0.97 → pass security
  • 27 Oct 26 −1
    • Stability: pass → 0.97 functional
  • 25 Oct 26 0
    • Stability: pass → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • First check of Schema quality: unverified functional
    • Package version: 1.3.16 → 1.3.26 functional
  • 24 Oct 26 −5
    • CVE-2023-54404 affects this package: high ▼ security
    • Known CVEs: pass → fail ▼ security
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 4 Nov 2026 · Analysed npm/ellmos-codecommander-mcp@1.3.26

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 158 packages
Packages resolved 158
Stale 45
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 23 exposed · ~2,678 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 ~105

Analyzes a Python, JavaScript, or TypeScript file: classes, functions, imports, metrics. Args: - path (string): Path to a .py, .js/.jsx/.mjs/.cjs, or .ts/.tsx/.mts/.cts file Returns: - Classes with methods, functions, import analysis, LOC, complexity

NameTypeReqDescription
pathstringyesPath to a supported Python, JavaScript, or TypeScript file

No output schema declared.

No examples provided.

cc_analyze_methods ~135

Detailed method analysis of a Python, JavaScript, or TypeScript file. Args: - path (string): Path to a .py, .js/.jsx/.mjs/.cjs, or .ts/.tsx/.mts/.cts file - class_name (string, optional): Only methods of this class Returns: - Methods with parameters and visibility; Python analysis also includes decorators, complexity, data flow, and BACH guardrails

NameTypeReqDescription
class_namestring–Only analyze this class
pathstringyesPath to a supported Python, JavaScript, or TypeScript file

No output schema declared.

No examples provided.

cc_check_indentation ~91

Prüft Python-Dateien auf fehlende Doppelpunkte, unindentierte return/yield-Zeilen und gemischte Tab-/Leerzeichen-Einrückung

NameTypeReqDescription
max_issuesinteger–Maximum number of issues to include
pathstringyesPython file or directory to check
recursiveboolean–Recurse into subdirectories when path is a directory

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 ~101

Diagnoses import issues in Python, JavaScript, or TypeScript files. Args: - path (string): Path to a .py, .js/.jsx/.mjs/.cjs, or .ts/.tsx/.mts/.cts file Detects: Unused bindings, duplicates, relative-import risks, and import-order issues

NameTypeReqDescription
pathstringyesPath to a supported Python, JavaScript, or TypeScript 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 ~149

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) - include_content (boolean, optional): Include pycutter-style code blocks in the response - max_chars (number, optional): Maximum response characters for included code Useful for code review and documentation.

NameTypeReqDescription
include_contentboolean–Include extracted class/helper content in the MCP response
max_charsinteger–Maximum characters of included extracted content
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_generate_python_code ~285

Generiert Python-Code-Snippets aus BACH-abgeleiteten Templates ohne Dateien zu schreiben

NameTypeReqDescription
actstring–Act block for test generation
arrangestring–Arrange block for test generation
assertionsstring–Assert block for test generation
basestring–Base exception class for exception generation
bases_jsonstring–JSON array of class base names
bodystring–Function or method body
contentstring–Module content
descriptionstring–Module or CLI description
docstringstring–Docstring
fields_jsonstring–JSON array of dataclass fields
imports_jsonstring–JSON array of import lines for module generation
init_params_jsonstring–JSON array of __init__ parameters for classes
kindstring–Template kind
main_bodystring–CLI main body
namestring–Generated item name
params_jsonstring–JSON array of parameters: [{"name":"x","type":"int","default":"0"}]
return_typestring–Return type annotation for functions
spec_jsonstring–Optional full JSON spec. If set, it is merged with the explicit fields.
targetstring–Target name for test generation

No output schema declared.

No examples provided.

cc_get_language ~23

Get the currently configured output language and supported languages for CodeCommander tools

Input schema present but exposes no named parameters.

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_python_structural_edit ~270

Prüft und wendet BACH-abgeleitete strukturelle Python-Edits mit Vorschau, Testdatei und Backup-Schutz an

NameTypeReqDescription
class_namestring–Target class for position=in_class
contentstring–Inserted code or replacement line content
create_backupboolean–Create a backup when mode=apply
edit_filestring–Edit file path for merge_edit_file
elementstring–Class/function/method name, e.g. MyClass.method
elementsstring–Comma-separated element names for create_edit_file
indent_spacesinteger–Indent inserted non-empty lines
lineinteger–1-based line for position=line or replace_line
modestring–preview returns a diff, test writes a .test.py file, apply writes the source
operationstringyesStructural edit operation
output_pathstring–Optional output path for test or edit-file modes
pathstringyesPython file to inspect or edit
positionstring–Insert position for operation=insert
python_pathstring–Python executable path for syntax checks
syntax_checkboolean–Compile-check edited Python before writing

No output schema declared.

No examples provided.

cc_regex_test ~95

Testet reguläre Ausdrücke 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_runtime_import_diagnose ~115

Führt BACH-abgeleitete Python-Runtime-Importdiagnosen in isolierten Subprozessen aus

NameTypeReqDescription
max_modulesinteger–Maximum auto-discovered modules to import
modulesstring–Optional module list: package.mod:Class,other.module
pathstringyesPython project directory or file
python_pathstring–Python executable path; defaults to PYTHON/PYTHON_EXECUTABLE/python
timeout_secondsinteger–Timeout per isolated import subprocess

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

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

# add to Claude Code
claude mcp add ellmos-ai-ellmos-codecommander-mcp -- npx -y ellmos-codecommander-mcp
Common questions

What is the ellmos CodeCommander MCP server?

ellmos CodeCommander is an MCP server listed in the public MCP registry as io.github.ellmos-ai/ellmos-codecommander-mcp. Developer MCP server: code analysis, JSON repair, imports, diffs, regex, format conversion. This page covers its npm package (ellmos-codecommander-mcp).

Is the ellmos CodeCommander MCP server safe to use?

ellmos CodeCommander scores 78 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 4 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 ellmos CodeCommander MCP server expose?

ellmos CodeCommander exposes 23 tools: cc_analyze_code, cc_analyze_methods, cc_extract_classes, cc_organize_imports, cc_diagnose_imports, and 18 more. Their descriptions and schemas cost roughly 2,678 tokens of context every time the server is loaded.

Is the ellmos CodeCommander MCP server still maintained?

ellmos CodeCommander is still listed as active in the MCP registry. We last reached this channel on 4 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 ellmos CodeCommander MCP server under?

ellmos 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.