Is MCP Interactive Terminal safe to use?

MCP Interactive Terminal has an HVTrust score of 22.5/100 (Grade D), ranked #943 of 1283 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 22.5/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

22.5/100

Rank #943 of 1283

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 C · 2/5 signals

Last push

2026-02-16 · 177d ago

Recent change

Rank +1

Is MCP Interactive Terminal safe? MCP Interactive Terminal scores 22.5/100 (Grade D), ranked #943 of 1283 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; no OSSF Scorecard result yet; 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

#476 MCP Image — 22.6 (D) → #477 State Memory MCP — 22.6 (D) → #479 UniFi Gateway — 22.5 (D) → #480 Alpha Vantage MCP — 22.5 (D) →

Quick Trust Read

What Would Improve It

Add or improve OSSF Scorecard coverage so safety checks are easier to verify.

Recent Changes

2026-08-10

Rank Moved

Rank dropped 54 spots (#880 → #934)

2026-08-08

Newly Listed

First tracked at rank #869

Maintainer Checklist

Add Scorecard coverage Expose the repository to OpenSSF Scorecard checks so supply-chain posture is easier to verify.

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

12.5

Activity sub-score · out of 100

#478

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 C is separate — it grades how many independent signal types back the score (2 of 5), so a high score on thin evidence stays visible. Full methodology →

Rank Trend

2026-08-11 2026-08-12

Activity & Reach

Stars

Forks

Last Push

2026-02-16

177 days ago

Commits (4 wk)

Downloads (7d)

npm

HN mentions (30d)

—

Open Issues

Rank Change

▼3

was #940

Analysis

HVTrust Dimensions vs MCP Servers

22.5 / 100 · 67.0% confidence

MCP Interactive Terminal MCP Servers average (761 agents)

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

0 / 25

5.0 below avg 5.0

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

2.5 below avg 13.3

Transparency50% declared license · 50% OSSF Scorecard

8.5 / 17

in line with avg 8.8

Maintenance60% last-push freshness · 40% commit activity

0.2 / 20

12.2 below avg 12.4

AdoptionLog-scaled stars · package downloads

5.7 / 20

in line with avg 5.8

Activity Inputs

12.5 / 100

StarsRepository reach

7.7 / 30

FreshnessLast push recency

0.4 / 25

ActivityRecent commits

0.0 / 25

CommunityFork signal

4.2 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

—

Not available

Signed Commits

of last 100 commits verified

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?

No OpenSSF Scorecard data is currently published for MCP Interactive Terminal. Maintainers can enable the Scorecard GitHub Action to get a public score; without it, automated supply-chain hygiene is harder for outsiders to verify.

Is MCP Interactive Terminal actively maintained?

Slowing down. Last push was 177 days ago — keep an eye on whether activity resumes.

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

high confidence

1 tags

Broad capability areas detected.

shell

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-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)
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON