photoshop-mcp@1.7.38
VERIFIED· not startedPublisher claims: "MCP server for Adobe Photoshop — 128 tools (generative AI + recipes), standalone web UI. Control Photoshop from Cursor, Claude, or natural language." Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Not started: dependency install failed; the server itself was not observed.- Tested
- the dependency install step · every file read, file written and host contacted by what ran
- Not tested
- server startup · the tool list · tool behavior
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
RYBBIT_API_KEYTYPESAFE_API_KEYConfiguration, not credentials: NO_UPDATE_NOTIFIER, PHOTOSHOP_MCP_HOME, PSMCP_INTENT_ROUTER, RYBBIT_HOST, RYBBIT_SITE_ID- Where it talks to
- no vendor host named in the codeAlso adobe.com, sideguard.io, stackexchange.com, indesignjs.de, ps-scripts.com — not the publisher's domain; check what for before connecting.
- What the honeypot saw
- no credential files read · no network
- What we could not test
- server startup · the tool list · tool behavior
Connect it with a scoped credential, under the guard, and read the third-party hosts first. The code names adobe.com, sideguard.io, stackexchange.com, indesignjs.de, ps-scripts.com as well as its own vendor. The guard injects RYBBIT_API_KEY, TYPESAFE_API_KEY only into requests to the host you bind (and its subdomains) and refuses the rest.
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; not started: dependency install failed; the server itself was not observed) on 2026-11-13 and scored it 82/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: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 15 s · 2 scenarios · 0 deviationsStatic findings
'Configuration is stored at ~/.photoshop-mcp/config.json (chmod 600).',Fix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.return ('Restart the MCP client (or reload this MCP server) so npx starts the new version. ' +Fix: Pin versions and sources; vendor anything fetched at install time.* Published tarballs omit src/. If a consumer npm/npx still runs `prepare`,Fix: Pin versions and sources; vendor anything fetched at install time.apiKeyHint: isCustom ? 'Enter your API key' : p.apiKeyHint,Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.'~/.photoshop-mcp/ui-session.json (chmod 600), sent as an',Fix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.Cost to the agent
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 @alisaitteke/photoshop-mcp@1.7.38 as of 37 h ago. This is the package itself, not its dependencies.