Ext Ops Panel
Open dashboard
Comparison

swallow-insurance-rating-engine vs QuantRisk

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). QuantRisk is an MCP server published by quantrisk.dev. Marketplaces we read that list it: 1 (Official MCP Registry). 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
Marketplaceswallow-insurance-rating-engineQuantRisk
Claude Code: claude-plugins-community Listed
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.2
Downloads/month (npm): 290
Downloads/week (npm): 95
Forks (GitHub): 1
Stars (GitHub): 2
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

swallow-insurance-rating-engine vs QuantRisk
Factswallow-insurance-rating-engineQuantRisk
Marketplaces that list it11
Stars (GitHub) (differs)0 (worse)2 (better)
Forks (GitHub) (differs)0 (worse)1 (better)
Last releaseNot publishedNot published
Where it runs (differs)Remote server (api.llow.io/ai/mcp)Remote server or your machine
Transport (differs)Streamable HTTPStreamable HTTP, stdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published1, secrets among them: 1
Parts of the bundle (differs)8Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/llow-group/swallow-claude-plugingithub.com/78degrees/mcp-server
Changes in the last 7 days00
First seen (differs)2026-10-122026-10-11
Endpoint at the last check (differs)Responded 44 h agoResponded 29 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

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

QuantRisk

In its own words, on Official MCP Registry:

Portfolio risk analytics — VaR, Monte Carlo, optimization, options Greeks, stress testing.

How to run each

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

QuantRisk As a remote MCP server

Claude Code
claude mcp add --transport http quantrisk https://quantrisk-mcp.quantrisk.workers.dev/mcp

Requires: QUANTRISK_API_KEY (secret)

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

The marketplaces of swallow-insurance-rating-engine publish no settings it asks for, so we do not compare settings.

What it can do: swallow-insurance-rating-engine · What it can do: QuantRisk · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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.

Where the data comes from: how the catalog is built