ellmos ControlCenter
NPM · ELLMOS-CONTROLCENTER-MCP · SCANNED SEP 20
MCP control plane: local server discovery, profiles, capability bundles, and policy audits.
Available components
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
- 48 of 149 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 0 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability71
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 2023 tokens (~101/item across 20 items; 20 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
- Stability observed for 28 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 20 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 20 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
How do I install the ellmos ControlCenter MCP server?
ellmos ControlCenter runs locally as an npm package, launched with npx -y ellmos-controlcenter-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-controlcenter-mcp
claude mcp add ellmos-ai-ellmos-controlcenter-mcp -- npx -y ellmos-controlcenter-mcp
{
"mcpServers": {
"ellmos-ai-ellmos-controlcenter-mcp": {
"command": "npx",
"args": [
"-y",
"ellmos-controlcenter-mcp"
]
}
}
} {
"servers": {
"ellmos-ai-ellmos-controlcenter-mcp": {
"command": "npx",
"args": [
"-y",
"ellmos-controlcenter-mcp"
]
}
}
} codex mcp add ellmos-ai-ellmos-controlcenter-mcp -- npx -y ellmos-controlcenter-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ellmos-ai-ellmos-controlcenter-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"ellmos-controlcenter-mcp"
],
"enabled": true
}
}
} openclaw mcp add ellmos-ai-ellmos-controlcenter-mcp --command npx --arg -y --arg ellmos-controlcenter-mcp
mcp_servers:
ellmos-ai-ellmos-controlcenter-mcp:
command: "npx"
args: ["-y", "ellmos-controlcenter-mcp"] {
"McpServers": {
"ellmos-ai-ellmos-controlcenter-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"ellmos-controlcenter-mcp"
]
}
}
} assistant mcp add ellmos-ai-ellmos-controlcenter-mcp -t stdio -c npx -a -y ellmos-controlcenter-mcp
{
"mcpServers": {
"ellmos-ai-ellmos-controlcenter-mcp": {
"command": "npx",
"args": [
"-y",
"ellmos-controlcenter-mcp"
]
}
}
} 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 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 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 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 −3
- Stability: pass → 0.80 functional
- 15 Sept 26 +1
- Stability: 0.97 → pass security
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 −3
- Stability: pass → 0.80 functional
- 8 Sept 26 +1
- Stability: 0.97 → pass security
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/ellmos-controlcenter-mcp@0.2.2
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 →
Dependencies 149 packages
| Packages resolved | 149 |
|---|---|
| Stale | 48 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
controlcenter_assign_tool_bundles Tools Capability-Bundles zuordnen ~175
Ordnet echte MCP-Tools anhand ihrer Metadaten den ControlCenter-Capability-Bundles zu.
| Name | Type | Req | Description |
|---|---|---|---|
| bundleConfigPath | string | – | Optionaler Pfad zu einer Capability-Bundle-Konfiguration. |
| mcpRoot | string | – | Optionaler MCP-Root. Standard ist der lokale ellmos-MCP-Ordner. |
| profileName | string | – | Optionaler Profilname. Wenn gesetzt, werden die aufgelösten Server dieses Claude-Profils gescannt. |
| profileRoot | string | – | Optionaler Profilordner. Standard ist ~/.claude/profiles. |
| serverName | string | – | Optionaler Servername für einen gezielten Scan. |
| timeoutMs | integer | – | Timeout pro MCP-Tool-Scan in Millisekunden. Standard: 5000. |
No output schema declared.
No examples provided.
controlcenter_audit_profile Claude-Profil auditieren ~107
Prüft ein aufgelöstes Claude-Profil auf erste Policy-Hinweise wie npx-Starts, Env-Secrets und ungültige Server-Konfigurationen.
| Name | Type | Req | Description |
|---|---|---|---|
| policyConfigPath | string | – | Optionaler Pfad zu einer Policy-Regel-Konfiguration. |
| profileName | string | yes | Profilname ohne .json, zum Beispiel software oder ai-lab. |
| profileRoot | string | – | Optionaler Profilordner. Standard ist ~/.claude/profiles. |
No output schema declared.
No examples provided.
controlcenter_build_catalog Lokalen Server-Katalog bauen ~223
Erzeugt einen JSON-Katalog der lokal gefundenen MCP-Server.
| Name | Type | Req | Description |
|---|---|---|---|
| bundleConfigPath | string | – | Optionaler Pfad zu einer Capability-Bundle-Konfiguration. |
| includeToolAssignments | boolean | – | Wenn true, werden Tool-Bundle-Zuordnungen für gescannte Tools in den Katalog aufgenommen. |
| includeTools | boolean | – | Wenn true, werden lokale MCP-Server gestartet und echte list_tools-Ergebnisse in den Katalog aufgenommen. |
| mcpRoot | string | – | Optionaler MCP-Root. Standard ist der lokale ellmos-MCP-Ordner. |
| outputPath | string | – | Optionaler Ausgabeort für den JSON-Katalog. |
| profileName | string | – | Optionaler Profilname. Wenn gesetzt, werden die aufgelösten Server dieses Claude-Profils gescannt. |
| profileRoot | string | – | Optionaler Profilordner. Standard ist ~/.claude/profiles. |
| timeoutMs | integer | – | Timeout pro MCP-Tool-Scan in Millisekunden. Standard: 5000. |
No output schema declared.
No examples provided.
controlcenter_context_pack Stack-Kontextpaket erstellen ~81
Erstellt ein kompaktes, rein lesendes Kontextpaket aus einem registrierten Stack-Manifest. Es führt keine Komponenten aus und liest weder Geheimnisse noch Live-Zustände.
| Name | Type | Req | Description |
|---|---|---|---|
| level | string | – | Umfang des Kontextpakets: short, execution oder full. |
| stackId | string | yes | Stabile Stack-ID aus stacks.catalog.json. |
No output schema declared.
No examples provided.
controlcenter_describe_stack Registrierten Stack beschreiben ~80
Zeigt typisierte Komponenten, Pflichtrollen, Policies und Validierungswarnungen für einen registrierten Stack.
| Name | Type | Req | Description |
|---|---|---|---|
| stackId | string | yes | Stabile Stack-ID aus stacks.catalog.json. |
| stacksRoot | string | – | Optionaler Pfad zum Ordner mit stacks.catalog.json. Standard ist der lokale .AI/.STACKS-Ordner. |
No output schema declared.
No examples provided.
controlcenter_find_skill Passende Skills finden ~208
Erkennt, welche Skills zu einer Freitext-Aufgabe bzw. einem Intent passen. Bewertet den gescannten Skill-Katalog lexikalisch über Name, Aliases, Tags, Kategorie und Beschreibung und gibt die besten Kandidaten mit den getroffenen Begriffen zurück.
| Name | Type | Req | Description |
|---|---|---|---|
| deployedOnly | boolean | – | Wenn true, werden nur deployte Skills zurückgegeben und die Quell-Skill-Bibliothek nicht gescannt. |
| intent | string | yes | Freitext-Aufgabe oder Intent, gegen den der Skill-Katalog gematcht wird. |
| limit | integer | – | Maximale Anzahl gerankter Skill-Kandidaten. Standard: 5. |
| skillsRoot | string | – | Optionaler Pfad zum deployte Skills-Ordner. Standard ist ~/.claude/skills. |
| sourceSkillsRoot | string | – | Optionaler Pfad zum Quell-Skill-Bibliotheks-Root. Standard ist der lokale .AI/.SKILLS/skills-Ordner. |
No output schema declared.
No examples provided.
controlcenter_get_language ControlCenter Sprache anzeigen ~27
Zeigt die aktuelle ControlCenter-Ausgabesprache und die unterstützten Sprachcodes.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
controlcenter_list_bundles Capability-Bundles listen ~80
Gruppiert lokale MCP-Server in Aufgaben-Bundles wie Software, Filesystem, Automation und Control Plane.
| Name | Type | Req | Description |
|---|---|---|---|
| bundleConfigPath | string | – | Optionaler Pfad zu einer Capability-Bundle-Konfiguration. |
| mcpRoot | string | – | Optionaler MCP-Root. Standard ist der lokale ellmos-MCP-Ordner. |
No output schema declared.
No examples provided.
controlcenter_list_local_servers Lokale MCP-Server listen ~59
Scannt den lokalen MCP-Root und listet gefundene MCP-Repos mit Metadaten auf.
| Name | Type | Req | Description |
|---|---|---|---|
| mcpRoot | string | – | Optionaler MCP-Root. Standard ist der lokale ellmos-MCP-Ordner. |
No output schema declared.
No examples provided.
controlcenter_list_plugins Plugins und Module listen ~137
Inventarisiert installierte Claude Code Plugins und lokale ellmos-Module mit ihren Fähigkeiten.
| Name | Type | Req | Description |
|---|---|---|---|
| modulesOnly | boolean | – | Wenn true, werden nur lokale Module zurückgegeben und Claude Code Plugins nicht gescannt. |
| modulesRoot | string | – | Optionaler Pfad zum ellmos-Module-Ordner. Standard ist der lokale .AI/.MODULES-Ordner. |
| pluginsOnly | boolean | – | Wenn true, werden nur Claude Code Plugins zurückgegeben und lokale Module nicht gescannt. |
| pluginsRoot | string | – | Optionaler Pfad zum Claude Code Plugins-Ordner. Standard ist ~/.claude/plugins. |
No output schema declared.
No examples provided.
controlcenter_list_profiles Claude-Profile listen ~52
Liest die lokalen Claude-Profile und zeigt Serveranzahl, Vererbung und Dateipfade.
| Name | Type | Req | Description |
|---|---|---|---|
| profileRoot | string | – | Optionaler Profilordner. Standard ist ~/.claude/profiles. |
No output schema declared.
No examples provided.
controlcenter_list_skills Claude Code Skills listen ~134
Inventarisiert installierte Claude Code Skills aus dem deployte Skills-Ordner und der Quell-Skill-Bibliothek.
| Name | Type | Req | Description |
|---|---|---|---|
| deployedOnly | boolean | – | Wenn true, werden nur deployte Skills zurückgegeben und die Quell-Skill-Bibliothek nicht gescannt. |
| skillsRoot | string | – | Optionaler Pfad zum deployte Skills-Ordner. Standard ist ~/.claude/skills. |
| sourceSkillsRoot | string | – | Optionaler Pfad zum Quell-Skill-Bibliotheks-Root. Standard ist der lokale .AI/.SKILLS/skills-Ordner. |
No output schema declared.
No examples provided.
controlcenter_list_stacks Registrierte Stacks listen ~69
Liest den neutralen Stack-Katalog und seine ellmos.stack.v2-Manifeste, ohne Stack-Komponenten auszuführen.
| Name | Type | Req | Description |
|---|---|---|---|
| stacksRoot | string | – | Optionaler Pfad zum Ordner mit stacks.catalog.json. Standard ist der lokale .AI/.STACKS-Ordner. |
No output schema declared.
No examples provided.
controlcenter_list_tools MCP-Tools listen ~168
Startet lokale oder profildefinierte MCP-Server kontrolliert und liest deren echte Tool-Liste per MCP list_tools aus.
| Name | Type | Req | Description |
|---|---|---|---|
| mcpRoot | string | – | Optionaler MCP-Root. Standard ist der lokale ellmos-MCP-Ordner. |
| profileName | string | – | Optionaler Profilname. Wenn gesetzt, werden die aufgelösten Server dieses Claude-Profils gescannt. |
| profileRoot | string | – | Optionaler Profilordner. Standard ist ~/.claude/profiles. |
| serverName | string | – | Optionaler Servername, Paketname, mcpName oder Profilservername für einen gezielten Scan. |
| timeoutMs | integer | – | Timeout pro Connect- und list_tools-Anfrage in Millisekunden. Standard: 5000. |
No output schema declared.
No examples provided.
controlcenter_resolve_profile Claude-Profil auflösen ~75
Löst ein Claude-Profil inklusive optionaler Vererbung auf und zeigt die resultierenden MCP-Server.
| Name | Type | Req | Description |
|---|---|---|---|
| profileName | string | yes | Profilname ohne .json, zum Beispiel software oder ai-lab. |
| profileRoot | string | – | Optionaler Profilordner. Standard ist ~/.claude/profiles. |
No output schema declared.
No examples provided.
controlcenter_set_language ControlCenter Sprache setzen ~44
Setzt die ControlCenter-Ausgabesprache für diese laufende MCP-Serverinstanz.
| Name | Type | Req | Description |
|---|---|---|---|
| language | string | yes | Sprachcode für die ControlCenter-Ausgaben. |
No output schema declared.
No examples provided.
controlcenter_status ControlCenter Status ~27
Zeigt einen Überblick über den lokalen MCP-Stack, lokale Server und Claude-Profile.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
controlcenter_suggest_bundles Capability-Bundles empfehlen ~85
Empfiehlt passende Capability-Bundles für eine Aufgabenbeschreibung.
| Name | Type | Req | Description |
|---|---|---|---|
| bundleConfigPath | string | – | Optionaler Pfad zu einer Capability-Bundle-Konfiguration. |
| mcpRoot | string | – | Optionaler MCP-Root. Standard ist der lokale ellmos-MCP-Ordner. |
| task | string | yes | Aufgabenbeschreibung oder Ziel der Session. |
No output schema declared.
No examples provided.
controlcenter_suggest_profile Profil empfehlen ~36
Empfiehlt ein Claude-Profil anhand der Aufgabenbeschreibung.
| Name | Type | Req | Description |
|---|---|---|---|
| task | string | yes | Aufgabenbeschreibung oder Ziel der Session. |
No output schema declared.
No examples provided.
controlcenter_switch_profile Profilwechsel vorbereiten ~156
Bereitet einen Profilwechsel vor, indem ein aufgelöstes --mcp-config-File erzeugt oder als Vorschau angezeigt wird.
| Name | Type | Req | Description |
|---|---|---|---|
| launchTemplate | string | – | Optionales Startbefehl-Template. Nutze {config} als Platzhalter für den Pfad zur generierten MCP-Config. |
| outputPath | string | – | Optionaler Ausgabeort für die generierte MCP-Config. |
| profileName | string | yes | Profilname ohne .json, zum Beispiel software oder ai-lab. |
| profileRoot | string | – | Optionaler Profilordner. Standard ist ~/.claude/profiles. |
| write | boolean | – | Wenn true, wird die generierte Config geschrieben. Sonst nur Vorschau. |
No output schema declared.
No examples provided.
What is the ellmos ControlCenter MCP server?
ellmos ControlCenter is an MCP server listed in the public MCP registry as io.github.ellmos-ai/ellmos-controlcenter-mcp. MCP control plane: local server discovery, profiles, capability bundles, and policy audits. This page covers its npm package (ellmos-controlcenter-mcp).
Is the ellmos ControlCenter MCP server safe to use?
ellmos ControlCenter scores 83 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. 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 ControlCenter MCP server expose?
ellmos ControlCenter exposes 20 tools: controlcenter_get_language, controlcenter_set_language, controlcenter_status, controlcenter_list_local_servers, controlcenter_list_stacks, and 15 more. Their descriptions and schemas cost roughly 2,023 tokens of context every time the server is loaded.
Is the ellmos ControlCenter MCP server still maintained?
ellmos ControlCenter 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 ellmos ControlCenter MCP server under?
ellmos ControlCenter declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.