Paid MCP Metering vs Fatstack
Paid MCP Metering is an MCP server published by dev55acc-ai. Marketplaces we read that list it: 1 (Official MCP Registry). Fatstack is an MCP server published by fatstack.net. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-05. 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 |  Paid MCP Metering |  Fatstack |
|---|---|---|
| Official MCP Registry | Listed Version: 2.0.0 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
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
| Fact | Paid MCP Metering | Fatstack |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) | 0 | 0 |
| Forks (GitHub) | 0 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (paid-mcp-metering-clsiojdd7-benlafreniere6-3913s-projects.vercel.app/mcp) | Remote server (www.fatstack.net/api/mcp) |
| Transport | Streamable HTTP | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/dev55acc-ai/paid-mcp-metering | github.com/f4tst4ck/fatstack-tools |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Status out of date: last check 6 days ago returned HTTP 404 | Responded 2 h 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
Paid MCP Metering
Metered MCP tools: free discovery over MCP; per-call execution settled in USDC via x402 v2.
Fatstack
Paid MCP tools behind one endpoint. Agents pay per call in USDC on Base via x402.
How to run each
Paid MCP Metering As a remote MCP server
claude mcp add --transport http paid-mcp-metering https://paid-mcp-metering-clsiojdd7-benlafreniere6-3913s-projects.vercel.app/mcpFatstack As a remote MCP server
claude mcp add --transport http registry https://www.fatstack.net/api/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only the endpoint of Fatstack responded at the last daily 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
Neither one's marketplaces publish the settings it asks for.
What it can do: Paid MCP Metering · What it can do: Fatstack · Compare two other plugins
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.