MCP server for terminal commands, file operations, and process management
Nothing to run from here
Drawing Anonymizer 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.
96/100
trust score
12
downloads a day
local
runs on your machine
141
downloads in 30d
What it does
Anonymize drawing PDFs: mask names, logos, addresses, emails; flattened PDF or expiring link.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user drawing-anonymizer-mcp '--' npx -y drawing-anonymizer-mcp
# 2 — ask your agent for something these tools do
# analyze_drawing, load_analysis, review_masking and 1 more
Drawing Anonymizer costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
IMAll 2 servers
imnoo2 servers
2 categories
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 Drawing Anonymizer 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 drawing-anonymizer-mcp '--' npx -y drawing-anonymizer-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 asks of you
Nothing is required, but it can take DRAWING_ANONYMIZER_URL (Optional. Base URL of the Imnoo web app that runs the drawing analysis and share links; only change it to target another deployment.) if you want to set it.
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
4 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.
Upload a technical-drawing PDF to Imnoo's drawing analysis and return the sensitive data it finds — company names, logos, person names, addresses, phone numbers, emails, websites, article numbers, drawing numbers, dates and other identifying text — each with a detection id, category, value, PDF…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| pdf_path | string | no | path to the drawing PDF (vector or scanned, ≤ 30 MB) |
| drawing_id | string | no | instead of pdf_path: the drawing_id of an earlier upload that returned status "processing" — keeps waiting for it without a new upload |
| save_analysis_to | string | no | write the analysis JSON to this path (re-open it later with load_analysis, no upload needed) |
| timeout_seconds | integer | no | how long to wait for the analysis before returning "processing" (default 180) |
Open a drawing analysis JSON saved earlier (analyze_drawing with save_analysis_to, or the Imnoo FileStore analysis document) and register it as a drawing for review_masking and mask_drawing. Fully offline — no upload, no daily credit. Pass pdf_path as well: masking needs the original PDF, and…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| analysis_path | string | yes | path to the analysis JSON |
| pdf_path | string | no | path to the matching drawing PDF (needed to write the masked PDF) |
| drawing_id | string | no | id to register the drawing under (default: the analysis id, else the file name) |
Compose the masks for an analysed drawing exactly as mask_drawing will, without writing anything: which detections are masked (with their replacement in mode "replace") and which stay visible, custom-term matches, rectangles, the article-number stamp, the pages written, the anonymity score (0–100)…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| drawing_id | string | yes | from analyze_drawing or load_analysis |
| masking | object | no | Masking settings — shared by review_masking and mask_drawing; pass the same object to both so the PDF matches the reviewed masks. Everything is optional; the defaults reproduce the web app. |
Mask the drawing and write the anonymized PDF: blank (or replacement-text / own-logo) boxes over every masked detection, custom term and rectangle; by default every page is then rasterized at 288 dpi so the covered content is destroyed rather than painted over (tamper-proof single-layer PDF) and…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| drawing_id | string | no | from analyze_drawing or load_analysis |
| pdf_path | string | no | the drawing PDF — analysed first when it is not known yet (one daily credit), or the original PDF for a drawing_id loaded without one |
| masking | object | no | Masking settings — shared by review_masking and mask_drawing; pass the same object to both so the PDF matches the reviewed masks. Everything is optional; the defaults reproduce the web app. |
| output_path | string | no | target .pdf path, or a directory (default: next to the drawing PDF, else the working directory) |
| overwrite | boolean | no | allow replacing an existing output file |
| share_link | string | no | also create an expiring public link to the masked copy, valid for 1 minute, 15 minutes, 1 hour or 24 hours |
| timeout_seconds | integer | no | with pdf_path: how long to wait for the analysis (default 180) |
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 Drawing Anonymizer 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 96 / 100
Release 0.1.0 · scanned 20 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 score96
Findings0 threat · 0 capability
Capabilitymoderate
Coveragesource
Verificationrepo
Surface digestfb8e4ef8ae91ab5631c604b92f8b5dbf79240f21cbc49243f5488072634bca2d
Score vectorthreat 100 → client 96
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| verification-discount | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| 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 (4 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 |
|---|---|---|
| analyze_drawing | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true, handler sends an HTTP POST (fetch(${appUrl()}/api/public/drawings) at dist/index.js:1096 |
| load_analysis | no tags | |
| review_masking | no tags | |
| mask_drawing | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true, handler sends an HTTP POST (fetch(${appUrl()}/api/public/drawings) at dist/index.js:1096, handler sends an HTTP POST (fetch(${appUrl()}/api/share) at dist/index.js:1587 |
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 digestfb8e4ef8ae91ab56
Scanned2026-10-20
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.1.0. Pin a release below and the command asks for exactly that one.
0.1.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 Drawing Anonymizer 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.