Is Prompt Optimizer Local safe and trustworthy?

tashan scores Prompt Optimizer Local on public evidence — tashan score 50.0/100, it is currently active, note: a single primary maintainer (bus-factor risk), no known advisories against the current release, it runs a script at install time. Audit scope: OSV advisories, install-time scripts, build provenance and declared permission surface. We do not review source code or execute the capability.

How do I install Prompt Optimizer Local?

In Claude Code: run `claude mcp add prompt-optimizer-local -- npx -y mcp-prompt-optimizer-local`. In Cursor / Claude Desktop, add it to mcp.json / claude_desktop_config.json.

Who maintains Prompt Optimizer Local?

source: mcp-prompt-optimizer/local-npm.

‹ The Index

Prompt Optimizer Local

npm

Advanced cross-platform prompt optimization with MCP integration and 120+ optimization rules

Works with: Claude Code, Cursor, Claude Desktop, Codex CLI, Gemini CLI, Cline, Windsurf, VS Code (installable)
installable: each client documents how to load an MCP server of this type — that is the client's promise, not a claim verified against this capability

Category: Cloud & Infra — see all ranked ›

Work: Prompt engineering

Who it is for: AI engineer

Install (Claude Code):

claude mcp add prompt-optimizer-local -- npx -y mcp-prompt-optimizer-local

tashan score: 50.0
Adoption: 34/wk
Upkeep: 68.0
Freshness: 95.0
Evidence coverage: 100% of the inputs this score can use
Health: active
License: Proprietary

Security audit

Every finding is shown in full — which advisory, the version that fixes it, and the exact command run at install time. Nothing in this audit is behind a licence.

No known advisoriesclearchecked against OSV for 4.1.8

Runs a script at install timecodenode secure-postinstall.js

No access inferred from declared dependenciesnothing it depends on reaches files, shell or network. This reads declarations only — built-in APIs are invisible to it, so absence of a declaration is not absence of access

No build provenanceno attestation — the published artifact cannot be traced to its source

What changed recently

2026-08-11 mcp-prompt-optimizer-local now runs a script when it installs Install-time code executes on your machine before you have used the tool once, and it did not do this before.

You are reading this because you came looking. tashan Pro gives tashan doctor the history behind it, so a run over your own config says which of YOURS moved.

You searched for one. Check the rest of your stack:

npx tashan-cli doctor

Reads the config already on your machine and names what is dead, deprecated or running code at install time. No account, nothing uploaded.

tashan Pro$6/mo

We recorded 1 change to Prompt Optimizer Local in the last 45 days. Pro tells you on the day — for the servers in your own config, not the ones you thought to look up.

Every score since we started measuring, for any capability
The named replacement when something you run is dying — not just that it is
tashan doctor over the config you already have, on your machine

Start a 7-day trial › Everything measured on this page stays free.

Show your score

Measured this well? Put the live badge in your README — it updates as the score does.

[![tashan](https://tashan.sh/badge/pkg-mcp-prompt-optimizer-local.svg)](https://tashan.sh/capability/pkg-mcp-prompt-optimizer-local.html)

npm ↗ · source ↗ · pkg:mcp-prompt-optimizer-local

Already running this? npx tashan-cli doctor checks your whole config against the Index — how it works ›

Measured 2026-08-14 · scorer s5 · how · something wrong here?