imgx-mcp
An MCP server for AI image generation and editing, allowing users to generate images from text, edit existing images with instructions, and manage iterative editing sessions with undo/redo.
Caution. Specific findings reduced this grade. They are listed on the page. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.
How we verified
Verified is a snapshot. Live keeps it current, and builds your track record.
⚡ Connect GitHub → continuous verification on every pushwhy connect →Who stands behind it
somacoffeekyoto
Source: Glama
Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →
Install from
The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.
These names and descriptions are the publisher's own, read from the source code. We print them as written. Our assessment is the findings above, not this list.
generate_imageGenerate an image from a text prompt
edit_imageEdit an existing image with text instructions
edit_lastEdit the last generated/edited image with new text instructions. Uses the output of the previous generate_image or edit_image call as input.
undo_editUndo the last edit, reverting to the previous image state
redo_editRedo a previously undone edit
edit_historyShow the full edit history with all sessions
switch_sessionSwitch to a different editing session to continue work on a previous image chain
clear_historyClear edit history for the current project. Files saved to custom output paths are never deleted — only files in managed directories (.imgx/ or ~/Pictures/imgx/).
set_output_dirChange the default output directory for generated images
list_providersList available image providers and their capabilities
Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.
When Vitest UI server is listening, arbitrary file can be read and executed
GEMINI_API_KEY"env": { "": "your-key" }IMGX_MODEL2. Environment variables (, IMGX_OUTPUT_DIR, etc.)IMGX_OUTPUT_DIR2. Environment variables (IMGX_MODEL, , etc.)IMGX_PROJECT_ROOTSet to your project path to save images inside the project (e.g. "C:\\Users\\you\\my-project"). Leave empty to use the global default (~/Pictures/imgx).IMGX_PROVIDERIMGX_TEST_CONFIG_DIROPENAI_API_KEYexport ="your-api-key"XDG_CONFIG_HOMETool annotations
No tools have read-only/destructive annotations
Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.
All four hints declared on every tool
10/10 tools missing one or more hints — generate_image (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); edit_image (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); edit_last (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +7 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.
For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.
Destructive tools are labelled
2 tools perform destructive updates without destructiveHint — clear_history deletes at line 356 (rmSync(fp)); set_output_dir deletes at line 395 (rmSync(oldDir, { recursive: true, force: true }))
Add destructiveHint:true to any tool whose handler calls .delete(), .upsert(), .update(), unlink, rm, DELETE, DROP, REPLACE INTO, or any operation that overwrites existing data.
Tool inputs are validated
6/10 tool handlers declare input schemas (60%)
Declare an inputSchema with zod/joi/yup on every tool definition.
Tool handlers catch errors
8/10 tool handlers wrap calls in try/catch (80%)
Wrap each tool handler body in try/catch and return a structured error response.
Tool test coverage
Only 0/10 tools referenced in tests (0%)
Write tests that reference each tool by name so every tool has at least one test.
Dev dependencies
1 critical/high in dev-only deps (does not ship to users)
Upgrade dev dependencies when convenient.
Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.
[](https://m8ven.ai/mcp/somacoffeekyoto/imgx-mcp)?variant=verified from the URL.Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.
https://m8ven.ai/api/mcp/tool-check