updated 2026-11-11 00:08 UTC

MCP Console Automation

Repository by ooples

MCP server for AI-driven console application automation and monitoring

MCP Servers TypeScript Listed MIT

Is MCP Console Automation safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 4.5 / 10
Provenance None
Signed commits 95%
Last push 7d ago
Advisories None known
Compare MCP Console Automation

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →
Suggest a correction

In detail: MCP Console Automation scores 57.4/100 (Grade C), ranked #787 of 1387 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 4.5/10; 95% of recent commits are signed; no published advisory affects its latest release (mcp-console-automation); last pushed 2026-11-04. Every point is earned from checkable signals — never paid placement. How scoring works →

How MCP Console Automation could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Already done? Suggest a correctionAdd the trust badge

Chain of custody

Scanners check what the code says. This traces who ships MCP Console Automation and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

  1. Source Signed

    github.com/ooples/mcp-console-automation, MIT, last pushed 2026-11-04. 95% of the last 100 commits carry a verified signature, so changes trace to a verified account.

  2. Review and release Mixed

    OpenSSF Scorecard rates the repository's practices 4.5/10 (scanned Nov 10, 2026). The checks that decide who can get a change released:

    • Code Review3
    • Branch Protection5
    • Signed Releasesn/a
    • Dangerous Workflow0
    • Token Permissions0
    • Pinned Dependencies4
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 5
    CI-Tests 8
    CII-Best-Practices 0
    Code-Review 3
    Contributors 3
    Dangerous-Workflow 0
    Dependency-Update-Tool 10
    Fuzzing 0
    License 10
    Maintained 9
    Packaging 10
    Pinned-Dependencies 4
    SAST 7
    Security-Policy 0
    Signed-Releases -1
    Token-Permissions 0
    Vulnerabilities 0

  3. Published packages Linked, not attested

    Without a build attestation, nothing proves the published files were built from this repository.

  4. What you install today No known advisories

    Latest release checked: mcp-console-automation 1.0.2. No published advisory affects it (OSV, checked 2026-11-10).

Changes to this chain

  • 2026-09-03 OSSF Scorecard: 4.6/10

Evidence behind this score

Coverage B: 3 of 5 independent evidence types found.

  • GitHub repository data
  • Package downloads
  • Supply-chain checks
  • Public actions (missing)
  • Community mentions (missing)

Verify this score yourself

Every build re-issues MCP Console Automation’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

Signed credential (JSON) How to verify

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.

How MCP Console Automation compares in MCP Servers

  1. #425 MCP Shodan 57.4 ±0
  2. #426 ArcGIS MCP Bridge 57.4 ±0
  3. #427 MCP Console Automation 57.4 this agent
  4. #428 MeiGen AI Design MCP 57.4 ±0
  5. #429 MCP Me 57.4 ±0

Bars show each HVTrust score; the tick marks MCP Console Automation’s 57.4.

Where the 57.4 comes from

HVTrust dimensions vs the MCP Servers average

57.4 / 100 · 100.0% confidence

