Ext Ops Panel
Open dashboard
Comparison

io.github.AceDataCloud/mcp-openai vs Tancky AI Image Combiner

io.github.AceDataCloud/mcp-openai is an MCP server published by AceDataCloud. Marketplaces we read that list it: 2 (Official MCP Registry, PyPI (MCP servers)). Tancky AI Image Combiner is an MCP server published by tancky777. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-11. 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
Marketplaceio.github.AceDataCloud/mcp-openaiTancky AI Image Combiner
Official MCP Registry Listed
Version: 2026.11.6.2
Downloads/month (PyPI): 388
Downloads/week (PyPI): 1 368
Forks (GitHub): 0
Stars (GitHub): 1
Not marked · First seen
Listed
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
PyPI (MCP servers) Listed
Version: 2026.11.6.2
Downloads/month (PyPI): 388
Downloads/week (PyPI): 1 368
Forks (GitHub): 0
Stars (GitHub): 1
Not marked · First seen
Not listed

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

io.github.AceDataCloud/mcp-openai vs Tancky AI Image Combiner
Factio.github.AceDataCloud/mcp-openaiTancky AI Image Combiner
Marketplaces that list it (differs)2 (better)1 (worse)
Stars (GitHub) (differs)1 (better)0 (worse)
Forks (GitHub)00
Last release (differs)2026-11-07Not published
Where it runs (differs)Remote server or your machineRemote server (tancky-mcp.tancky777-482.workers.dev/mcp)
Transport (differs)Streamable HTTP, stdioStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)1, secrets among them: 1Not published
Licence (differs)MITNot stated
Repository (differs)github.com/acedatacloud/openaimcpgithub.com/tancky777/ai-image-combiner
Changes in the last 7 days (differs)140
First seen (differs)2026-10-112026-10-13
Endpoint at the last check (differs)Responded 27 h ago, requires authenticationResponded 1 h 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

io.github.AceDataCloud/mcp-openai

In its own words, on Official MCP Registry:

MCP server for OpenAI API (chat completions, image generation, embeddings) via AceDataCloud

Tancky AI Image Combiner

In its own words, on Official MCP Registry:

AI photo tools from Tancky AI: image combiner, couple, family and wedding photos, background remover

How to run each

io.github.AceDataCloud/mcp-openai As a remote MCP server

Claude Code
claude mcp add --transport http mcp-openai https://openai.mcp.acedata.cloud/mcp

Requires: ACEDATACLOUD_API_TOKEN (secret)

Tancky AI Image Combiner As a remote MCP server

Claude Code
claude mcp add --transport http ai-image-combiner https://tancky-mcp.tancky777-482.workers.dev/mcp

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

Both endpoints responded at the last daily 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

The marketplaces of Tancky AI Image Combiner publish no settings it asks for, so we do not compare settings.

What it can do: io.github.AceDataCloud/mcp-openai · What it can do: Tancky AI Image Combiner · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the Python Package Index (pypi.org). 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