Ext Ops Panel
Open dashboard
Comparison

Image Generator API vs io.github.Cripacx/mediagen

Image Generator API is an MCP server published by Br0ski777. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.Cripacx/mediagen is an MCP server published by Cripacx. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-02. 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
MarketplaceImage Generator APIio.github.Cripacx/mediagen
Official MCP Registry Listed
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 0.3.0
Downloads/month (npm): 336
Downloads/week (npm): 31
Forks (GitHub): 0
Stars (GitHub): 51
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

Image Generator API vs io.github.Cripacx/mediagen
FactImage Generator APIio.github.Cripacx/mediagen
Marketplaces that list it11
Stars (GitHub) (differs)0 (worse)51 (better)
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)Remote server (image-generator-x402-production.up.railway.app/mcp)On your machine (mediagen)
Transport (differs)SSEstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
LicenceNot statedNot stated
Repository (differs)github.com/br0ski777/image-generator-x402github.com/cripacx/mediagen
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Answered with HTTP 404 (20 h ago)no 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

Image Generator API

In its own words, on Official MCP Registry:

AI image generation from text prompts via Gemini. x402 micropayment.

io.github.Cripacx/mediagen

In its own words, on Official MCP Registry:

Generate images and video from text prompts across Gemini, OpenAI and Kie AI.

How to run each

Image Generator API As a remote MCP server

Claude Code
claude mcp add --transport sse image-generator https://image-generator-x402-production.up.railway.app/mcp

io.github.Cripacx/mediagen As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio mediagen -- npx -y mediagen

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

Only Image Generator API 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: Image Generator API · What it can do: io.github.Cripacx/mediagen · 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