Is Terminal MCP Server safe to use?

Terminal MCP Server has an HVTrust score of 38.5/100 (Grade D), ranked #1191 of 1325 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Terminal MCP Server?

Terminal MCP Server scores 38.5/100 on HVTracker's evidence-weighted HVTrust scale. It has 19 GitHub stars and is categorized under MCP Servers.

Terminal MCP Server

aybelatchane/mcp-server-terminal

Terminal MCP Server - Model Context Protocol server for TUI/CLI automation with structured Terminal State Tree (TST)

MCP Servers Rust Listed MIT

Is Terminal MCP Server safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 3.6 / 10

Provenance None

Signed commits 4%

Last push 267d ago

Compare Terminal MCP Server

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: Terminal MCP Server scores 38.5/100 (Grade D), ranked #1191 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 3.6/10; 4% of recent commits are signed; last pushed 2026-01-02. Every point is earned from checkable signals — never paid placement. How scoring works →

How Terminal MCP Server compares in MCP Servers

#707 XamlMcp 38.7 +0.2
#708 Unreal MCP Ue4 38.7 +0.2
#709 Terminal MCP Server 38.5 this agent
#710 OneTool MCP 38.5 ±0
#711 Augments MCP Server 38.4 −0.1

Bars show each HVTrust score; the tick marks Terminal MCP Server’s 38.5.

Where the 38.5 comes from

HVTrust dimensions vs the MCP Servers average

38.5 / 100 · 100.0% confidence

