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

MCP server for AI-driven console application automation and monitoring

−1 this week 32 Trust /100

Last scanned (15 hours ago)

Scores higher than 4% 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 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
  • 136 of 380 dependencies flagged as unhealthy (4 deprecated). View diagnostics → Partial
Provenance & Transparency42
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 →

What we tested

Checks we ran (9)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure

Checks we could not complete (5)

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.

  • Schema quality in Schema Quality & AI Usability (scores 0 for this)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.
  • Stability in Stability & Change Management (scores 0 for this)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.
  • Tool coverage in Tool Coverage (scores 0 for this)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.
  • Tool safety in Tool Safety (scores 0 for this)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.
  • Capabilities in Capabilities (scores 0 for this)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.

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.

  • 19 Nov 26 0
    • Security disclosure: unverified → fail ▼ functional
  • 18 Nov 26 0
    • Security disclosure: fail → unverified ▼ functional
  • 16 Nov 26 −1

    No change was recorded against any check on this day. Provenance & Transparency went from 43 to 42.

  • 10 Nov 26 0
    • Security disclosure: unverified → fail ▼ functional
  • 9 Nov 26 0
    • Security disclosure: fail → unverified ▼ functional
  • 7 Nov 26 0
    • Security disclosure: unverified → fail ▼ functional
  • 6 Nov 26 0
    • Security disclosure: fail → unverified ▼ functional
  • 4 Nov 26 0
    • CVE-2026-121426 affects this package: high ▼ security
    • CVE-2026-121424 affects this package: high ▼ security
    • CVE-2026-121425 affects this package: high ▼ security
    • GHSA-8c8m-p3m8-cjg8 no longer affects this package ▲ security
    • GHSA-85x2-q946-cp5h no longer affects this package ▲ security
    • GHSA-m943-m63m-w62w no longer affects this package ▲ 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 21 Nov 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 23 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-39m8-27wv-hr27 CVE-2026-110871 medium CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H yes
GHSA-4ffr-jq9g-5ffx CVE-2026-110869 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-4g23-2xm8-66gc CVE-2026-110872 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-6vj9-mwq6-2f5v CVE-2026-100701 medium CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:L/A:N yes
GHSA-85x2-q946-cp5h CVE-2026-121426 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N yes
GHSA-8c8m-p3m8-cjg8 CVE-2026-121424 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N 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-8vvx-rff5-p5rq CVE-2026-100702 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H 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-g73g-hqqh-jr95 CVE-2026-110870 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N yes
GHSA-m943-m63m-w62w CVE-2026-121425 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-v53p-9fqp-m79j CVE-2026-100700 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 380 packages
Packages resolved 380
Deprecated 4
Stale 133
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.

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
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 32 out of 100 on VerifyMCP. We recorded 23 known advisories 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.

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

What did VerifyMCP test on the io.github.ooples/mcp-console-automation server?

VerifyMCP ran 9 checks on io.github.ooples/mcp-console-automation, covering Malware scan, Known CVEs, Install scripts, Dependency health and 5 more. 5 items could not be completed, a gap on our side rather than a finding about io.github.ooples/mcp-console-automation: Schema quality, Stability, Tool coverage, Tool safety and 1 more. 5 categories score 0 for that reason, because we only credit what we can confirm. 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.