Schogini Image Border vs io.github.shinpr/mcp-image
Schogini Image Border is an MCP server published by schogini. Marketplaces we read that list it: 1 (Docker MCP Catalog). io.github.shinpr/mcp-image is an MCP server published by shinpr. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-10-26. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |   Schogini Image Border |  io.github.shinpr/mcp-image |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:aadb75058ed1 Forks (GitHub): 0 Pulls (Docker Hub): 36 407 Stars (Docker Hub): 0 Stars (GitHub): 0 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.18.2 Downloads/month (npm): 14 591 Downloads/week (npm): 932 Forks (GitHub): 41 Stars (GitHub): 183 Not marked · First seen |
| npm registry (MCP servers) | Not listed | Listed Version: 0.18.2 Downloads/month (npm): 14 591 Downloads/week (npm): 932 Forks (GitHub): 41 Stars (GitHub): 183 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | Schogini Image Border | io.github.shinpr/mcp-image |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 0 (worse) | 183 (better) |
| Pulls (Docker Hub) (differs) | 36 407 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 0 (worse) | 41 (better) |
| Last release (differs) | Not published | 2026-10-22 |
| Where it runs (differs) | On your machine (mcp/schogini_mcp_image_border) | On your machine (mcp-image) |
| Transport | stdio | stdio |
| Tools it declares (differs) | 3 | Not published |
| Environment variables it asks for (differs) | Not published | 7, secrets among them: 3 |
| Licence (differs) | Not stated | MIT |
| Repository (differs) | github.com/schogini/schogini_mcp_image_border | github.com/shinpr/mcp-image |
| Changes in the last 7 days (differs) | 0 | 3 |
| First seen | 2026-10-11 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
Schogini Image Border
This adds a border to an image and returns base64 encoded image.
io.github.shinpr/mcp-image
AI image generation and editing with prompt optimization and quality presets
How to run each
Schogini Image Border As a local MCP server: Docker image
claude mcp add --transport stdio schogini-mcp-image-border -- docker run -i --rm mcp/schogini_mcp_image_borderio.github.shinpr/mcp-image As a local MCP server: npm package
claude mcp add --env "ARK_API_KEY=<YOUR_ARK_API_KEY>" --env "GEMINI_API_KEY=<YOUR_GEMINI_API_KEY>" --env "OPENAI_API_KEY=<YOUR_OPENAI_API_KEY>" --transport stdio mcp-image -- npx -y mcp-imageRequires: ARK_API_KEY (secret), GEMINI_API_KEY (secret), OPENAI_API_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of io.github.shinpr/mcp-image publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of Schogini Image Border publish no settings it asks for, so we do not compare settings.
What it can do: Schogini Image Border · What it can do: io.github.shinpr/mcp-image · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.