Ext Ops Panel
Open dashboard
Comparison

Schogini Image Border vs Craftery Developer Tools

Schogini Image Border is an MCP server published by schogini. Marketplaces we read that list it: 1 (Docker MCP Catalog). Craftery Developer Tools is an MCP server published by craftery.dev. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-21. 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

Where each is published
MarketplaceSchogini Image BorderCraftery Developer Tools
Docker MCP Catalog Listed
Version: sha256:aadb75058ed1
Forks (GitHub): 0
Pulls (Docker Hub): 36 109
Stars (Docker Hub): 0
Stars (GitHub): 0
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.2
No figure published
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

Schogini Image Border vs Craftery Developer Tools
FactSchogini Image BorderCraftery Developer Tools
Marketplaces that list it11
Stars (GitHub) (differs)0No figure on GitHub
Pulls (Docker Hub) (differs)36 109No figure on Docker Hub
Forks (GitHub) (differs)0No figure on GitHub
Last release (differs)Not published2026-10-17
Where it runs (differs)On your machine (mcp/schogini_mcp_image_border)Remote server (craftery.dev/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declares (differs)3Not published
Environment variables it asks forNot publishedNot published
LicenceNot statedNot stated
Repository (differs)github.com/schogini/schogini_mcp_image_borderNot stated
Changes in the last 7 days (differs)01
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 4 days ago

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

In its own words, on Docker MCP Catalog:

This adds a border to an image and returns base64 encoded image.

Craftery Developer Tools

In its own words, on Official MCP Registry:

Developer utilities: color conversion, WCAG contrast, timestamps, UUIDs, and hashing.

How to run each

Schogini Image Border As a local MCP server: Docker image

Claude Code
claude mcp add --transport stdio schogini-mcp-image-border -- docker run -i --rm mcp/schogini_mcp_image_border

Craftery Developer Tools As a remote MCP server

Claude Code
claude mcp add --transport http tools https://craftery.dev/mcp

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only Craftery Developer Tools has a remote endpoint we check. How we check endpoints

Tools each declares

Only Schogini Image Border has

  • add-two-numbers
  • image-border
  • image-meta

Only Craftery Developer Tools has

  • check_contrast
  • convert_color
  • convert_timestamp
  • generate_uuid
  • hash_text
  • swiftui_color

Both have

None

Tool names as the marketplaces declare them and as Ext Ops observed them on the endpoints (Craftery Developer Tools as of 2026-10-21). More tools is not better in itself: compare what each needs for the job.

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: Schogini Image Border · What it can do: Craftery Developer Tools · 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. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built