Ext Ops Panel
Open dashboard
Comparison

Neon vs Firebase push-id time prefix, value discarded

Neon is an MCP server published by neondatabase. Marketplaces we read that list it: 1 (Docker MCP Catalog). Firebase push-id time prefix, value discarded is an MCP server published by sadri-dridi. Marketplaces we read that list it: 1 (Official MCP Registry). 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
MarketplaceNeonFirebase push-id time prefix, value discarded
Docker MCP Catalog Listed
Version: sha256:fab32eb73fb0
Forks (GitHub): 131
Pulls (Docker Hub): 23 418
Stars (Docker Hub): 3
Stars (GitHub): 652
Not marked · First seen
Not listed
Official MCP Registry 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

Neon vs Firebase push-id time prefix, value discarded
FactNeonFirebase push-id time prefix, value discarded
Marketplaces that list it11
Stars (GitHub) (differs)652 (better)0 (worse)
Pulls (Docker Hub) (differs)23 418No figure on Docker Hub
Forks (GitHub) (differs)131 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/neon)Remote server (agent-observatory-sensor.nolimit-observatory.workers.dev/s/pushid-ts/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declares (differs)19Not published
Environment variables it asks for (differs)1, secrets among them: 1Not published
Licence (differs)MITNot stated
Repository (differs)github.com/neondatabase-labs/mcp-server-neongithub.com/sadri-dridi/named-mcp-utilities
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 4 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

Neon

In its own words, on Docker MCP Catalog:

MCP server for interacting with Neon Management API and databases.

Firebase push-id time prefix, value discarded

In its own words, on Official MCP Registry:

Firebase push-id time prefix, value discarded

How to run each

Neon As a local MCP server: Docker image

Claude Code
claude mcp add --env "NEON_API_KEY=<YOUR_NEON_API_KEY>" --transport stdio neon -- docker run -i --rm -e NEON_API_KEY mcp/neon

Requires: NEON_API_KEY (secret)

Firebase push-id time prefix, value discarded As a remote MCP server

Claude Code
claude mcp add --transport http pushid-ts https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/pushid-ts/mcp

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

Only Firebase push-id time prefix, value discarded has a remote endpoint we check. How we check endpoints

Tools each declares

The marketplaces of Firebase push-id time prefix, value discarded publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of Firebase push-id time prefix, value discarded publish no settings it asks for, so we do not compare settings.

What it can do: Neon · What it can do: Firebase push-id time prefix, value discarded · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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