updated 2026-10-16 16:07 UTC

Chat on Steroids

Repository

Cross-platform local MCP capabilities for ChatGPT with Chrome integration, Goal, Compact & Resume, and durable multi-agent workflows.

MCP Servers TypeScript Listed MIT

Is Chat on Steroids safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 5.6 / 10
Provenance None
Signed commits 37%
Last push today
Compare Chat on Steroids

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →
Suggest a correction

In detail: Chat on Steroids scores 63.5/100 (Grade C), ranked #569 of 1378 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 5.6/10; 37% of recent commits are signed; last pushed 2026-10-16. Every point is earned from checkable signals — never paid placement. How scoring works →

How Chat on Steroids 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.

Already done? Suggest a correctionAdd the trust badge

Chain of custody

Scanners check what the code says. This traces who ships Chat on Steroids 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.

  1. Source Partly signed

    github.com/totec448-spec/chat-on-steroids, MIT, last pushed 2026-10-16. 37% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.

  2. Review and release Mixed

    OpenSSF Scorecard rates the repository's practices 5.6/10 (scanned Oct 13, 2026). The checks that decide who can get a change released:

    • Code Review2
    • Branch Protection0
    • Signed Releases0
    • Dangerous Workflow10
    • Token Permissions10
    • Pinned Dependencies9
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 0
    CI-Tests 10
    CII-Best-Practices 0
    Code-Review 2
    Contributors 10
    Dangerous-Workflow 10
    Dependency-Update-Tool 10
    Fuzzing 0
    License 10
    Maintained 0
    Packaging -1
    Pinned-Dependencies 9
    SAST 10
    Security-Policy 4
    Signed-Releases 0
    Token-Permissions 10
    Vulnerabilities 4

  3. Published packages None

    No registry package. Chat on Steroids 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-10-13 OSSF Scorecard: 5.7/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 Chat on Steroids’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 Chat on Steroids compares in MCP Servers

  1. #315 IDA Pro MCP 63.6 +0.1
  2. #316 Web Researcher MCP 63.5 ±0
  3. #317 Chat on Steroids 63.5 this agent
  4. #318 Galaxy MCP 63.5 ±0
  5. #319 Waggle MCP 63.4 −0.1

Bars show each HVTrust score; the tick marks Chat on Steroids’s 63.5.

Where the 63.5 comes from

HVTrust dimensions vs the MCP Servers average

63.5 / 100 · 100.0% confidence

Chat on Steroids MCP Servers average (781 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
8.8 / 25
1.7 below avg 10.5
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.7 below avg 13.5
Transparency50% declared license · 50% OSSF Scorecard
13.3 / 17
1.0 above avg 12.3
Maintenance60% last-push freshness · 40% commit activity
20.0 / 20
7.7 above avg 12.3
AdoptionLog-scaled stars · package downloads
8.9 / 20
1.5 above avg 7.4

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-10-14
Rank Moved
Rank dropped 15 spots (#555 → #570)
2026-10-13
Scorecard Added
OSSF Scorecard: 5.7/10
2026-10-13
Grade Changed
Trust grade D → C
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 5.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.
Compare with another agent Get email alerts for Chat on Steroids View MCP Servers Report missing data
85.3
Activity sub-score · out of 100
#317
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 C 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-10-16 16:07 UTC · Repo last pushed today

Rank Trend

2026-09-29 2026-10-16

Activity & Reach

Stars
4.9k
Forks
648
Last Push
2026-10-16
today
Commits (4 wk)
2366
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
18
Rank Change
▼4
was #565

Analysis

Activity Inputs

85.3 / 100
StarsRepository reach
22.2 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
13.1 / 20

Common questions about Chat on Steroids

Chat on Steroids has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.
Does Chat on Steroids publish package provenance?
No published build provenance is currently detected for Chat on Steroids. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Chat on Steroids have an OpenSSF Scorecard?
Chat on Steroids has an OpenSSF Scorecard score of 5.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 Chat on Steroids actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does Chat on Steroids use?
Chat on Steroids ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Chat on Steroids's commits signed?
37% of the last 100 commits to Chat on Steroids 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
Chat on Steroids appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
medium confidence
1 detected
Public provider/service dependencies detected.
Credential signal: No explicit API-key/config marker detected.
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

Maintain Chat on Steroids?

For maintainers

HVTrust scores Chat on Steroids 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
Rank 3Listed 1HVTrust 1Grade 1Scorecard 1
2026-10-14
Rank Moved
Rank dropped 15 spots (#555 → #570)
2026-10-13
Scorecard Added
OSSF Scorecard: 5.7/10
2026-10-13
Grade Changed
Trust grade D → C
2026-10-13
Rank Moved
Rank rose 792 spots (#1347 → #555)
2026-10-13
HVTrust Changed
HVTrust up 37.1pts (26.7 → 63.8)
2026-10-09
Rank Moved
Rank dropped 13 spots (#1323 → #1336)
2026-09-29
Newly Listed
First tracked at rank #1317
GitHub →

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 63.5 Grade C
Markdown:
[![HVTrust](https://hvtracker.net/badge/chat-on-steroids.svg)](https://hvtracker.net/agents/chat-on-steroids)
HTML:
<a href="https://hvtracker.net/agents/chat-on-steroids"><img src="https://hvtracker.net/badge/chat-on-steroids.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