MCP Console Automation MCP Servers average (779 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
10.4 / 25
in line with avg 10.8
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.9 below avg 13.7
Transparency50% declared license · 50% OSSF Scorecard
12.3 / 17
in line with avg 12.3
Maintenance60% last-push freshness · 40% commit activity
11.5 / 20
0.8 below avg 12.3
AdoptionLog-scaled stars · package downloads
6.4 / 20
1.2 below avg 7.6

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-11-10
Rank Moved
Rank dropped 10 spots (#774 → #784)
2026-11-07
Rank Moved
Rank dropped 39 spots (#728 → #767)
2026-10-30
Rank Moved
Rank rose 21 spots (#742 → #721)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 4.5/10. Tighten the weakest checks to improve public safety evidence.
Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.
Compare with another agent
View MCP Servers Report missing data
40.3
Activity sub-score · out of 100
#427
In MCP Servers

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade C reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-11-11 00:08 UTC · Repo last pushed 7 days ago

Rank Trend

2026-09-29 2026-11-10

Activity & Reach

Stars
54
Forks
16
Last Push
2026-11-04
7 days ago
Commits (4 wk)
0
Downloads (7d)
47
npm
HN mentions (30d)
—
Open Issues
0
Rank Change
▼3
was #784

Analysis

Activity Inputs

40.3 / 100
StarsRepository reach
10.4 / 30
FreshnessLast push recency
24.0 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
5.7 / 20

Common questions about MCP Console Automation

MCP Console Automation has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.
Does MCP Console Automation publish package provenance?
No published build provenance is currently detected for MCP Console Automation. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does MCP Console Automation have an OpenSSF Scorecard?
MCP Console Automation has an OpenSSF Scorecard score of 4.5/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.
Is MCP Console Automation actively maintained?
Actively maintained. The repository was pushed to within the last 7 day(s).
What license does MCP Console Automation use?
MCP Console Automation ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are MCP Console Automation's commits signed?
95% of the last 100 commits to MCP Console Automation are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

AI agent surface

MCP, providers, tool surface
Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support
high confidence
Implemented
MCP Console Automation appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
None detected
No clear third-party provider dependency detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
None detected
No clear plugin system or broad tool surface detected.
Detailed evidence is not shown in the public view.
Package Provenance Drift
high confidence
Match
Published package metadata matches the tracked repo
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live
How this surface has changed

Detected changes to MCP Console Automation's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.

2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented

Maintain MCP Console Automation?

For maintainers

HVTrust scores MCP Console Automation from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history
Rank 34HVTrust 3Grade 2Scorecard 1Delisted 1Listed 1MCP 1Score 1
2026-11-10
Rank Moved
Rank dropped 10 spots (#774 → #784)
2026-11-07
Rank Moved
Rank dropped 39 spots (#728 → #767)
2026-10-30
Rank Moved
Rank rose 21 spots (#742 → #721)
2026-10-27
Rank Moved
Rank rose 53 spots (#789 → #736)
2026-10-18
Rank Moved
Rank dropped 15 spots (#743 → #758)
2026-10-15
Rank Moved
Rank dropped 10 spots (#735 → #745)
2026-10-14
Rank Moved
Rank dropped 15 spots (#720 → #735)
2026-10-14
Activity Score Changed
Activity score down 5pts (46 → 41)
2026-10-10
Rank Moved
Rank dropped 13 spots (#688 → #701)
2026-10-09
Rank Moved
Rank dropped 11 spots (#677 → #688)
2026-10-08
Rank Moved
Rank dropped 77 spots (#600 → #677)
2026-10-02
Rank Moved
Rank dropped 11 spots (#581 → #592)
2026-09-30
Rank Moved
Rank dropped 55 spots (#530 → #585)
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Grade Changed
Trust grade D → C
2026-09-23
Rank Moved
Rank rose 313 spots (#849 → #536)
2026-09-23
HVTrust Changed
HVTrust up 35.1pts (27.9 → 63.0)
2026-09-22
Newly Listed
First tracked at rank #849
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-16
Rank Moved
Rank rose 69 spots (#584 → #515)
2026-09-11
Rank Moved
Rank rose 27 spots (#608 → #581)
2026-09-10
Rank Moved
Rank dropped 79 spots (#529 → #608)
2026-09-08
Rank Moved
Rank rose 70 spots (#594 → #524)
2026-09-07
Grade Changed
Trust grade D → C
2026-09-07
Rank Moved
Rank rose 512 spots (#1106 → #594)
2026-09-07
HVTrust Changed
HVTrust up 19.5pts (40.0 → 59.5)
2026-09-06
Rank Moved
Rank dropped 12 spots (#1094 → #1106)
2026-09-05
Rank Moved
Rank dropped 36 spots (#1058 → #1094)
2026-09-04
Rank Moved
Rank dropped 53 spots (#1005 → #1058)
2026-09-03
Scorecard Added
OSSF Scorecard: 4.6/10
2026-09-03
Rank Moved
Rank rose 241 spots (#1246 → #1005)
2026-09-03
HVTrust Changed
HVTrust up 18.7pts (22.5 → 41.2)
2026-09-02
Rank Moved
Rank dropped 34 spots (#1212 → #1246)
2026-09-01
Rank Moved
Rank dropped 32 spots (#1180 → #1212)
2026-08-31
Rank Moved
Rank dropped 27 spots (#1153 → #1180)
2026-08-30
Rank Moved
Rank dropped 39 spots (#1114 → #1153)
2026-08-29
Rank Moved
Rank dropped 40 spots (#1074 → #1114)
2026-08-28
Rank Moved
Rank dropped 28 spots (#1046 → #1074)
2026-08-27
Rank Moved
Rank dropped 21 spots (#1025 → #1046)
2026-08-26
Rank Moved
Rank dropped 93 spots (#932 → #1025)
2026-08-19
Rank Moved
Rank dropped 10 spots (#921 → #931)
2026-08-17
Rank Moved
Rank rose 10 spots (#934 → #924)
2026-08-16
Rank Moved
Rank dropped 29 spots (#905 → #934)
2026-08-14
Rank Moved
Rank dropped 10 spots (#897 → #907)
GitHub → npm: mcp-console-automation

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 57.4 Grade C
Markdown:
[![HVTrust](https://hvtracker.net/badge/mcp-console-automation.svg)](https://hvtracker.net/agents/mcp-console-automation)
HTML:
<a href="https://hvtracker.net/agents/mcp-console-automation"><img src="https://hvtracker.net/badge/mcp-console-automation.svg" alt="HVTrust"></a>

Other agents in MCP Servers

Data sources
GitHub REST API (repo, commits, stars, forks, license) · npm Registry (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON