hackmd-mcp

MCPattested

v1.5.7yuna0x0MITUpdated 9mo agonpm GitHub

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

Works in

ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Attested build

A verified provenance attestation binds this artifact to the listed repository. Nobody has claimed the listing yet — this proves where the code was built, not who stands behind it.

97Downloads/wk

9mo agoLast update

Needs 1 credential before it runs

HACKMD_API_TOKENAPI keyrequired
Your HackMD API token for API authentication

Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.

Package

Authoryuna0x0

LicenseMIT

Version1.5.7

Sourcenpm+mcp-registry

GitHubyuna0x0/hackmd-mcp

SBOMCycloneDX 1.6 ↓

Trust Status

A

85/100Trusted

✓Listed in Forge index+10/10

✓Identity verified · attested build+20/20

—Ed25519 publish signature+0/5

→ Included automatically when the publisher runs `forge publish`

—Domain verification+0/5

→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }

✓npm Trusted Publishing (Sigstore)+5/5

—npm maintainer match+0/5

→ Publisher: add the verified GitHub login to the npm package's maintainers (npm owner add <login>)

✓CVE scan · clean+30/30

✓Static analysis · clean+20/20

Paste into Claude Code, Cursor, or any AI assistant to fix all gaps

StatusIdentity verified

PublisherUnverified

SignatureUnsigned

Domain—

Provenance✓ Sigstore-verified · 7192414

Dependencies✓ 60 resolved+ · none vulnerable

Tool surface12 tools · 2 privileged

Security scan✓ Cleanv1.5.7 · 3d agoHow well does this scan work?

EvalsNone

IndexedAug 28, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

12 tools · 2 privileged

Statically extracted from the published packagev1.5.7 · 3d ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

Filter toolsPrivileged only

get_historyGet user's reading history

Get user's reading history

No input schema was published for this tool.

get_user_infoGet information about the authenticated user

Get information about the authenticated user

No input schema was published for this tool.

list_team_notesList all notes in a team

List all notes in a team

No input schema was published for this tool.

create_team_noteCreate a new note in a team

Create a new note in a team

No input schema was published for this tool.

update_team_noteUpdate an existing note in a team

Update an existing note in a team

No input schema was published for this tool.

delete_team_noteprivilegedDelete a note in a team

Delete a note in a team

No input schema was published for this tool.

list_teamsList all teams accessible to the user

List all teams accessible to the user

No input schema was published for this tool.

list_user_notesList all notes owned by the user

List all notes owned by the user

No input schema was published for this tool.

get_noteGet a note by its ID

Get a note by its ID

No input schema was published for this tool.

create_noteCreate a new note

Create a new note

No input schema was published for this tool.

update_noteUpdate an existing note

Update an existing note

No input schema was published for this tool.

delete_noteprivilegedDelete a note

Delete a note

No input schema was published for this tool.

12 of 12 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

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

Keywords

apiaimcphackmdllmmcp-server

Alternatives

Comparing tool surfaces…

Tools exposed

12 tools · 2 privileged · observed 2026-08-30 by static extraction. A tool surface is what one scan read on one day, not a live capability list.

Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.

Dependency tree

What one Forge scan resolved from npm metadata on 2026-08-30 — observed resolution, not a publisher declaration.

60 packages resolved · 6 direct · none carrying advisories Resolution stops at depth 4 and 60 packages.

zod4.5.4
cors2.8.62 dependencies
- object-assign4.1.1
- vary1.1.2
dotenv17.4.2
express5.2.1+11 not drawn17 dependencies
- qs6.16.0+2 not drawn
- depd2.0.0
- etag1.8.1
- once1.4.0+1 not drawn
- send1.2.1+5 not drawn6 dependencies
  - debug4.4.3+1 not drawn
  - encodeurl2.0.0
  - etag1.8.1shown above
  - fresh2.0.0
  - mime-types3.0.2+1 not drawn
  - statuses2.0.2
- vary1.1.2shown above
- debug4.4.3shown above+1 not drawn
- fresh2.0.0shown above
- cookie0.7.2
- router2.2.0+2 not drawn3 dependencies
  - debug4.4.3shown above+1 not drawn
  - depd2.0.0shown above
  - parseurl1.3.3
- accepts2.0.0+1 not drawn1 dependency
  - mime-types3.0.2shown above+1 not drawn
- type-is2.1.0+2 not drawn1 dependency
  - mime-types3.0.2shown above+1 not drawn
- parseurl1.3.3shown above
- statuses2.0.2shown above
- encodeurl2.0.0shown above
- mime-types3.0.2shown above+1 not drawn
- proxy-addr2.0.7+2 not drawn
@hackmd/api2.7.0+2 not drawn
@modelcontextprotocol/sdk1.30.0+14 not drawn3 dependencies
- zod4.5.4shown above
- cors2.8.6shown above
- express5.2.1shown above+11 not drawn

The crawl stopped at the 60-package limit. The rest of the tree was never resolved.

36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)

Declared but not resolved

49 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.

package cap reached: 49

forwarded 0.2.0 — required by proxy-addr@2.0.7package cap reached
ipaddr.js 1.9.1 — required by proxy-addr@2.0.7package cap reached
bytes ^3.1.2 — required by body-parser@2.3.0package cap reached
raw-body ^3.0.2 — required by body-parser@2.3.0package cap reached
iconv-lite ^0.7.2 — required by body-parser@2.3.0package cap reached
http-errors ^2.0.1 — required by body-parser@2.3.0package cap reached
on-finished ^2.4.1 — required by body-parser@2.3.0package cap reached
content-type ^2.0.0 — required by body-parser@2.3.0package cap reached
depd ~2.0.0 — required by http-errors@2.0.1package cap reached
inherits ~2.0.4 — required by http-errors@2.0.1package cap reached
setprototypeof ~1.2.0 — required by http-errors@2.0.1package cap reached
statuses ~2.0.2 — required by http-errors@2.0.1package cap reached

+37 more not listed. The counts by reason above cover all of them.

Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.