XF Model Source vs StudioMeyer GEO
XF Model Source is an MCP server published by xpansion.dev. Marketplaces we read that list it: 1 (Official MCP Registry). StudioMeyer GEO is an MCP server published by studiomeyer.io. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-05. 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
| Marketplace |  XF Model Source |  StudioMeyer GEO |
|---|---|---|
| Official MCP Registry | Listed Version: 0.5.3 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 2.12.0 No figure published 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
| Fact | XF Model Source | StudioMeyer GEO |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 0 | No figure on GitHub |
| Forks (GitHub) (differs) | 0 | No figure on GitHub |
| Last release (differs) | 2026-10-17 | Not published |
| Where it runs (differs) | Remote server (xfms.xpansion.dev/mcp) | Remote server (geo.studiomeyer.io/mcp) |
| Transport | Streamable HTTP | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/visionairyse/xfms | Not stated |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Status out of date: last check 5 days ago returned HTTP 406 | Status out of date: last check 30 h ago returned HTTP 401 |
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
XF Model Source
Find the right AI model for your job. Free discovery and ranking; tests on your own key.
StudioMeyer GEO
AI visibility across 8 LLM platforms. 30 tools, most need no API key. EU-hosted, free.
How to run each
XF Model Source As a remote MCP server
claude mcp add --transport http xfms https://xfms.xpansion.dev/mcp --header "X-OpenRouter-Key: <YOUR_X_OPENROUTER_KEY>"Requires: X-OpenRouter-Key header
StudioMeyer GEO As a remote MCP server
claude mcp add --transport http geo https://geo.studiomeyer.io/mcpCommands 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: XF Model Source · What it can do: StudioMeyer GEO · 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.