iris-eval vs XFMS — Model Source
iris-eval is a plugin bundle for AI coding tools published by Iris. Marketplaces we read that list it: 1 (Community GitHub marketplaces). XFMS — 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-14. 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 |  XFMS — Model Source | |
|---|---|---|
| Community marketplace iris-eval/mcp-server | Listed Version: 0.20.0 Forks (GitHub): 4 Stars (GitHub): 9 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.4.0 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 | iris-eval | XFMS — Model Source |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 9 (better) | 0 (worse) |
| Forks (GitHub) (differs) | 4 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (@iris-eval/mcp-server) | Remote server (xfms.vercel.app/mcp) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 2 | Not a bundle |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/iris-eval/mcp-server | github.com/visionairyse/xfms |
| Changes in the last 7 days (differs) | 2 | 0 |
| First seen (differs) | 2026-10-13 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Answered with HTTP 307 (40 h 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
iris-eval
Stop shipping agents on vibes — agent eval for any MCP workflow. Score output quality, catch PII and prompt injection, verify citations, and enforce cost budgets. 12 MCP tools + the iris-eval skill.
XFMS — Model Source
Pick the right LLM for any task. Ranked shortlist with rationale across 8 evaluators.
How to run each
iris-eval As a Claude Code plugin
/plugin marketplace add iris-eval/mcp-server
/plugin install iris-eval@iris-evalXFMS — Model Source As a remote MCP server
claude mcp add --transport http xfms https://xfms.vercel.app/mcp/ --header "Authorization: Bearer <YOUR_TOKEN>"Requires: Authorization header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only XFMS — 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
Neither one's marketplaces publish the settings it asks for.
What it can do: iris-eval · What it can do: XFMS — Model Source · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. 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.