Is MCP Interactive Terminal safe to use?

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

What is the trust score for MCP Interactive Terminal?

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

MCP Interactive Terminal

amol21p/mcp-interactive-terminal

MCP server that gives AI agents (Claude Code, Cursor, Windsurf) real interactive terminal sessions — REPLs, SSH, databas

MCP Servers TypeScript Grade D Listed MIT

34.0/100

Rank #1240 of 1328

Compare MCP Interactive Terminal

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Thin or incomplete trust evidence. Review carefully before production use.

Open compare tool Suggest correction

Listing state

Listed

Evidence coverage

Grade B · 3/5 signals

Last push

2026-02-16 · 204d ago

Recent change

Rank +7

Is MCP Interactive Terminal safe? MCP Interactive Terminal scores 34.0/100 (Grade D), ranked #1240 of 1328 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 1.6/10; recent commits are unsigned; last pushed 2026-02-16. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in MCP Servers

#739 Yuvalsuede Memory MCP — 34.1 (D) → #740 Tomyud1 Godot MCP — 34.1 (D) → #742 Nanobanana MCP Server — 33.7 (D) → #743 Chrome MCP Server — 33.7 (D) →

Quick Trust Read

What Would Improve It

Publish package provenance or release attestations for stronger supply-chain evidence.

Recent Changes

2026-09-08

Rank Moved

Rank dropped 17 spots (#1223 → #1240)

2026-09-07

Rank Moved

Rank dropped 14 spots (#1209 → #1223)

2026-09-06

Rank Moved

Rank dropped 15 spots (#1194 → #1209)

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 1.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 204 days ago. Fresh activity helps separate stable projects from stale ones.

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

11.6

Activity sub-score · out of 100

#741

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

Activity & Reach

Stars

Forks

Last Push

2026-02-16

204 days ago

Commits (4 wk)

Downloads (7d)

npm

HN mentions (30d)

—

Open Issues

Rank Change

▼17

was #1223

Analysis

HVTrust Dimensions vs MCP Servers

34.0 / 100 · 100.0% confidence

MCP Interactive Terminal MCP Servers average (778 agents)

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

2.0 / 25

7.9 below avg 9.9

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

2.6 below avg 13.4

Transparency50% declared license · 50% OSSF Scorecard

9.9 / 17

2.1 below avg 12.0

Maintenance60% last-push freshness · 40% commit activity

0 / 20

12.2 below avg 12.2

AdoptionLog-scaled stars · package downloads

5.3 / 20

1.6 below avg 6.9

Activity Inputs

11.6 / 100

StarsRepository reach

7.7 / 30

FreshnessLast push recency

0.0 / 25

ActivityRecent commits

0.0 / 25

CommunityFork signal

3.9 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

1.6 / 10

OpenSSF Scorecard · scanned Sep 7, 2026

Signed Commits

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 0

CI-Tests -1

CII-Best-Practices 0

Code-Review 0

Contributors 3

Dangerous-Workflow -1

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 0

Packaging -1

Pinned-Dependencies -1

SAST 0

Security-Policy 0

Signed-Releases -1

Token-Permissions -1

Vulnerabilities 0

Is MCP Interactive Terminal safe?

Public trust evidence for MCP Interactive Terminal 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 MCP Interactive Terminal publish package provenance?

No published build provenance is currently detected for MCP Interactive Terminal. 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 Interactive Terminal have an OpenSSF Scorecard?

MCP Interactive Terminal has an OpenSSF Scorecard score of 1.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 MCP Interactive Terminal actively maintained?

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

What license does MCP Interactive Terminal use?

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

Are MCP Interactive Terminal's commits signed?

0% of the last 100 commits to MCP Interactive Terminal 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 Interactive Terminal appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

high confidence

1 detected

Public provider/service dependencies detected.

Anthropic

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

Maintain MCP Interactive Terminal?

For maintainers

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

Rank Moved

Rank dropped 17 spots (#1223 → #1240)

2026-09-07

Rank Moved

Rank dropped 14 spots (#1209 → #1223)

2026-09-06

Rank Moved

Rank dropped 15 spots (#1194 → #1209)

2026-09-05

Rank Moved

Rank dropped 30 spots (#1164 → #1194)

2026-09-04

Rank Moved

Rank dropped 15 spots (#1149 → #1164)

2026-09-03

Rank Moved

Rank dropped 45 spots (#1104 → #1149)

2026-09-02

Rank Moved

Rank dropped 43 spots (#1061 → #1104)

2026-09-01

Rank Moved

Rank dropped 39 spots (#1022 → #1061)

2026-08-31

Rank Moved

Rank dropped 33 spots (#989 → #1022)

2026-08-30

Rank Moved

Rank dropped 53 spots (#936 → #989)

2026-08-29

Rank Moved

Rank dropped 50 spots (#886 → #936)

2026-08-28

Scorecard Added

OSSF Scorecard: 1.6/10

2026-08-28

Rank Moved

Rank rose 161 spots (#1047 → #886)

2026-08-28

HVTrust Changed

HVTrust up 11.8pts (22.6 → 34.4)

2026-08-27

Rank Moved

Rank dropped 21 spots (#1026 → #1047)

2026-08-26

Rank Moved

Rank dropped 92 spots (#934 → #1026)

2026-08-22

Rank Moved

Rank rose 11 spots (#944 → #933)

2026-08-17

Rank Moved

Rank rose 12 spots (#957 → #945)

2026-08-16

Rank Moved

Rank dropped 25 spots (#932 → #957)

2026-08-13

Rank Moved

Rank dropped 14 spots (#919 → #933)

2026-08-12

Rank Moved

Rank rose 21 spots (#940 → #919)

2026-08-10

Rank Moved

Rank dropped 54 spots (#880 → #934)

2026-08-08

Newly Listed

First tracked at rank #869

GitHub → npm: mcp-interactive-terminal

Embed Badge Badge guide for maintainers →

For maintainers

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