Image processing pipeline for Next.js.
Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.
darkroom_initCreates shutterbox.config.ts in a project directory. Scaffolds a starter config with thumbnail and hero image variants, breakpoints, and a .shutterbox-cache directory.Creates shutterbox.config.ts in a project directory. Scaffolds a starter config with thumbnail and hero image variants, breakpoints, and a .shutterbox-cache directory.
No input schema was published for this tool.
darkroom_optimizeProcesses images in a directory using shutterbox image pipeline. Scans the directory for image files and returns processing instructions or results.Processes images in a directory using shutterbox image pipeline. Scans the directory for image files and returns processing instructions or results.
No input schema was published for this tool.
2 of 2 tools published a description.
Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.
Image processing pipeline for Next.js.
Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.