com.puter/mcp-server vs sh.objekt/mcp-upload
com.puter/mcp-server is an MCP server published by puter.com. Marketplaces we read that list it: 1 (Official MCP Registry). sh.objekt/mcp-upload is an MCP server published by objekt.sh. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-26. 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.puter/mcp-server |  sh.objekt/mcp-upload |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.1 Forks (GitHub): 4 116 Stars (GitHub): 43 899 Not marked · First seen |
Listed Version: 0.1.5 Downloads/month (npm): 94 Downloads/week (npm): 11 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 | com.puter/mcp-server | sh.objekt/mcp-upload |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 43 899 (better) | 0 (worse) |
| Forks (GitHub) (differs) | 4 116 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (mcp.puter.com) | On your machine (@objekt.sh/mcp-upload) |
| 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) | github.com/heyputer/puter | github.com/0xlighthouse/objekt-mcp-upload |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Not responding since 2026-10-26 | 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.puter/mcp-server
Puter MCP enables AI tools to interact with Puter: manage files, websites, workers, and more
sh.objekt/mcp-upload
Public file storage for AI agents. Upload files and get a permalink back.
How to run each
com.puter/mcp-server As a remote MCP server
claude mcp add --transport http com-puter-mcp-server https://mcp.puter.com/sh.objekt/mcp-upload As a local MCP server: npm package
claude mcp add --env "OBJEKT_API_KEY=<YOUR_OBJEKT_API_KEY>" --transport stdio mcp-upload -- npx -y @objekt.sh/mcp-uploadRequires: OBJEKT_API_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only com.puter/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
The marketplaces of com.puter/mcp-server publish no settings it asks for, so we do not compare settings.
What it can do: com.puter/mcp-server · What it can do: sh.objekt/mcp-upload · 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.