findem-studio vs TopClozer LinkedIn MCP
findem-studio is a plugin bundle for AI coding tools published by findemdev. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). TopClozer LinkedIn MCP is an MCP server published by topclozer.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-23. 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 |  findem-studio | |
|---|---|---|
| Claude Code: claude-plugins-community | Listed Version: 9115be6 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 2.0.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 | findem-studio | TopClozer LinkedIn MCP |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 0 | No figure on GitHub |
| Forks (GitHub) (differs) | 0 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (topclozer.com/api/mcp) |
| Transport (differs) | Not stated | 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/findemdev/findem-studio-claude-plugin | Not stated |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen (differs) | 2026-10-11 | 2026-10-16 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 26 h 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
findem-studio
Findem Studio plugin for talent intelligence — 3 remote MCP connectors with OAuth, comprehensive reviewer runbook.
TopClozer LinkedIn MCP
LinkedIn for AI agents: search people, read profiles, posts and connections via a connected account
How to run each
findem-studio As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install findem-studio@claude-communityTopClozer LinkedIn MCP As a remote MCP server
claude mcp add --transport http linkedin https://topclozer.com/api/mcp --header "Authorization: Bearer <YOUR_API_KEY>"Requires: Authorization header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only TopClozer LinkedIn MCP 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: findem-studio · What it can do: TopClozer LinkedIn MCP · 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.