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.ooples/mcp-console-automation

NPM · MCP-CONSOLE-AUTOMATION · SCANNED SEP 28

MCP server for AI-driven console application automation and monitoring

Available components

npm · mcp-console-automation 33
0 this week 33 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 Security80
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects nodemailer 6.10.1, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 133 of 376 dependencies flagged as unhealthy (4 deprecated). View diagnostics → Partial
Provenance & Transparency43
Schema Quality & AI Usability0
  • Schema quality not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no schema to assess.Unverified
Stability & Change Management0
  • Stability not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no schema to compare.Unverified
Tool Coverage0
  • Tool coverage not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no tool definitions to assess.Unverified
Tool Safety0
  • Tool safety not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no tool text to scan.Unverified
Capabilities0
  • Protocol version not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we never saw its MCP handshake.Unverified

Unverified: 5 categories

Categories scored 0 because our sandbox has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you. How we score packages →

Install

How do I install the io.github.ooples/mcp-console-automation server?

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

npm · mcp-console-automation

# add to Claude Code
claude mcp add ooples-mcp-console-automation -- npx -y mcp-console-automation
// .cursor/mcp.json
{
  "mcpServers": {
    "ooples-mcp-console-automation": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-console-automation"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "ooples-mcp-console-automation": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-console-automation"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add ooples-mcp-console-automation -- npx -y mcp-console-automation
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ooples-mcp-console-automation": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "mcp-console-automation"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add ooples-mcp-console-automation --command npx --arg -y --arg mcp-console-automation
# ~/.hermes/config.yaml
mcp_servers:
  ooples-mcp-console-automation:
    command: "npx"
    args: ["-y", "mcp-console-automation"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "ooples-mcp-console-automation": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "mcp-console-automation"
      ]
    }
  }
}
# add to Vellum
assistant mcp add ooples-mcp-console-automation -t stdio -c npx -a -y mcp-console-automation
// mcp.json
{
  "mcpServers": {
    "ooples-mcp-console-automation": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-console-automation"
      ]
    }
  }
}
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.

  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 18 Sept 26 0
    • CVE-2026-92598 affects this package: high ▼ security
    • CVE-2026-92595 affects this package: high ▼ security
    • CVE-2026-92597 affects this package: high ▼ security
    • CVE-2026-92596 affects this package: high ▼ security
    • GHSA-cc9r-2j5m-2m83 no longer affects this package ▲ security
    • GHSA-8m3c-c648-2xjj no longer affects this package ▲ security
    • GHSA-wmmp-3585-3rmp no longer affects this package ▲ security
    • GHSA-2x7j-588g-ccc2 no longer affects this package ▲ security
  • 16 Sept 26 0
    • CVE-2026-82562 no longer affects this package ▲ security
    • CVE-2026-82417 no longer affects this package ▲ security
  • 9 Sept 26 0
    • GHSA-8m3c-c648-2xjj affects this package: high ▼ security
    • GHSA-2x7j-588g-ccc2 affects this package: high ▼ security
    • GHSA-cc9r-2j5m-2m83 affects this package: high ▼ security
    • GHSA-wmmp-3585-3rmp affects this package: high ▼ security
  • 4 Sept 26 0
    • Security disclosure: unverified → fail ▼ functional
  • 3 Sept 26 0
    • CVE-2026-82562 affects this package: high ▼ security
    • CVE-2026-82417 affects this package: high ▼ security
  • 2 Sept 26 0
    • Security disclosure: fail → unverified ▼ 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 28 Sept 2026 · Analysed npm/mcp-console-automation@1.0.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 →

Vulnerabilities 13 findings
ID CVE Severity Vector Fix available
GHSA-268h-hp4c-crq3 CVE-2026-82661 medium CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N yes
GHSA-2x7j-588g-ccc2 CVE-2026-92596 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-8m3c-c648-2xjj CVE-2026-92595 medium CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:L/A:N yes
GHSA-c7w3-x93f-qmm8 CVE-2026-82854 low yes
GHSA-cc9r-2j5m-2m83 CVE-2026-92597 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N yes
GHSA-mm7p-fcc7-pg87 CVE-2025-13033 medium yes
GHSA-p6gq-j5cr-w38f CVE-2026-82659 high CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N yes
GHSA-r7g4-qg5f-qqm2 CVE-2026-82662 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N yes
GHSA-rcmh-qjqh-p98v CVE-2025-14874 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-vvjj-xcjg-gr5g CVE-2026-82853 medium CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:N yes
GHSA-wmmp-3585-3rmp CVE-2026-92598 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N yes
GHSA-wqvq-jvpq-h66f CVE-2026-82660 medium CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N yes
GHSA-w5hq-g745-h8pq CVE-2026-41907 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 376 packages
Packages resolved 376
Deprecated 4
Stale 130
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools

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 →

Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.

Common questions

What is the io.github.ooples/mcp-console-automation server?

io.github.ooples/mcp-console-automation is listed in the public MCP registry as io.github.ooples/mcp-console-automation. MCP server for AI-driven console application automation and monitoring. This page covers its npm package (mcp-console-automation).

Is the io.github.ooples/mcp-console-automation server safe to use?

io.github.ooples/mcp-console-automation scores 33 out of 100 on VerifyMCP. We recorded 13 known advisories against it as of 28 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.

Is the io.github.ooples/mcp-console-automation server still maintained?

io.github.ooples/mcp-console-automation is still listed as active in the MCP registry. We last reached this channel on 28 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.ooples/mcp-console-automation server under?

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