ai.cdbx/mcp-server vs Pibox
ai.cdbx/mcp-server is an MCP server published by cdbx.ai. Marketplaces we read that list it: 1 (Official MCP Registry). Pibox is an MCP server published by psyb0t. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-29. 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 |  ai.cdbx/mcp-server |  Pibox |
|---|---|---|
| Official MCP Registry | Listed Version: 1.1.0 No figure published Not marked · First seen |
Listed Version: 0.21.0 Forks (GitHub): 0 Stars (GitHub): 3 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 | ai.cdbx/mcp-server | Pibox |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | No figure on GitHub | 3 |
| Forks (GitHub) (differs) | No figure on GitHub | 0 |
| Last release (differs) | Not published | 2026-10-24 |
| Where it runs (differs) | Remote server (cdbx.ai/api/mcp/server) | On your machine (docker.io/psyb0t/pibox:v0.21.0) |
| 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/christopherhbutler/cdbx.ai | github.com/psyb0t/docker-pibox |
| Changes in the last 7 days (differs) | 0 | 4 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 2 days ago | no remote endpoint we check |
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
ai.cdbx/mcp-server
Build Apps and run code in 30 languages — sandboxed, with persistent sessions for agent loops.
Pibox
Self-hosted MCP server: pi-coding-agent tools (run_prompt, file ops) over streamable HTTP.
How to run each
ai.cdbx/mcp-server As a remote MCP server
claude mcp add --transport http ai-cdbx-mcp-server https://cdbx.ai/api/mcp/server --header "Authorization: Bearer <YOUR_TOKEN>"Requires: Authorization header
Pibox
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only ai.cdbx/mcp-server 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: ai.cdbx/mcp-server · What it can do: Pibox · 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.