Maxio MCP vs three.ws Billing
Maxio MCP is an MCP server published by Servosity. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). three.ws Billing is an MCP server published by nirholas. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-20. 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
| Marketplace |   Maxio MCP |  three.ws Billing |
|---|---|---|
| Official MCP Registry | Listed Version: 0.1.4 Forks (GitHub): 13 Stars (GitHub): 61 Not marked · First seen |
Listed Version: 0.1.3 Downloads/month (npm): 158 Downloads/week (npm): 40 Forks (GitHub): 66 Stars (GitHub): 241 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
| Fact | Maxio MCP | three.ws Billing |
|---|---|---|
| Marketplaces that list it (differs) | 2 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 61 (worse) | 241 (better) |
| Forks (GitHub) (differs) | 13 (worse) | 66 (better) |
| Last release (differs) | 2026-10-16 | Not published |
| Where it runs (differs) | On your machine (https://github.com/Servosity/msp-skills/releases/download/maxio-v0.1.4/maxio-mcp.mcpb) | On your machine (@three-ws/billing-mcp) |
| Transport | stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 5, secrets among them: 4 | 3, secrets among them: 1 |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | github.com/servosity/msp-skills | github.com/nirholas/three.ws |
| Changes in the last 7 days (differs) | 5 | 0 |
| First seen | 2026-10-11 | 2026-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
Maxio MCP
Open, local revenue-intelligence CLI for Maxio Advanced Billing - MRR waterfalls
three.ws Billing
An agent's account economics — plan quotas, metered usage, invoices, receipts, and earnings.
How to run each
Maxio MCP As a Claude Code plugin
/plugin marketplace add servosity/msp-skills
/plugin install maxio@msp-skillsRequires: MAXIO_API_KEY (secret), MAXIO_PASSWORD (secret), MAXIO_SITE (secret), MAXIO_USERNAME (secret)
three.ws Billing As a local MCP server: npm package
claude mcp add --env "THREE_WS_SESSION=<YOUR_THREE_WS_SESSION>" --transport stdio billing-mcp -- npx -y @three-ws/billing-mcpRequires: THREE_WS_SESSION (secret)
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
Only Maxio MCP asks for
MAXIO_API_KEY (secret)MAXIO_BASE_URLMAXIO_PASSWORD (secret)MAXIO_SITE (secret)MAXIO_USERNAME (secret)
Only three.ws Billing asks for
THREE_WS_BASETHREE_WS_SESSION (secret)THREE_WS_TIMEOUT_MS
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: Maxio MCP · What it can do: three.ws Billing · Compare two other plugins
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.