Ext Ops Panel
Open dashboard
Comparison

mumo vs XF Model Source

mumo is an MCP server published by mumo.chat. Marketplaces we read that list it: 2 (Official MCP Registry, Claude Code: claude-plugins-community). XF Model Source is an MCP server published by xpansion.dev. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-28. 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
MarketplacemumoXF Model Source
Official MCP Registry Listed
Version: 1.1.0
Forks (GitHub): 1
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 0.5.3
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Claude Code: claude-plugins-community Listed
Version: 0.2.2
Forks (GitHub): 1
Stars (GitHub): 0
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

mumo vs XF Model Source
FactmumoXF Model Source
Marketplaces that list it (differs)2 (better)1 (worse)
Stars (GitHub)00
Forks (GitHub) (differs)1 (better)0 (worse)
Last release (differs)Not published2026-10-17
Where it runs (differs)Remote server (mumo.chat/api/mcp)Remote server (xfms.xpansion.dev/mcp)
TransportStreamable HTTPStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)2Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/mumo-chat/mumo-mcpgithub.com/visionairyse/xfms
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 8 h agoResponded 5 days 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

mumo

In its own words, on Official MCP Registry:

Multi-model deliberation over MCP: full responses plus typed cross-model reactions from other labs.

XF Model Source

In its own words, on Official MCP Registry:

Find the right AI model for your job. Free discovery and ranking; tests on your own key.

How to run each

mumo As a remote MCP server

Claude Code
claude mcp add --transport http mumo https://mumo.chat/api/mcp --header "Authorization: Bearer <YOUR_MUMO_API_KEY>"

Requires: Authorization header

XF Model Source As a remote MCP server

Claude Code
claude mcp add --transport http xfms https://xfms.xpansion.dev/mcp --header "X-OpenRouter-Key: <YOUR_X_OPENROUTER_KEY>"

Requires: X-OpenRouter-Key header

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

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

What it can do: mumo · What it can do: XF Model Source · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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