Ext Ops Panel
Open dashboard
Comparison

tsm vs com.puter/mcp-server

tsm is a plugin bundle for AI coding tools published by lu-zhengda. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). com.puter/mcp-server is an MCP server published by puter.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-17. 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

Where each is published
Marketplacetsmcom.puter/mcp-server
Claude Code: claude-plugins-community Listed
Version: 0.6.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.1
Forks (GitHub): 4 098
Stars (GitHub): 43 761
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

tsm vs com.puter/mcp-server
Facttsmcom.puter/mcp-server
Marketplaces that list it11
Stars (GitHub) (differs)0 (worse)43 761 (better)
Forks (GitHub) (differs)0 (worse)4 098 (better)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (mcp.puter.com)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)1Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/lu-zhengda/tsmgithub.com/heyputer/puter
Changes in the last 7 days00
First seen (differs)2026-10-122026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 3 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

tsm

In its own words, on Claude Code: claude-plugins-community:

Manage Transmission BitTorrent client from Claude Code. Add torrents, monitor downloads, set per-file priorities, apply seeding policies by label, bulk-replace trackers, and automate torrent workflows, all through natural language. Supports JSON output for scripting, macOS Keychain auth, multi-server profiles, and advanced filtering (e.g., "ratio>2.0 AND label:movies AND age<7d").

com.puter/mcp-server

In its own words, on Official MCP Registry:

Puter MCP enables AI tools to interact with Puter: manage files, websites, workers, and more

How to run each

tsm As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install tsm@claude-community

com.puter/mcp-server As a remote MCP server

Claude Code
claude mcp add --transport http com-puter-mcp-server https://mcp.puter.com/

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

Neither one's marketplaces publish the settings it asks for.

What it can do: tsm · What it can do: com.puter/mcp-server · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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.

Where the data comes from: how the catalog is built