Skills/npm/haru-cms-mcp

haru-cms-mcp@1.0.1

VERIFIED· startup only

Publisher claims: "日本語ヘッドレスCMS。記事の作成・更新・予約公開・画像取り込みをAIから実行できる。APIキーで接続、npm不要。Astro/Next.js等へ配信APIで届く。" Observed in sandbox: calls app.harucms.com only, touches nothing outside the project, writes no memory.

Registry npm (MCP server) · listed in the official MCP RegistryPublisher harucms · publishing for 92 daysInstalls 0Last detonated 5d ago
$claude mcp add haru-cms-mcp -- npx -y haru-cms-mcp
WatchReport an issue

Coverage

Startup only; authenticated tool behavior not tested.
Tested
server startup over stdio (initialize sent) · every file read, file written and host contacted by what ran
Not tested
the tool list (the server exited before answering) · what the tools do when called with real credentials

What this means for the label: Verified here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.

Before you give it your token

It will ask for
API_KEYHARU_CMS_API_KEYConfiguration, not credentials: HARU_CMS_ENDPOINT
Where it talks to
harucms.com, webharu.com (its own)
What the honeypot saw
no credential files read · reached only app.harucms.com (its own)
What we could not test
the tool list (the server exited before answering) · what the tools do when called with real credentials

Connect it with a scoped credential, under the guard. It asks for API_KEY, HARU_CMS_API_KEY and talks to harucms.com, webharu.com. Give the credential to the guard, not the server: the value never enters the server's environment and only travels to the host you bind. What the tools do with a real credential was not observed.

$vet-skills run --secrets API_KEY=harucms.com,HARU_CMS_API_KEY=harucms.com -- npx -y haru-cms-mcp

Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.

Is [email protected] safe to install?

KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; startup only; authenticated tool behavior not tested) on 2026-11-09 and scored it 92/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: calls app.harucms.com only, touches nothing outside the project, writes no memory.

Behavior trace

Honeypot run · 20 s · 2 scenarios · 0 deviations
t+CategoryObserved action
0.0sprocessno install scripts in bundle
20snetworkCONNECT tcp://app.harucms.com:443
20snetworkCONNECT tcp://app.harucms.com:443
20snetworkCONNECT tcp://app.harucms.com:443
20snetworkCONNECT tcp://app.harucms.com:443
20sclaimedstartup only: exited (0) before answering · tools/list error: APIキーが必要です。環境変数 HARU_CMS_API_KEY に hcms_ で始まるキーを設定してください。発行手順: https://www.webharu.com/cms/start (無料プランで発行できます・クレジットカード不要)
20sprocessscript backend runs setup only
20sprocessno install scripts to re-run

Static findings

MEDIUM
npx invocation of non-well-known packageindex.mjs:25 · npx invocation of non-well-known package — may execute untrusted code* HARU_CMS_API_KEY=hcms_... npx haru-cms-mcpFix: Pin versions and sources; vendor anything fetched at install time.
AST06

No other findings across 257 lines in 4 files.

Cost to the agent

Instructions loaded
≈56 tok
1 file · 4 in bundle
Tool list per prompt
≈0 tok
0 tools · 0 per tool
Handshake
396 ms
launch to tools/list, stdio
Undocumented tools
0
description under 20 chars · avg 0

Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.

Known vulnerabilities

No advisories in OSV for haru-cms-mcp@1.0.1 as of 5d ago. This is the package itself, not its dependencies.