Is Substack MCP Server safe to use?

Substack MCP Server has an HVTrust score of 80.7/100 (Grade A), ranked #135 of 1325 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Substack MCP Server?

Substack MCP Server scores 80.7/100 on HVTracker's evidence-weighted HVTrust scale. It has 36 GitHub stars and is categorized under MCP Servers.

Substack MCP Server

conorbronsdon/substack-mcp

MCP server for Substack: rich drafts, Notes, analytics, and consented subscriber management across publications. Long-form posts stay draft-only; Notes publish immediately. Used regularly by multiple newsletters, includes a CLI.

MCP Servers TypeScript Listed MIT

Is Substack MCP Server safe? Strong public trust posture, backed by multiple independent signals.

OSSF Scorecard 6.2 / 10

Provenance Attested

Signed commits 36%

Last push yesterday

Compare Substack MCP Server

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: Substack MCP Server scores 80.7/100 (Grade A), ranked #135 of 1325 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 6.2/10; 36% of recent commits are signed; last pushed 2026-09-26. Every point is earned from checkable signals — never paid placement. How scoring works →

How Substack MCP Server compares in MCP Servers

Bars show each HVTrust score; the tick marks Substack MCP Server’s 80.7.

Where the 80.7 comes from

HVTrust dimensions vs the MCP Servers average

80.7 / 100 · 100.0% confidence

Substack MCP Server MCP Servers average (775 agents)

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

17.0 / 25

6.7 above avg 10.3

Identity / Provenance60% listing status · 40% build provenance

18.0 / 18

4.6 above avg 13.4

Transparency50% declared license · 50% OSSF Scorecard

13.8 / 17

1.6 above avg 12.2

Maintenance60% last-push freshness · 40% commit activity

19.9 / 20

7.9 above avg 12.0

AdoptionLog-scaled stars · package downloads

7.3 / 20

in line with avg 7.2

Quick Trust Read

What Would Improve It

Increase the share of verified signed commits for clearer maintainer identity.

Recent Changes

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

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 6.2/10. Tighten the weakest checks to improve public safety evidence.

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 Substack MCP Server View MCP Servers Report missing data

63.8

Activity sub-score · out of 100

#66

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 A reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →

Rank Trend

2026-08-11 2026-09-27

Activity & Reach

Stars

Forks

Last Push

2026-09-26

yesterday

Commits (4 wk)

203

Downloads (7d)

485

npm

HN mentions (30d)

—

Open Issues

Rank Change

▼2

was #133

Analysis

Activity Inputs

63.8 / 100

StarsRepository reach

9.4 / 30

FreshnessLast push recency

24.9 / 25

ActivityRecent commits

25 / 25

CommunityFork signal

4.4 / 20

Supply Chain Trust

Package Provenance

Verified

npm attestation

OSSF Scorecard

6.2 / 10

OpenSSF Scorecard · scanned Sep 26, 2026

Signed Commits

36%

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 10

Fuzzing 0

License 10

Maintained 10

Packaging 10

Pinned-Dependencies 10

SAST 0

Security-Policy 4

Signed-Releases -1

Token-Permissions 0

Vulnerabilities 10

Common questions about Substack MCP Server

Public supply-chain signals for Substack MCP Server are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but Substack MCP Server carries less obvious unverified-evidence risk than projects with thin signals.

Does Substack MCP Server publish package provenance?

Yes. Substack MCP Server's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.

Does Substack MCP Server have an OpenSSF Scorecard?

Substack MCP Server has an OpenSSF Scorecard score of 6.2/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 Substack MCP Server actively maintained?

Actively maintained. The repository was pushed to within the last 1 day(s).

What license does Substack MCP Server use?

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

Are Substack MCP Server's commits signed?

36% of the last 100 commits to Substack MCP Server 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

Substack MCP Server 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

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

How this surface has changed

Detected changes to Substack MCP Server'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

2026-09-23

Provenance Added

Package provenance attestation detected

2026-09-08

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-09-08

Provider Added

Runtime surface grew — new detected provider dependency: Anthropic

Maintain Substack MCP Server?

For maintainers

HVTrust scores Substack MCP Server 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-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

Provenance Added

Package provenance attestation detected

2026-09-23

Grade Changed

Trust grade D → A

2026-09-23

Rank Moved

Rank rose 540 spots (#674 → #134)

2026-09-23

HVTrust Changed

HVTrust up 49.2pts (31.4 → 80.6)

2026-09-22

Newly Listed

First tracked at rank #674

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-19

Grade Changed

Trust grade B → A

2026-09-19

Rank Moved

Rank rose 13 spots (#155 → #142)

2026-09-15

Rank Moved

Rank rose 24 spots (#176 → #152)

2026-09-14

Rank Moved

Rank dropped 15 spots (#161 → #176)

2026-09-08

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-09-08

Provider Added

Runtime surface grew — new detected provider dependency: Anthropic

2026-09-08

Rank Moved

Rank rose 29 spots (#186 → #157)

2026-09-08

Activity Score Changed

Activity score up 6pts (55 → 61)

2026-09-06

Rank Moved

Rank rose 46 spots (#235 → #189)

2026-09-05

Rank Moved

Rank dropped 60 spots (#175 → #235)

2026-09-04

Scorecard Added

OSSF Scorecard: 5.2/10

2026-09-04

Grade Changed

Trust grade C → B

2026-09-04

Rank Moved

Rank rose 219 spots (#394 → #175)

2026-09-04

HVTrust Changed

HVTrust up 10.9pts (62.3 → 73.2)

2026-09-03

Rank Moved

Rank dropped 17 spots (#377 → #394)

2026-09-02

Grade Changed

Trust grade D → C

2026-09-02

Rank Moved

Rank rose 484 spots (#861 → #377)

2026-09-02

HVTrust Changed

HVTrust up 19.2pts (42.7 → 61.9)

2026-09-01

Rank Moved

Rank dropped 28 spots (#833 → #861)

2026-08-31

Rank Moved

Rank dropped 34 spots (#799 → #833)

2026-08-30

Rank Moved

Rank dropped 28 spots (#771 → #799)

2026-08-29

Rank Moved

Rank dropped 21 spots (#750 → #771)

2026-08-29

Activity Score Changed

Activity score up 5pts (47 → 52)

2026-08-28

Rank Moved

Rank dropped 32 spots (#718 → #750)

2026-08-27

Rank Moved

Rank dropped 23 spots (#695 → #718)

2026-08-26

Rank Moved

Rank dropped 97 spots (#598 → #695)

2026-08-16

Rank Moved

Rank dropped 11 spots (#584 → #595)

2026-08-10

Rank Moved

Rank dropped 22 spots (#557 → #579)

2026-08-08

Newly Listed

First tracked at rank #551

GitHub → npm: @conorbronsdon/substack-mcp

Embed Badge Badge guide for maintainers →

For maintainers

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

Other agents in MCP Servers

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