updated 2026-09-26 10:08 UTC

MCP Console Automation

ooples/mcp-console-automation

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 5.3 / 10
Provenance None
Signed commits 95%
Last push 12d ago
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 62.8/100 (Grade C), ranked #543 of 1325 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 5.3/10; 95% of recent commits are signed; last pushed 2026-09-14. Every point is earned from checkable signals — never paid placement. How scoring works →

How MCP Console Automation compares in MCP Servers

  1. #306 IvanMurzak Unity MCP 62.9 +0.1
  2. #307 Prometheus MCP 62.8 ±0
  3. #308 MCP Console Automation 62.8 this agent
  4. #309 MCP Server for Excel 62.6 −0.2
  5. #310 Sub Agents MCP 62.6 −0.2

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

Where the 62.8 comes from

HVTrust dimensions vs the MCP Servers average

62.8 / 100 · 100.0% confidence

MCP Console Automation MCP Servers average (775 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
11.4 / 25
1.1 above avg 10.3
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.6 below avg 13.4
Transparency50% declared license · 50% OSSF Scorecard
13.0 / 17
0.8 above avg 12.2
Maintenance60% last-push freshness · 40% commit activity
15.5 / 20
3.4 above avg 12.1
AdoptionLog-scaled stars · package downloads
6.1 / 20
1.1 below avg 7.2

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
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)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 5.3/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 Get email alerts for MCP Console Automation View MCP Servers Report missing data
52.9
Activity sub-score · out of 100
#308
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-09-26 10:08 UTC · Repo last pushed 12 days ago

Rank Trend

2026-08-11 2026-09-26

Activity & Reach

Stars
49
Forks
16
Last Push
2026-09-14
12 days ago
Commits (4 wk)
11
Downloads (7d)
34
npm
HN mentions (30d)
—
Open Issues
0
Rank Change
=
was #543

Analysis

Activity Inputs

52.9 / 100
StarsRepository reach
10.2 / 30
FreshnessLast push recency
23.3 / 25
ActivityRecent commits
13.5 / 25
CommunityFork signal
5.7 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
5.3 / 10
OpenSSF Scorecard · scanned Sep 25, 2026
Signed Commits
95%
of last 100 commits verified
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 10
Packaging 10
Pinned-Dependencies 4
SAST 7
Security-Policy 0
Signed-Releases -1
Token-Permissions 0
Vulnerabilities 10

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 5.3/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?
Maintained. Last push was 12 days ago.
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 23HVTrust 3Listed 2Grade 2Scorecard 1Delisted 1MCP 1
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)
2026-08-10
Rank Moved
Rank dropped 53 spots (#864 → #917)
2026-08-08
Newly Listed
First tracked at rank #861
GitHub → npm: mcp-console-automation

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 62.8 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.3 · Raw JSON