updated 2026-09-26 12:32 UTC

SocialGPT

scrollmark/socialgpt-mcp

Connect SocialGPT to Claude, ChatGPT, Cursor, and any MCP-compatible AI agent.

MCP Servers Python Listed MIT

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

OSSF Scorecard 3.8 / 10
Provenance None
Signed commits 46%
Last push 54d ago
Compare SocialGPT

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →
Suggest a correction

In detail: SocialGPT scores 42.4/100 (Grade D), ranked #1113 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 3.8/10; 46% of recent commits are signed; last pushed 2026-08-03. Every point is earned from checkable signals — never paid placement. How scoring works →

How SocialGPT compares in MCP Servers

  1. #655 Scopus MCP 42.6 +0.2
  2. #656 Spec Workflow MCP 42.5 +0.1
  3. #657 SocialGPT 42.4 this agent
  4. #658 CleanSlice 42.4 ±0
  5. #659 Multi Gmail MCP 42.3 −0.1

Bars show each HVTrust score; the tick marks SocialGPT’s 42.4.

Where the 42.4 comes from

HVTrust dimensions vs the MCP Servers average

42.4 / 100 · 100.0% confidence

SocialGPT MCP Servers average (775 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
7.0 / 25
3.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.7 / 17
0.5 below avg 12.2
Maintenance60% last-push freshness · 40% commit activity
8.4 / 20
3.6 below avg 12.0
AdoptionLog-scaled stars · package downloads
2.5 / 20
4.7 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-24
Rank Moved
Rank dropped 13 spots (#1098 → #1111)
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Rank Moved
Rank dropped 379 spots (#719 → #1098)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 3.8/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 54 days ago. Fresh activity helps separate stable projects from stale ones.
Compare with another agent Get email alerts for SocialGPT View MCP Servers Report missing data
25.2
Activity sub-score · out of 100
#657
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 →

Signals refreshed 2026-09-26 12:32 UTC · Repo last pushed 54 days ago

Rank Trend

2026-08-11 2026-09-26

Activity & Reach

Stars
10
Forks
1
Last Push
2026-08-03
54 days ago
Commits (4 wk)
0
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
0
Rank Change
=
was #1113

Analysis

Activity Inputs

25.2 / 100
StarsRepository reach
6.2 / 30
FreshnessLast push recency
17.5 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
1.4 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
3.8 / 10
OpenSSF Scorecard · scanned Sep 24, 2026
Signed Commits
46%
of last 100 commits verified
Binary-Artifacts 10
Branch-Protection 3
CI-Tests 10
CII-Best-Practices 0
Code-Review 0
Contributors 3
Dangerous-Workflow 10
Dependency-Update-Tool 0
Fuzzing 0
License 10
Maintained 3
Packaging -1
Pinned-Dependencies 0
SAST 0
Security-Policy 0
Signed-Releases -1
Token-Permissions 0
Vulnerabilities 10

Common questions about SocialGPT

Public trust evidence for SocialGPT 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 SocialGPT publish package provenance?
No published build provenance is currently detected for SocialGPT. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does SocialGPT have an OpenSSF Scorecard?
SocialGPT has an OpenSSF Scorecard score of 3.8/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 SocialGPT actively maintained?
Slowing down. Last push was 54 days ago — keep an eye on whether activity resumes.
What license does SocialGPT use?
SocialGPT ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are SocialGPT's commits signed?
45% of the last 100 commits to SocialGPT 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
medium confidence
Implemented
SocialGPT appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
None detected
No clear third-party provider dependency detected.
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
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 SocialGPT'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
Mcp Status Changed
Detected MCP server support changed: none → implemented

Maintain SocialGPT?

For maintainers

HVTrust scores SocialGPT 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 22Listed 2HVTrust 2Score 1Scorecard 1Delisted 1MCP 1
2026-09-24
Rank Moved
Rank dropped 13 spots (#1098 → #1111)
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Rank Moved
Rank dropped 379 spots (#719 → #1098)
2026-09-23
HVTrust Changed
HVTrust up 12.7pts (30.4 → 43.1)
2026-09-22
Newly Listed
First tracked at rank #719
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-12
Rank Moved
Rank dropped 14 spots (#1065 → #1079)
2026-09-09
Rank Moved
Rank dropped 16 spots (#1043 → #1059)
2026-09-08
Rank Moved
Rank dropped 13 spots (#1030 → #1043)
2026-09-06
Rank Moved
Rank dropped 16 spots (#1016 → #1032)
2026-09-05
Rank Moved
Rank dropped 45 spots (#971 → #1016)
2026-09-04
Rank Moved
Rank dropped 28 spots (#943 → #971)
2026-09-03
Rank Moved
Rank dropped 58 spots (#885 → #943)
2026-09-02
Scorecard Added
OSSF Scorecard: 3.6/10
2026-09-02
Rank Moved
Rank rose 376 spots (#1261 → #885)
2026-09-02
HVTrust Changed
HVTrust up 24.1pts (19.6 → 43.7)
2026-09-02
Activity Score Changed
Activity score down 6pts (35 → 28)
2026-09-01
Rank Moved
Rank dropped 17 spots (#1244 → #1261)
2026-08-31
Rank Moved
Rank dropped 19 spots (#1225 → #1244)
2026-08-30
Rank Moved
Rank dropped 17 spots (#1208 → #1225)
2026-08-29
Rank Moved
Rank dropped 27 spots (#1181 → #1208)
2026-08-28
Rank Moved
Rank dropped 20 spots (#1161 → #1181)
2026-08-27
Rank Moved
Rank dropped 14 spots (#1147 → #1161)
2026-08-26
Rank Moved
Rank dropped 52 spots (#1095 → #1147)
2026-08-24
Rank Moved
Rank dropped 11 spots (#1078 → #1089)
2026-08-17
Rank Moved
Rank rose 11 spots (#1083 → #1072)
2026-08-16
Rank Moved
Rank dropped 30 spots (#1053 → #1083)
2026-08-12
Rank Moved
Rank rose 13 spots (#1060 → #1047)
2026-08-10
Rank Moved
Rank dropped 66 spots (#989 → #1055)
2026-08-08
Newly Listed
First tracked at rank #983
GitHub →

Embed Badge Badge guide for maintainers →

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