Terminal MCP Server MCP Servers average (775 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

4.7 / 25

5.6 below 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

11.6 / 17

0.6 below avg 12.2

Maintenance60% last-push freshness · 40% commit activity

0 / 20

12.0 below avg 12.0

AdoptionLog-scaled stars · package downloads

5.4 / 20

1.8 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

Rank Moved

Rank rose 78 spots (#1270 → #1192)

2026-09-23

HVTrust Changed

HVTrust up 24.1pts (14.3 → 38.4)

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 3.6/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.

Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.

Refresh maintenance signals The repo was last pushed 267 days ago. Fresh activity helps separate stable projects from stale ones.

Compare with another agent Get email alerts for Terminal MCP Server View MCP Servers Report missing data

11.4

Activity sub-score · out of 100

#709

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 D 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 →

Rank Trend

2026-08-11 2026-09-26

Activity & Reach

Stars

Forks

Last Push

2026-01-02

267 days ago

Commits (4 wk)

Downloads (7d)

npm

HN mentions (30d)

—

Open Issues

Rank Change

▲1

was #1192

Analysis

Activity Inputs

11.4 / 100

StarsRepository reach

7.8 / 30

FreshnessLast push recency

0.0 / 25

ActivityRecent commits

0.0 / 25

CommunityFork signal

3.6 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

3.6 / 10

OpenSSF Scorecard · scanned Sep 21, 2026

Signed Commits

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 0

CI-Tests 10

CII-Best-Practices 0

Code-Review 0

Contributors 0

Dangerous-Workflow 10

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 0

Packaging 10

Pinned-Dependencies 0

SAST 10

Security-Policy 10

Signed-Releases 0

Token-Permissions 0

Vulnerabilities 0

Common questions about Terminal MCP Server

Public trust evidence for Terminal MCP Server is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.

Does Terminal MCP Server publish package provenance?

No published build provenance is currently detected for Terminal MCP Server. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.

Does Terminal MCP Server have an OpenSSF Scorecard?

Terminal MCP Server has an OpenSSF Scorecard score of 3.6/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 Terminal MCP Server actively maintained?

Stale. The repository has not been pushed to in 267 days. Consider whether the project is still being maintained.

What license does Terminal MCP Server use?

Terminal MCP Server ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are Terminal MCP Server's commits signed?

3% of the last 100 commits to Terminal MCP Server 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

medium confidence

Implemented

Terminal MCP Server 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 Terminal MCP Server'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

2026-08-12

Tool Surface Changed

Detected tool/plugin surface changed: extension-based → none

Maintain Terminal MCP Server?

For maintainers

HVTrust scores Terminal MCP Server 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

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Rank Moved

Rank rose 78 spots (#1270 → #1192)

2026-09-23

HVTrust Changed

HVTrust up 24.1pts (14.3 → 38.4)

2026-09-22

Newly Listed

First tracked at rank #1270

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-09

Rank Moved

Rank dropped 12 spots (#1155 → #1167)

2026-09-08

Rank Moved

Rank dropped 14 spots (#1141 → #1155)

2026-09-07

Rank Moved

Rank dropped 16 spots (#1125 → #1141)

2026-09-06

Rank Moved

Rank dropped 15 spots (#1110 → #1125)

2026-09-05

Rank Moved

Rank dropped 37 spots (#1073 → #1110)

2026-09-04

Rank Moved

Rank dropped 24 spots (#1049 → #1073)

2026-09-03

Rank Moved

Rank rose 154 spots (#1203 → #1049)

2026-09-03

HVTrust Changed

HVTrust up 12.8pts (26.3 → 39.1)

2026-09-02

Rank Moved

Rank dropped 255 spots (#948 → #1203)

2026-09-02

HVTrust Changed

HVTrust down 12.8pts (39.1 → 26.3)

2026-09-01

Rank Moved

Rank dropped 36 spots (#912 → #948)

2026-08-31

Rank Moved

Rank rose 183 spots (#1095 → #912)

2026-08-31

HVTrust Changed

HVTrust up 12.8pts (26.3 → 39.1)

2026-08-30

Rank Moved

Rank dropped 254 spots (#841 → #1095)

2026-08-30

HVTrust Changed

HVTrust down 12.8pts (39.1 → 26.3)

2026-08-29

Rank Moved

Rank dropped 40 spots (#801 → #841)

2026-08-28

Rank Moved

Rank dropped 22 spots (#779 → #801)

2026-08-27

Rank Moved

Rank dropped 23 spots (#756 → #779)

2026-08-26

Scorecard Added

OSSF Scorecard: 3.8/10

2026-08-26

Rank Moved

Rank rose 174 spots (#930 → #756)

2026-08-26

HVTrust Changed

HVTrust up 16.3pts (22.8 → 39.1)

2026-08-24

Rank Moved

Rank rose 333 spots (#1267 → #934)

2026-08-24

HVTrust Changed

HVTrust up 7.7pts (15.0 → 22.7)

2026-08-22

Rank Moved

Rank dropped 324 spots (#943 → #1267)

2026-08-22

HVTrust Changed

HVTrust down 7.7pts (22.7 → 15.0)

2026-08-19

Rank Moved

Rank rose 326 spots (#1267 → #941)

2026-08-19

HVTrust Changed

HVTrust up 7.9pts (15.0 → 22.9)

2026-08-17

Rank Moved

Rank dropped 322 spots (#945 → #1267)

2026-08-17

HVTrust Changed

HVTrust down 7.9pts (22.9 → 15.0)

2026-08-16

Rank Moved

Rank dropped 14 spots (#931 → #945)

2026-08-13

Rank Moved

Rank rose 309 spots (#1241 → #932)

2026-08-13

HVTrust Changed

HVTrust up 7.7pts (15.0 → 22.7)

2026-08-12

Tool Surface Changed

Detected tool/plugin surface changed: extension-based → none

2026-08-12

Rank Moved

Rank dropped 274 spots (#967 → #1241)

2026-08-12

HVTrust Changed

HVTrust down 7.1pts (22.1 → 15.0)

2026-08-10

Rank Moved

Rank dropped 58 spots (#903 → #961)

2026-08-08

Newly Listed

First tracked at rank #872

GitHub → npm: mcp-server-terminal

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/terminal-mcp-server.svg)](https://hvtracker.net/agents/terminal-mcp-server)
            
HTML:
            <a href="https://hvtracker.net/agents/terminal-mcp-server"><img src="https://hvtracker.net/badge/terminal-mcp-server.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