Ext Ops Panel
Open dashboard
Comparison

io.github.MediaShareORG/yourimageshare vs io.github.charmshots/mcp-server

io.github.MediaShareORG/yourimageshare is an MCP server published by MediaShareORG. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.charmshots/mcp-server is an MCP server published by charmshots. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-25. 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.MediaShareORG/yourimageshareio.github.charmshots/mcp-server
Official MCP Registry Listed
Version: 1.0.6
Downloads/month (npm): 340
Downloads/week (npm): 31
Forks (GitHub): 0
Stars (GitHub): 1
Not marked · First seen
Listed
Version: 1.2.1
Downloads/month (npm): 845
Downloads/week (npm): 26
Forks (GitHub): 0
Stars (GitHub): 0
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

io.github.MediaShareORG/yourimageshare vs io.github.charmshots/mcp-server
Factio.github.MediaShareORG/yourimageshareio.github.charmshots/mcp-server
Marketplaces that list it11
Stars (GitHub) (differs)1 (better)0 (worse)
Forks (GitHub)00
Last release (differs)2026-10-18Not published
Where it runs (differs)Remote server or your machineRemote server (mcp.charmshots.com/mcp)
Transport (differs)stdio, Streamable HTTPStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)1, secrets among them: 1Not published
LicenceNot statedNot stated
Repository (differs)github.com/mediashareorg/yourimagesharegithub.com/charmshots/mcp-server
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Answered with HTTP 403 (31 h ago)Responded 12 h ago, requires a key

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.MediaShareORG/yourimageshare

In its own words, on Official MCP Registry:

MCP server exposing the YourImageShare upload API (upload/list/delete) as tools for AI agents.

io.github.charmshots/mcp-server

In its own words, on Official MCP Registry:

Read-only MCP connector for Charmshots photoshoots, photo metadata and owner-authenticated links.

How to run each

io.github.MediaShareORG/yourimageshare As a local MCP server: npm package

Claude Code
claude mcp add --env "YIS_API_KEY=<YOUR_YIS_API_KEY>" --transport stdio yourimageshare -- npx -y yourimageshare-mcp

Requires: YIS_API_KEY (secret)

io.github.charmshots/mcp-server As a remote MCP server

Claude Code
claude mcp add --transport http io-github-charmshots-mcp-server https://mcp.charmshots.com/mcp

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

Only the endpoint of io.github.charmshots/mcp-server 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 io.github.charmshots/mcp-server publish no settings it asks for, so we do not compare settings.

What it can do: io.github.MediaShareORG/yourimageshare · What it can do: io.github.charmshots/mcp-server · 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