Ext Ops Panel
Open dashboard
Comparison

iris-eval vs swallow-insurance-rating-engine

iris-eval is a plugin bundle for AI coding tools published by Iris. Marketplaces we read that list it: 1 (Community GitHub marketplaces). swallow-insurance-rating-engine is a plugin bundle for AI coding tools published by llow-group. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). As of our marketplace pass on 2026-10-15. 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
Marketplaceiris-evalswallow-insurance-rating-engine
Community marketplace iris-eval/mcp-server Listed
Version: 0.20.0
Forks (GitHub): 4
Stars (GitHub): 9
Not marked · First seen
Not listed
Claude Code: claude-plugins-community Not listed Listed
Version: 1.0.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

iris-eval vs swallow-insurance-rating-engine
Factiris-evalswallow-insurance-rating-engine
Marketplaces that list it11
Stars (GitHub) (differs)9 (better)0 (worse)
Forks (GitHub) (differs)4 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (@iris-eval/mcp-server)Remote server (api.llow.io/ai/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)28
Licence (differs)Not statedMIT
Repository (differs)github.com/iris-eval/mcp-servergithub.com/llow-group/swallow-claude-plugin
Changes in the last 7 days (differs)20
First seen (differs)2026-10-132026-10-12
Endpoint at the last check (differs)no remote endpoint we checkResponded 2 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

iris-eval

In its own words, on Community GitHub marketplaces:

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.

swallow-insurance-rating-engine

In its own words, on Claude Code: claude-plugins-community:

Build, validate, analyse, and test insurance rating models with the Swallow Rating Engine via MCP

How to run each

iris-eval As a Claude Code plugin

Claude Code
/plugin marketplace add iris-eval/mcp-server
/plugin install iris-eval@iris-eval

swallow-insurance-rating-engine As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install swallow-insurance-rating-engine@claude-community

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

Only swallow-insurance-rating-engine 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: swallow-insurance-rating-engine · Compare two other plugins

Data comes from public marketplace files in GitHub repositories of their authors. 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