Is Pty MCP safe to use?

Pty MCP has an HVTrust score of 46.3/100 (Grade D), ranked #1098 of 1374 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Pty MCP?

Pty MCP scores 46.3/100 on HVTracker's evidence-weighted HVTrust scale. It has 20 GitHub stars and is categorized under MCP Servers.

Pty MCP

Repository

MCP server for interactive terminal sessions — local shells, SSH, serial ports, and persistent remote sessions

MCP Servers Go Listed MIT

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

OSSF Scorecard 4.0 / 10

Provenance None

Signed commits 0%

Last push 19d ago

Compare Pty MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: Pty MCP scores 46.3/100 (Grade D), ranked #1098 of 1374 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 4.0/10; recent commits are unsigned; last pushed 2026-10-22. Every point is earned from checkable signals — never paid placement. How scoring works →

How Pty MCP 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.

Raise the OSSF Scorecard from 4.0 to 9.0lowest checks: Branch-Protection 0, CII-Best-Practices 0, Code-Review 0 +10.4 → 56.7 C · #436 of 778
Sign every commit0% signed today +5.0 → 51.3 C · #543 of 778

Already done? Suggest a correction Add the trust badge

Chain of custody

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

Source Unsigned

github.com/raychao-oao/pty-mcp, MIT, last pushed 2026-10-22. None of the last 100 commits carry a verified signature, so no change traces to a verified identity.
Review and release Mixed

OpenSSF Scorecard rates the repository's practices 4.0/10 (scanned Nov 4, 2026). The checks that decide who can get a change released:
- Code Review0
- Branch Protection0
- Signed Releases0
- Dangerous Workflow10
- Token Permissions0
- Pinned Dependencies0
All 18 Scorecard checks

Binary-Artifacts 10

Branch-Protection 0

CI-Tests -1

CII-Best-Practices 0

Code-Review 0

Contributors 0

Dangerous-Workflow 10

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 10

Packaging -1

Pinned-Dependencies 0

SAST 0

Security-Policy 10

Signed-Releases 0

Token-Permissions 0

Vulnerabilities 9
Published packages None

No registry package. Pty MCP is used from its repository, so what you run is whatever you check out: pin a release tag or commit.

Changes to this chain

2026-09-02 OSSF Scorecard: 4.0/10

Evidence behind this score

Coverage C: 2 of 5 independent evidence types found.

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

Verify this score yourself

Every build re-issues Pty MCP’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 Pty MCP compares in MCP Servers

#622 Godot MCP 46.6 +0.3
#623 MCP Slim Guard 46.4 +0.1
#624 Pty MCP 46.3 this agent
#625 Chart Library — Pattern Intelligence 46.2 −0.1
#626 Help Scout MCP Server 46.2 −0.1

Bars show each HVTrust score; the tick marks Pty MCP’s 46.3.

Where the 46.3 comes from

HVTrust dimensions vs the MCP Servers average

46.3 / 100 · 100.0% confidence

Pty MCP MCP Servers average (778 agents)

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

5.0 / 25

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

11.9 / 17

in line with avg 12.3

Maintenance60% last-push freshness · 40% commit activity

14.7 / 20

2.5 above avg 12.2

AdoptionLog-scaled stars · package downloads

3.2 / 20

4.4 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-01

Rank Moved

