Ext Ops Panel
Open dashboard
Comparison

swallow-insurance-rating-engine vs io.github.Davmunrey/trazum

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). io.github.Davmunrey/trazum is an MCP server published by Davmunrey. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-23. 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-engineio.github.Davmunrey/trazum
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: 2.6.0
Downloads/month (npm): 1 870
Downloads/week (npm): 995
Forks (GitHub): 0
Stars (GitHub): 1
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 io.github.Davmunrey/trazum
Factswallow-insurance-rating-engineio.github.Davmunrey/trazum
Marketplaces that list it11
Stars (GitHub) (differs)0 (worse)1 (better)
Forks (GitHub)00
Last release (differs)Not published2026-10-13
Where it runs (differs)Remote server (api.llow.io/ai/mcp)On your machine (@trazum/mcp)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)8Not a bundle
LicenceMITMIT
Repository (differs)github.com/llow-group/swallow-claude-plugingithub.com/davmunrey/trazum
Changes in the last 7 days00
First seen (differs)2026-10-122026-10-11
Endpoint at the last check (differs)Responded 5 days agono 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

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

io.github.Davmunrey/trazum

In its own words, on Official MCP Registry:

Trazum as an MCP server: let an agent price and budget its own prompts before it sends them.

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

io.github.Davmunrey/trazum As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio trazum -- npx -y @trazum/mcp

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: swallow-insurance-rating-engine · What it can do: io.github.Davmunrey/trazum · 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. Data comes from public marketplace files in GitHub repositories of their authors. 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