Ext Ops Panel
Open dashboard
Comparison

ai.pictomancer/image-processing vs Sprig Fit Images

ai.pictomancer/image-processing is an MCP server published by pictomancer.ai. Marketplaces we read that list it: 1 (Official MCP Registry). Sprig Fit Images is an MCP server published by BillyQin. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-27. 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
Marketplaceai.pictomancer/image-processingSprig Fit Images
Official MCP Registry Listed
Version: 0.4.0
No figure published
Not marked · First seen
Listed
Version: 0.1.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

ai.pictomancer/image-processing vs Sprig Fit Images
Factai.pictomancer/image-processingSprig Fit Images
Marketplaces that list it11
Last release (differs)Not published2026-10-21
Where it runs (differs)Remote server (api.pictomancer.ai/mcp)On your machine (sprig-fit-mcp)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
LicenceNot statedNot stated
Repository (differs)Not statedgithub.com/billyqin/uploadfit
Changes in the last 7 days (differs)03
First seen (differs)2026-10-112026-10-21
Endpoint at the last check (differs)Responded 5 days agono remote endpoint we check

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

ai.pictomancer/image-processing

In its own words, on Official MCP Registry:

Image processing for AI agents: resize, convert, compress, crop, and web-ready AI-generated images.

Sprig Fit Images

In its own words, on Official MCP Registry:

Inspect local photos and crop, resize or compress images to exact dimensions and file-size limits.

How to run each

ai.pictomancer/image-processing As a remote MCP server

Claude Code
claude mcp add --transport http image-processing https://api.pictomancer.ai/mcp

Sprig Fit Images As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio sprig-fit -- npx -y sprig-fit-mcp

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

Only ai.pictomancer/image-processing has a remote endpoint we check. How we check endpoints

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

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

What it can do: ai.pictomancer/image-processing · What it can do: Sprig Fit Images · Compare two other plugins

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