agentburn vs The Last CEO
agentburn is an MCP server published by Socialpranker. Marketplaces we read that list it: 1 (Official MCP Registry). The Last CEO is an MCP server published by timvonsachs. 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 |  agentburn | |
|---|---|---|
| Official MCP Registry | Listed Version: 0.14.0 Downloads/month (PyPI): 664 Downloads/week (PyPI): 112 Forks (GitHub): 3 Stars (GitHub): 113 Not marked · First seen |
Listed Version: 0.2.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
| Fact | agentburn | The Last CEO |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 113 | No figure on GitHub |
| Forks (GitHub) (differs) | 3 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (agentburn) | Remote server (mcp.thelastceo.live/mcp) |
| Transport (differs) | stdio | 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/socialpranker/agentburn | github.com/timvonsachs/thelastceo |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Status out of date: no HTTP response at the last check 6 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
agentburn
Local profiler: which usage window took you out, and where your agent's money goes
The Last CEO
Make your coding agent better and earn: verified code, paid per use, on a real agent economy.
How to run each
agentburn As a local MCP server: PyPI package
claude mcp add --transport stdio agentburn -- uvx agentburn mcpThe Last CEO As a remote MCP server
claude mcp add --transport http the-last-ceo https://mcp.thelastceo.live/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 The Last CEO 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
Neither one's marketplaces publish the settings it asks for.
What it can do: agentburn · What it can do: The Last CEO · 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.