Ext Ops Panel
Open dashboard
Comparison

Trentina vs io.github.firebase/firebase-mcp

Trentina is an MCP server published by crunchtools. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.firebase/firebase-mcp is an MCP server published by firebase. Marketplaces we read that list it: 3 (Official MCP Registry, Claude Code: claude-plugins-official, Community GitHub marketplaces). As of our marketplace pass on 2026-10-18. 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
MarketplaceTrentinaio.github.firebase/firebase-mcp
Official MCP Registry Listed
Version: 0.5.0
Downloads/month (PyPI): 5 689
Downloads/week (PyPI): 164
Forks (GitHub): 3
Stars (GitHub): 11
Not marked · First seen
Listed
Version: 0.3.0
Downloads/month (npm): 14 088 257
Downloads/week (npm): 3 454 538
Forks (GitHub): 1 267
Stars (GitHub): 4 475
Not marked · First seen
Claude Code: claude-plugins-official Not listed Listed
Version: not stated
Forks (GitHub): 4 462
Stars (GitHub): 41 694
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

Trentina vs io.github.firebase/firebase-mcp
FactTrentinaio.github.firebase/firebase-mcp
Marketplaces that list it (differs)1 (worse)3 (better)
Stars (GitHub) (differs)11 (worse)41 694 (better)
Forks (GitHub) (differs)3 (worse)4 462 (better)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp-trentina-crunchtools)On your machine (firebase-tools)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published1, secrets among them: 0
Parts of the bundle (differs)Not a bundle15
Licence (differs)Not statedMIT
Repository (differs)github.com/crunchtools/mcp-trentinagithub.com/firebase/firebase-tools
Changes in the last 7 days (differs)02
First seen2026-10-112026-10-11

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

Trentina

In its own words, on Official MCP Registry:

Secure MCP gateway and quarantine for AI agent traffic — three-layer prompt injection defense

io.github.firebase/firebase-mcp

In its own words, on Official MCP Registry:

Gives AI development tools Firebase-specific capabilities and expertise.

How to run each

Trentina As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio trentina -- uvx mcp-trentina-crunchtools

io.github.firebase/firebase-mcp As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio firebase-mcp -- npx -y mcp firebase-tools

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

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 Trentina publish no settings it asks for, so we do not compare settings.

What it can do: Trentina · What it can do: io.github.firebase/firebase-mcp · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-official/blob/HEAD/.claude-plugin/marketplace.json. 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