Rank dropped 14 spots (#1068 → #1082)

2026-10-22

Rank Moved

Rank rose 64 spots (#1123 → #1059)

2026-10-22

HVTrust Changed

HVTrust up 3.2pts (45.0 → 48.2)

Maintainer Checklist

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

Compare with another agent View MCP Servers Report missing data

45.0

Activity sub-score · out of 100

#624

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-09-29 2026-11-10

Activity & Reach

Stars

Forks

Last Push

2026-10-22

19 days ago

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

▲1

was #1099

Analysis

Activity Inputs

45.0 / 100

StarsRepository reach

7.9 / 30

FreshnessLast push recency

22.4 / 25

ActivityRecent commits

12.5 / 25

CommunityFork signal

2.2 / 20

Common questions about Pty MCP

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

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

Does Pty MCP have an OpenSSF Scorecard?

Pty MCP has an OpenSSF Scorecard score of 4.0/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 Pty MCP actively maintained?

Maintained. Last push was 19 days ago.

What license does Pty MCP use?

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

Are Pty MCP's commits signed?

0% of the last 100 commits to Pty MCP 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

Pty MCP 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: API keys or service config markers documented.

Tool / Plugin Surface

high confidence

Declared

Declared plugin/integration surface detected.

Detailed evidence is not shown in the public view.

Package Provenance Drift

N/A

No package source configured

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 Pty MCP'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

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-09-23

Provider Added

Runtime surface grew — new detected provider dependency: Anthropic

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

Maintain Pty MCP?

For maintainers

HVTrust scores Pty MCP 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-11-01

Rank Moved

Rank dropped 14 spots (#1068 → #1082)

2026-10-22

Rank Moved

Rank rose 64 spots (#1123 → #1059)

2026-10-22

HVTrust Changed

HVTrust up 3.2pts (45.0 → 48.2)

2026-10-22

Activity Score Changed

Activity score up 9pts (41 → 50)

2026-10-10

Rank Moved

Rank rose 29 spots (#1110 → #1081)

2026-10-09

Rank Moved

Rank dropped 27 spots (#1083 → #1110)

2026-10-02

Rank Moved

Rank rose 21 spots (#1087 → #1066)

2026-10-02

Activity Score Changed

Activity score up 7pts (40 → 47)

2026-09-25

Rank Moved

Rank dropped 11 spots (#1054 → #1065)

2026-09-23

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-09-23

Provider Added

Runtime surface grew — new detected provider dependency: Anthropic

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Rank Moved

Rank dropped 488 spots (#564 → #1052)

2026-09-23

HVTrust Changed

HVTrust up 9.2pts (36.1 → 45.3)

2026-09-22

Newly Listed

First tracked at rank #564

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-17

Rank Moved

Rank rose 33 spots (#1068 → #1035)

2026-09-16

Rank Moved

Rank dropped 13 spots (#1055 → #1068)

2026-09-13

Rank Moved

Rank dropped 50 spots (#1001 → #1051)

2026-09-12

Rank Moved

Rank dropped 25 spots (#976 → #1001)

2026-09-10

Rank Moved

Rank dropped 34 spots (#933 → #967)

2026-09-09

Rank Moved

Rank rose 29 spots (#962 → #933)

2026-09-08

Rank Moved

Rank dropped 16 spots (#946 → #962)

2026-09-07

Rank Moved

Rank dropped 39 spots (#907 → #946)

2026-09-06

Rank Moved

Rank dropped 14 spots (#893 → #907)

2026-09-05

Rank Moved

Rank dropped 55 spots (#838 → #893)

2026-09-04

Rank Moved

Rank dropped 35 spots (#803 → #838)

2026-09-03

Rank Moved

Rank dropped 48 spots (#755 → #803)

2026-09-02

Scorecard Added

OSSF Scorecard: 4.0/10

2026-09-02

Rank Moved

Rank rose 490 spots (#1245 → #755)

2026-09-02

HVTrust Changed

HVTrust up 28.0pts (20.3 → 48.3)

2026-09-01

Rank Moved

Rank dropped 19 spots (#1226 → #1245)

2026-08-31

Rank Moved

Rank dropped 26 spots (#1200 → #1226)

2026-08-30

Rank Moved

Rank dropped 23 spots (#1177 → #1200)

2026-08-29

Rank Moved

Rank dropped 26 spots (#1151 → #1177)

2026-08-28

Rank Moved

Rank dropped 22 spots (#1129 → #1151)

2026-08-27

Rank Moved

Rank dropped 19 spots (#1110 → #1129)

2026-08-26

Rank Moved

Rank dropped 67 spots (#1043 → #1110)

2026-08-17

Rank Moved

Rank rose 24 spots (#1060 → #1036)

2026-08-16

Rank Moved

Rank dropped 36 spots (#1024 → #1060)

2026-08-13

Rank Moved

Rank rose 15 spots (#1037 → #1022)

GitHub →

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/pty-mcp.svg)](https://hvtracker.net/agents/pty-mcp)
            
HTML:
            <a href="https://hvtracker.net/agents/pty-mcp"><img src="https://hvtracker.net/badge/pty-mcp.svg" alt="HVTrust"></a>

Other agents in MCP Servers

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

Pty MCP

How Pty MCP could raise its score

Chain of custody

Source Unsigned

Review and release Mixed

Published packages None

Changes to this chain

Evidence behind this score

Verify this score yourself

What this score doesn’t check

How Pty MCP compares in MCP Servers

Where the 46.3 comes from

HVTrust dimensions vs the MCP Servers average

Quick Trust Read

Rank Trend

Activity & Reach

Analysis

Activity Inputs

Common questions about Pty MCP

AI agent surface

Maintain Pty MCP?

Reputation Timeline

Embed Badge Badge guide for maintainers →

Other agents in MCP Servers