Verified conversions across 205 color spaces: CSS strings, gamut checks, .cube LUTs
Nothing to run from here
Harie is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
97/100
trust score
8
downloads a day
local
runs on your machine
444
downloads in 30d
What it does
Annotate screenshots for user guides. Saved as plain JPEG/PNG whose annotations stay editable.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user harie-mcp '--' npx -y @harie/mcp
# 2 — ask your agent for something these tools do
# harie_open, harie_create, harie_edit and 4 more
Harie costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
HOAll 1 server
hosshan1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Harie as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user harie-mcp '--' npx -y @harie/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it runs from its publisher’s own package: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
7 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Read from its source code. A server that builds its tool list when it starts can list more tools than this.
Harie ファイル（注釈を再編集できる JPEG/PNG）を開き、注釈の一覧と画像を返す。注釈の文言や位置は JSON で読めるので、画像が要らなければ image: false。普通の画像なら status: plain を返す
| Parameter | Type | Required | Notes |
|---|---|---|---|
| path | string | yes | ファイルのパス（… からの相対パスか絶対パス） |
| image | boolean | no | — |
普通の JPEG/PNG から注釈のない Harie ファイルを作る。元の画像はそのまま残し、既定では <名前>.harie.<拡張子> に保存する。以後の保存もこの形式になる
| Parameter | Type | Required | Notes |
|---|---|---|---|
| imagePath | string | yes | ファイルのパス（… からの相対パスか絶対パス） |
| outPath | string | no | 保存先。省略時は <名前>.harie.<拡張子> |
| format | string | no | — |
| title | string | no | 画像のタイトル（例: 通知設定の画面） |
注釈を追加・更新・削除し、画像を描き直して上書き保存する。保存後の画像を返す。先に harie_preview で確認するとよい
| Parameter | Type | Required | Notes |
|---|---|---|---|
| path | string | yes | ファイルのパス（… からの相対パスか絶対パス） |
| ops | array | yes | — |
| expectedRevision | integer | no | harie_open で得た revision。他で先に保存されていたら失敗させる |
| image | boolean | no | — |
ops を適用した結果の画像を返す。ファイルは変更しない
| Parameter | Type | Required | Notes |
|---|---|---|---|
| path | string | yes | ファイルのパス（… からの相対パスか絶対パス） |
| ops | array | yes | harie_edit の ops と同じ形式 |
画像内の個人情報（氏名・メール・電話番号など）を、ベース画像を書き換えて隠す。保存すると元に戻せず、ファイルのどこにも元の情報は残らない。 まず confirm を付けずに呼ぶと、保存せずに加工後の画像を返す。範囲と方法を確かめてから、同じ masks に confirm: true を付けて保存する。 method: replace（ダミー文字列に置き換える。replacement に同じ種類のダミー値を渡す。例: 山田 花子 / hanako@example.com）/ fill（塗りつぶし）/ mosaic / blur。文字は replace か fill を使う。 rect…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| path | string | yes | ファイルのパス（… からの相対パスか絶対パス） |
| masks | array | yes | 隠す範囲と方法 |
| confirm | boolean | no | true で保存する（元に戻せない）。省略時は保存せずに結果だけ返す |
| outPath | string | no | 別のファイルとして保存する場合の保存先。省略時は上書き |
| expectedRevision | integer | no | harie_open で得た revision。他で先に保存されていたら失敗させる |
Harie ファイルの注釈を残したまま、画像だけを新しいスクリーンショットに差し替えて保存する（画面が変わったときのガイドの更新）。大きさが違えば注釈を比率で拡大縮小する。位置がずれた注釈は保存後の画像を見て harie_edit で直す
| Parameter | Type | Required | Notes |
|---|---|---|---|
| path | string | yes | ファイルのパス（… からの相対パスか絶対パス） |
| imagePath | string | yes | 新しい画像（JPEG/PNG）のパス |
| outPath | string | no | 別のファイルとして保存する場合の保存先。省略時は上書き |
| expectedRevision | integer | no | harie_open で得た revision。他で先に保存されていたら失敗させる |
| image | boolean | no | — |
ディレクトリ内の Harie ファイルを、タイトル・リビジョン・注釈数とともに一覧する
| Parameter | Type | Required | Notes |
|---|---|---|---|
| dir | string | no | 探すディレクトリ。省略時は許可されたディレクトリ全体 |
| recursive | boolean | no | サブディレクトリも探すか（既定 true） |
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Harie or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATrust score 97 / 100
Release 0.5.0 · scanned 30 Oct 2026
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score97
Findings0 threat · 0 capability
Capabilitymoderate
Coveragesource
Verificationsource
Surface digesta162f92b0a8c8bba868c6b2bca5023e825a7a4e067e0b09b7aa7d9bcf2dba74a
Score vectorthreat 100 → client 97
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| verification-discount | source | publisher verification (provenance) — cryptographic build provenance ties the artifact to its source | −0 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tool surfaceread
Implementation sourceread
Package metadataread
Live transportnot available
Tools were statically extracted from the published source (7 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| harie_open | no tags | |
| harie_create | no tags | |
| harie_edit | state-write | state-write: declares destructiveHint: true |
| harie_preview | no tags | |
| harie_mask | state-write | state-write: declares destructiveHint: true |
| harie_replace_base | state-write | state-write: declares destructiveHint: true |
| harie_list | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digesta162f92b0a8c8bba
Scanned2026-10-30
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 0.5.0. Pin a release below and the command asks for exactly that one.
0.5.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Harie can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.