Photoshop (alisaitteke) MCP Server

@alisaitteke/photoshop-mcp npm v1.3.13

Published by @alisaitteke — no publish provenance and no vendor-owned scope, so the publisher could not be verified. The repository link below is self-declared.

Trust grade
A
100/100
Last scanned
Trust
A · 100/100
How safe the published surface and source look. Deterministic; every point is auditable.
Capability
High
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
A Why this grade

Started at 100 and nothing was deducted: the deterministic scan raised no scored threat in the published surface it inspected. Capability observations and advisory notes are recorded but never lower the score.

Findings 11

high Dynamic code execution in server code (dist/utils/extendscript-result.js)MTC-SRC-001

In the server's implementation (`dist/utils/extendscript-result.js:22`): Evaluating strings as code is the most direct RCE primitive; if any tool input reaches it, the server executes attacker-chosen code. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: new Function(

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server dist/utils/extendscript-result.js

high Shell/command execution in server code (dist/platform/macos-detector.js)MTC-SRC-002

In the server's implementation (`dist/platform/macos-detector.js:1`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: child_process

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server dist/platform/macos-detector.js

high Shell/command execution in server code (dist/platform/macos-executor.js)MTC-SRC-002

In the server's implementation (`dist/platform/macos-executor.js:1`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: child_process

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server dist/platform/macos-executor.js

high Shell/command execution in server code (dist/platform/windows-detector.js)MTC-SRC-002

In the server's implementation (`dist/platform/windows-detector.js:1`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: child_process

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server dist/platform/windows-detector.js

high Shell/command execution in server code (dist/platform/windows-executor.js)MTC-SRC-002

In the server's implementation (`dist/platform/windows-executor.js:1`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: child_process

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server dist/platform/windows-executor.js

high Shell/command execution in server code (dist/ui/agent/gemini-account.js)MTC-SRC-002

In the server's implementation (`dist/ui/agent/gemini-account.js:4`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: child_process

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server dist/ui/agent/gemini-account.js

high Shell/command execution in server code (dist/ui/providers/cli-utils.js)MTC-SRC-002

In the server's implementation (`dist/ui/providers/cli-utils.js:2`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: child_process

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server dist/ui/providers/cli-utils.js

medium Hardcoded egress to an external endpoint (dist/ui/providers/anthropic.js)MTC-SRC-003

In the server's implementation (`dist/ui/providers/anthropic.js:49`): A hardcoded outbound call to a fixed external host inside server code is a classic exfiltration/telemetry channel — especially paired with reads of local data. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: fetch('https://api.anthropic.com/v1/models?limit=1'

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server dist/ui/providers/anthropic.js

medium Hardcoded egress to an external endpoint (dist/ui/providers/google.js)MTC-SRC-003

In the server's implementation (`dist/ui/providers/google.js:50`): A hardcoded outbound call to a fixed external host inside server code is a classic exfiltration/telemetry channel — especially paired with reads of local data. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: fetch(`https://generativelanguage.googleapis.com/v1beta/models?key=${encodeURIComponent(key)}&pageSize=1`

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server dist/ui/providers/google.js

medium Hardcoded egress to an external endpoint (dist/ui/providers/openai.js)MTC-SRC-003

In the server's implementation (`dist/ui/providers/openai.js:46`): A hardcoded outbound call to a fixed external host inside server code is a classic exfiltration/telemetry channel — especially paired with reads of local data. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: fetch('https://api.openai.com/v1/models'

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server dist/ui/providers/openai.js

medium Hardcoded egress to an external endpoint (dist/ui/providers/openrouter.js)MTC-SRC-003

In the server's implementation (`dist/ui/providers/openrouter.js:57`): A hardcoded outbound call to a fixed external host inside server code is a classic exfiltration/telemetry channel — especially paired with reads of local data. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: fetch('https://openrouter.ai/api/v1/auth/key'

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server dist/ui/providers/openrouter.js

What this scan could not see

Versions

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v1.3.13 latest A 100/100 11 1.5.0 2026-07-22

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 100/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/alisaitteke-photoshop-mcp/badge.svg)](https://mcptrustchecker.com/registry/alisaitteke-photoshop-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/alisaitteke-photoshop-mcp"><img src="https://mcptrustchecker.com/registry/alisaitteke-photoshop-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/alisaitteke-photoshop-mcp/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan @alisaitteke/photoshop-mcp --online

Use the free API → How scoring works

Other implementations of Photoshop 1

Independent packages implementing the same tool, scanned with the same engine. Compare all 2 side by side →

More in Developer Tools