com.machineinbox/machine-inbox vs EmptyInbox
com.machineinbox/machine-inbox is an MCP server published by machineinbox.com. Marketplaces we read that list it: 1 (Official MCP Registry). EmptyInbox is an MCP server published by cnohall. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-25. 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 |  com.machineinbox/machine-inbox |  EmptyInbox |
|---|---|---|
| Official MCP Registry | Listed Version: 0.1.0 No figure published Not marked · First seen |
Listed Version: 1.5.0 Downloads/month (npm): 597 Downloads/week (npm): 418 Forks (GitHub): 1 Stars (GitHub): 4 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 | com.machineinbox/machine-inbox | EmptyInbox |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | No figure on GitHub | 4 |
| Forks (GitHub) (differs) | No figure on GitHub | 1 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (machineinbox.com/mcp) | On your machine (emptyinbox-mcp) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 1, secrets among them: 1 |
| Licence | Not stated | Not stated |
| Repository (differs) | Not stated | github.com/blockonomics/emptyinbox-me |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 12 h 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
com.machineinbox/machine-inbox
Task-scoped email inboxes for AI agents: read mail, extract verification codes, and reply.
EmptyInbox
Zero-config disposable email inboxes for AI agents: create, read mail, await verify codes.
How to run each
com.machineinbox/machine-inbox As a remote MCP server
claude mcp add --transport http machine-inbox https://machineinbox.com/mcpEmptyInbox As a local MCP server: npm package
claude mcp add --env "EMPTYINBOX_API_KEY=<YOUR_EMPTYINBOX_API_KEY>" --transport stdio emptyinbox -- npx -y emptyinbox-mcpRequires: EMPTYINBOX_API_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only com.machineinbox/machine-inbox 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
The marketplaces of com.machineinbox/machine-inbox publish no settings it asks for, so we do not compare settings.
What it can do: com.machineinbox/machine-inbox · What it can do: EmptyInbox · 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.