XF Model Source vs EvalForge Lite
XF Model Source is an MCP server published by xpansion.dev. Marketplaces we read that list it: 1 (Official MCP Registry). EvalForge Lite is an MCP server published by thejaredchapman. 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
| Marketplace |  XF Model Source |  EvalForge Lite |
|---|---|---|
| Official MCP Registry | Listed Version: 0.5.3 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 1.0.1 Downloads/month (PyPI): 244 Downloads/week (PyPI): 124 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
| Fact | XF Model Source | EvalForge Lite |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) | 0 | 0 |
| Forks (GitHub) | 0 | 0 |
| Last release (differs) | 2026-10-17 | Not published |
| Where it runs (differs) | Remote server (xfms.xpansion.dev/mcp) | On your machine (evalforge-lite) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 1, secrets among them: 1 |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/visionairyse/xfms | github.com/thejaredchapman/evalforge-lite |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 4 days ago | no 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
XF Model Source
Find the right AI model for your job. Free discovery and ranking; tests on your own key.
EvalForge Lite
Compare text LLMs across OpenRouter, Bedrock, Vertex AI and Foundry with automated grading.
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
EvalForge Lite As a local MCP server: PyPI package
claude mcp add --env "OPENROUTER_API_KEY=<YOUR_OPENROUTER_API_KEY>" --transport stdio evalforge-lite -- uvx evalforge-liteRequires: OPENROUTER_API_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only XF Model Source has a remote endpoint we 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 XF Model Source publish no settings it asks for, so we do not compare settings.
What it can do: XF Model Source · What it can do: EvalForge Lite · 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.