Ext Ops Panel
Open dashboard
Comparison

AGTS MCP Server vs io.github.firebase/firebase-mcp

AGTS MCP Server is an MCP server published by mcp.obligationsign.com. 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-11-11. 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
MarketplaceAGTS MCP Serverio.github.firebase/firebase-mcp
Official MCP Registry Listed
Version: 1.0.2
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 0.3.0
Downloads/month (npm): 13 149 020
Downloads/week (npm): 4 514 786
Forks (GitHub): 1 282
Stars (GitHub): 4 489
Not marked · First seen
Claude Code: claude-plugins-official Not listed Listed
Version: not stated
Forks (GitHub): 4 870
Stars (GitHub): 46 862
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

AGTS MCP Server vs io.github.firebase/firebase-mcp
FactAGTS MCP Serverio.github.firebase/firebase-mcp
Marketplaces that list it (differs)1 (worse)3 (better)
Stars (GitHub) (differs)0 (worse)46 862 (better)
Forks (GitHub) (differs)0 (worse)4 870 (better)
Last releaseNot publishedNot published
Where it runs (differs)Remote server (mcp.obligationsign.com/mcp)On your machine (firebase-tools)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published1, secrets among them: 0
Parts of the bundle (differs)Not a bundle16
Licence (differs)Not statedMIT
Repository (differs)github.com/obligationsign/agts-mcpgithub.com/firebase/firebase-tools
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 12 h 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

AGTS MCP Server

In its own words, on Official MCP Registry:

Sovereign MCP Gateway — 64 governed tools with Merkle transparency log. EU AI Act ready.

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

AGTS MCP Server As a remote MCP server

Claude Code
claude mcp add --transport http agts-mcp https://mcp.obligationsign.com/mcp

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.

Only AGTS MCP Server 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

The marketplaces of AGTS MCP Server publish no settings it asks for, so we do not compare settings.

What it can do: AGTS MCP Server · 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