Pty MCP

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 17d ago

In detail: Pty MCP scores 45.1/100 (Grade D), ranked #1063 of 1325 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-09-09. Every point is earned from checkable signals — never paid placement. How scoring works →

How Pty MCP compares in MCP Servers

  1. #622 Storeshots MCP 45.3 +0.2
  2. #623 Glidermcp Com 45.2 +0.1
  3. #624 Pty MCP 45.1 this agent
  4. #625 CodeWiki MCP — AI-generated docs for GitHub repos 45.1 ±0
  5. #626 Strava MCP 45.1 ±0

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

Where the 45.1 comes from

HVTrust dimensions vs the MCP Servers average

45.1 / 100 · 100.0% confidence

Pty MCP MCP Servers average (775 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
5.0 / 25
5.3 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.9 / 17
in line with avg 12.2
Maintenance60% last-push freshness · 40% commit activity
13.7 / 20
1.6 above avg 12.1
AdoptionLog-scaled stars · package downloads
3.0 / 20
4.2 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-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
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.
40.9
Activity sub-score · out of 100
#624

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 →

Signals refreshed 2026-09-26 06:32 UTC · Repo last pushed 17 days ago

Rank Trend

2026-08-11 2026-09-26

Activity & Reach

Stars
16
Forks
2
Last Push
2026-09-09
17 days ago
Commits (4 wk)
4
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
0
Rank Change
▲2
was #1065

Analysis

Activity Inputs

40.9 / 100
StarsRepository reach
7.4 / 30
FreshnessLast push recency
22.6 / 25
ActivityRecent commits
8.7 / 25
CommunityFork signal
2.2 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
4.0 / 10
OpenSSF Scorecard · scanned Sep 17, 2026
Signed Commits
0%
of last 100 commits verified
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 9
Vulnerabilities 0

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 17 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.
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.

Reputation Timeline

Signal history
Rank 27HVTrust 3Listed 2Score 2Scorecard 1Delisted 1MCP 1Surface 1Surface 1
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)
2026-08-12
Rank Moved
Rank rose 15 spots (#1052 → #1037)
2026-08-11
Activity Score Changed
Activity score up 6pts (43 → 50)
2026-08-10
Rank Moved
Rank rose 60 spots (#1163 → #1103)
2026-08-10
HVTrust Changed
HVTrust up 4.2pts (15.1 → 19.3)
2026-08-10
Activity Score Changed
Activity score up 21pts (23 → 43)
2026-08-08
Newly Listed
First tracked at rank #1160

Embed Badge Badge guide for maintainers →

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