Ext Ops Panel
Open dashboard
Comparison

Suzieq vs Centipid ISP Billing

Suzieq is an MCP server published by PovedaAqui. Marketplaces we read that list it: 1 (Docker MCP Catalog). Centipid ISP Billing is an MCP server published by centipidbilling.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-22. 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
MarketplaceSuzieqCentipid ISP Billing
Docker MCP Catalog Listed
Version: sha256:ea9f7d06053d
Forks (GitHub): 1
Pulls (Docker Hub): 33 589
Stars (Docker Hub): 1
Stars (GitHub): 4
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.1.0
No figure published
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

Suzieq vs Centipid ISP Billing
FactSuzieqCentipid ISP Billing
Marketplaces that list it11
Stars (GitHub) (differs)4No figure on GitHub
Pulls (Docker Hub) (differs)33 589No figure on Docker Hub
Forks (GitHub) (differs)1No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/suzieq-mcp)Remote server (mcp.centipidbilling.com/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declares (differs)2Not published
Environment variables it asks for (differs)2, secrets among them: 1Not published
Licence (differs)MITNot stated
Repository (differs)github.com/povedaaqui/suzieq-mcpNot stated
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 3 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

Suzieq

In its own words, on Docker MCP Catalog:

MCP Server to interact with a SuzieQ network observability instance via its REST API.

Centipid ISP Billing

In its own words, on Official MCP Registry:

Query your ISP's revenue, subscribers, payments and routers. Needs a Centipid account and API key.

How to run each

Suzieq As a local MCP server: Docker image

Claude Code
claude mcp add --env "SUZIEQ_API_KEY=<YOUR_SUZIEQ_API_KEY>" --transport stdio suzieq -- docker run -i --rm -e SUZIEQ_API_KEY mcp/suzieq-mcp

Requires: SUZIEQ_API_KEY (secret)

Centipid ISP Billing As a remote MCP server

Claude Code
claude mcp add --transport http billing https://mcp.centipidbilling.com/mcp --header "Authorization: Bearer <YOUR_TOKEN>"

Requires: Authorization header

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

Only Centipid ISP Billing has a remote endpoint we check. How we check endpoints

Tools each declares

The marketplaces of Centipid ISP Billing publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of Centipid ISP Billing publish no settings it asks for, so we do not compare settings.

What it can do: Suzieq · What it can do: Centipid ISP Billing · 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