MCP server

HackMD

mcp:yuna0x0/hackmd-mcp

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

awesome-mcp-servers Glama MCP Registry

Verdict

No issues found

No suspicious or malicious behavior was found.

Analyzed Oct 26, 2026, 13:08 UTC at 38f6a4b

findings

—

highest severity

threat classes

files scanned

387/387

checks satisfied

package advisories

Why this verdict

benign: 387 checks satisfied, no findings for mcp-server:.

Security findings 0

No security findings

No suspicious or malicious behavior was found; 1 candidate finding was refuted on review.

Refuted findings 1

Candidates the review stage examined and rejected, kept for transparency.

Credential access

criticalRefutedlow confidence

In HTTP mode the server defaults CORS origin to wildcard "*" while /mcp falls back to the operator's HACKMD_API_TOKEN env var when no header is supplied, so any web origin that can reach the server could use the operator's token via the MCP tools.

index.ts:27

origin: process.env.CORS_ORIGIN?.split(",") || "*",

Why it was refuted

The wildcard CORS default is an openly commented choice for browser-based MCP clients. The env token fallback is the wrapped HackMD service's own API key being used for that service, which is a carve-out. The remaining concern is a deployment hardening issue (operator exposure in HTTP mode), not concealed or undeclared credential misuse.