Hackmd MCP

A Model Context Protocol server for integrating HackMD's note-taking platform with AI assistants.

MCP Servers TypeScript Listed MIT

Is Hackmd MCP safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 3.5 / 10
Provenance Attested
Signed commits 100%
Last push 75d ago
Compare Hackmd MCP
Suggest a correction

In detail: Hackmd MCP scores 65.3/100 (Grade B), ranked #468 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 3.5/10; 100% of recent commits are signed; last pushed 2026-07-13. Every point is earned from checkable signals — never paid placement. How scoring works →

How Hackmd MCP compares in MCP Servers

  1. #268 Apache Pinot MCP Server 65.3 ±0
  2. #269 Google Workspace MCP 65.3 ±0
  3. #270 Hackmd MCP 65.3 this agent
  4. #271 Korea Stock MCP 65.3 ±0
  5. #272 MCP Uptime Kuma 65.1 −0.2

Bars show each HVTrust score; the tick marks Hackmd MCP’s 65.3.

Where the 65.3 comes from

HVTrust dimensions vs the MCP Servers average

65.3 / 100 · 100.0% confidence

Hackmd MCP MCP Servers average (775 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
16.9 / 25
6.6 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
11.5 / 17
0.7 below avg 12.2
Maintenance60% last-push freshness · 40% commit activity
7.0 / 20
5.1 below avg 12.1
AdoptionLog-scaled stars · package downloads
6.9 / 20
in line with avg 7.2

Quick Trust Read

What Would Improve It
Improve adoption to lift the weakest part of the trust profile.
Recent Changes
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 → B
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 3.5/10. Tighten the weakest checks to improve public safety evidence.
Refresh maintenance signals The repo was last pushed 75 days ago. Fresh activity helps separate stable projects from stale ones.
31.5
Activity sub-score · out of 100
#270

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade B 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 →

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

Rank Trend

2026-08-11 2026-09-26

Activity & Reach

Stars
67
Forks
17
Last Push
2026-07-13
75 days ago
Commits (4 wk)
0
Downloads (7d)
75
npm
HN mentions (30d)
—
Open Issues
0
Rank Change
▼1
was #467

Analysis

Activity Inputs

31.5 / 100
StarsRepository reach
11.0 / 30
FreshnessLast push recency
14.6 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
5.8 / 20

Supply Chain Trust

Package Provenance
Verified
npm attestation
OSSF Scorecard
3.5 / 10
OpenSSF Scorecard · scanned Sep 25, 2026
Signed Commits
100%
of last 100 commits verified
Binary-Artifacts 10
Branch-Protection 3
CI-Tests -1
CII-Best-Practices 0
Code-Review 0
Contributors 10
Dangerous-Workflow 10
Dependency-Update-Tool 0
Fuzzing 0
License 10
Maintained 0
Packaging 10
Pinned-Dependencies 0
SAST 0
Security-Policy 0
Signed-Releases 0
Token-Permissions 8
Vulnerabilities 0

Common questions about Hackmd MCP

Hackmd MCP 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 Hackmd MCP publish package provenance?
Yes. Hackmd MCP's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.
Does Hackmd MCP have an OpenSSF Scorecard?
Hackmd MCP has an OpenSSF Scorecard score of 3.5/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 Hackmd MCP actively maintained?
Slowing down. Last push was 75 days ago — keep an eye on whether activity resumes.
What license does Hackmd MCP use?
Hackmd MCP ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Hackmd MCP's commits signed?
100% of the last 100 commits to Hackmd 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
Hackmd MCP appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
low confidence
None detected
No clear third-party provider dependency detected.
Credential signal: API keys or service config markers documented.
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
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 Hackmd 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
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Provenance Added
Package provenance attestation detected

Maintain Hackmd MCP?

For maintainers

HVTrust scores Hackmd 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 22HVTrust 3Listed 2Grade 2Scorecard 1Delisted 1Provenance 1MCP 1
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 → B
2026-09-23
Rank Moved
Rank rose 722 spots (#1178 → #456)
2026-09-23
HVTrust Changed
HVTrust up 45.7pts (19.9 → 65.6)
2026-09-22
Newly Listed
First tracked at rank #1178
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-20
Rank Moved
Rank rose 15 spots (#445 → #430)
2026-09-11
Rank Moved
Rank dropped 16 spots (#400 → #416)
2026-09-10
Rank Moved
Rank dropped 12 spots (#388 → #400)
2026-09-09
Rank Moved
Rank dropped 10 spots (#378 → #388)
2026-09-08
Grade Changed
Trust grade D → B
2026-09-08
Rank Moved
Rank rose 654 spots (#1032 → #378)
2026-09-08
HVTrust Changed
HVTrust up 22.5pts (44.4 → 66.9)
2026-09-07
Rank Moved
Rank dropped 33 spots (#999 → #1032)
2026-09-06
Rank Moved
Rank dropped 16 spots (#983 → #999)
2026-09-05
Rank Moved
Rank dropped 48 spots (#935 → #983)
2026-09-04
Rank Moved
Rank dropped 29 spots (#906 → #935)
2026-09-03
Rank Moved
Rank dropped 52 spots (#854 → #906)
2026-09-02
Rank Moved
Rank dropped 43 spots (#811 → #854)
2026-09-01
Rank Moved
Rank dropped 29 spots (#782 → #811)
2026-08-31
Rank Moved
Rank dropped 33 spots (#749 → #782)
2026-08-30
Rank Moved
Rank dropped 27 spots (#722 → #749)
2026-08-29
Scorecard Added
OSSF Scorecard: 3.5/10
2026-08-29
Rank Moved
Rank rose 60 spots (#782 → #722)
2026-08-29
HVTrust Changed
HVTrust up 4.9pts (39.9 → 44.8)
2026-08-28
Rank Moved
Rank dropped 24 spots (#758 → #782)
2026-08-27
Rank Moved
Rank dropped 27 spots (#731 → #758)
2026-08-26
Rank Moved
Rank dropped 97 spots (#634 → #731)
2026-08-16
Rank Moved
Rank dropped 13 spots (#614 → #627)
2026-08-12
Rank Moved
Rank dropped 17 spots (#594 → #611)
2026-08-10
Rank Moved
Rank dropped 20 spots (#574 → #594)
2026-08-08
Newly Listed
First tracked at rank #573

Embed Badge Badge guide for maintainers →

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