Ext Ops Panel
Open dashboard
Comparison

Spritefetch vs io.github.mtbun/storeshots-mcp

Spritefetch is an MCP server published by spritefetch.dev. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.mtbun/storeshots-mcp is an MCP server published by mtbun. Marketplaces we read that list it: 3 (Official MCP Registry, npm registry (MCP servers), Community GitHub marketplaces). As of our marketplace pass on 2026-10-24. 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
MarketplaceSpritefetchio.github.mtbun/storeshots-mcp
Official MCP Registry Listed
Version: 0.1.0
No figure published
Not marked · First seen
Listed
Version: 0.4.0
Downloads/month (npm): 2 613
Downloads/week (npm): 376
Forks (GitHub): 0
Stars (GitHub): 27
Not marked · First seen
npm registry (MCP servers) Not listed Listed
Version: 0.5.0
Downloads/month (npm): 2 613
Downloads/week (npm): 376
Forks (GitHub): 0
Stars (GitHub): 27
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

Spritefetch vs io.github.mtbun/storeshots-mcp
FactSpritefetchio.github.mtbun/storeshots-mcp
Marketplaces that list it (differs)1 (worse)3 (better)
Stars (GitHub) (differs)No figure on GitHub27
Forks (GitHub) (differs)No figure on GitHub0
Last releaseNot publishedNot published
Where it runs (differs)Remote server (api.spritefetch.dev/mcp)On your machine (storeshots-mcp)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)Not a bundle1
Licence (differs)Not statedMIT
Repository (differs)Not statedgithub.com/mtbun/storeshots-mcp
Changes in the last 7 days (differs)20
First seen (differs)2026-10-232026-10-11
Endpoint at the last check (differs)not checked yetno 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

Spritefetch

In its own words, on Official MCP Registry:

Search and download free CC0 2D sprite sheets and tilesets for games.

io.github.mtbun/storeshots-mcp

In its own words, on Official MCP Registry:

Render store-ready App Store and Google Play screenshots: device frames, headlines, exact sizes.

How to run each

Spritefetch As a remote MCP server

Claude Code
claude mcp add --transport http spritefetch https://api.spritefetch.dev/mcp

io.github.mtbun/storeshots-mcp As a local MCP server: npm package

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

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

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: Spritefetch · What it can do: io.github.mtbun/storeshots-mcp · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). Data comes from public marketplace files in GitHub repositories of their authors. 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