Firecrawl MCP Server vs io.github.shephouse-actors/shephouse-yt-mcp
Firecrawl MCP Server is an MCP server published by firecrawl. Marketplaces we read that list it: 3 (Official MCP Registry, Docker MCP Catalog, Community GitHub marketplaces). io.github.shephouse-actors/shephouse-yt-mcp is an MCP server published by shephouse-actors. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-14. 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 | ||
|---|---|---|
| Official MCP Registry | Listed Version: 3.40.0 Downloads/month (npm): 517 013 Downloads/week (npm): 158 613 Forks (GitHub): 930 Stars (GitHub): 7 813 Not marked · First seen |
Listed Version: 0.1.0 No figure published Not marked · First seen |
| Docker MCP Catalog | Listed Version: sha256:3b22a74af198 Forks (GitHub): 930 Pulls (Docker Hub): 151 195 Stars (Docker Hub): 20 Stars (GitHub): 7 813 Not marked · First seen |
Not listed |
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 | Firecrawl MCP Server | io.github.shephouse-actors/shephouse-yt-mcp |
|---|---|---|
| Marketplaces that list it (differs) | 3 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 7 813 | No figure on GitHub |
| Pulls (Docker Hub) (differs) | 151 195 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 930 | No figure on GitHub |
| Last release (differs) | 2026-11-12 | Not published |
| Where it runs (differs) | Remote server or your machine | On your machine (shephouse-yt-mcp) |
| Transport (differs) | Streamable HTTP, stdio | stdio |
| Tools it declares (differs) | 28 | Not published |
| Environment variables it asks for (differs) | 2, secrets among them: 1 | 1, secrets among them: 1 |
| Parts of the bundle (differs) | 18 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/firecrawl/firecrawl-mcp-server | github.com/shephouse-actors/shephouse-yt-mcp |
| Changes in the last 7 days | 2 | 2 |
| First seen (differs) | 2026-10-11 | 2026-10-29 |
| Endpoint at the last check (differs) | Responded 4 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
Firecrawl MCP Server
Firecrawl, the context API for AI agents: search, scrape, interact with the web, plus paper search.
io.github.shephouse-actors/shephouse-yt-mcp
YouTube transcripts for agents on cloud servers, via an Apify Actor. By ShepHouse (AI-operated).
How to run each
Firecrawl MCP Server As a remote MCP server
claude mcp add --transport http firecrawl-mcp-server https://mcp.firecrawl.dev/v2/mcp --header "Authorization: Bearer <YOUR_TOKEN>"
Requires: FIRECRAWL_API_KEY (secret), Authorization header
io.github.shephouse-actors/shephouse-yt-mcp As a local MCP server: PyPI package
claude mcp add --env "APIFY_TOKEN=<YOUR_APIFY_TOKEN>" --transport stdio shephouse-yt-mcp -- uvx shephouse-yt-mcp
Requires: APIFY_TOKEN (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Firecrawl MCP Server has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of io.github.shephouse-actors/shephouse-yt-mcp publish no list of tools, so we do not compare tools.
Settings each asks for
Only Firecrawl MCP Server asks for
FIRECRAWL_API_KEY (secret)FIRECRAWL_API_URL
Only io.github.shephouse-actors/shephouse-yt-mcp asks for
APIFY_TOKEN (secret)
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: Firecrawl MCP Server · What it can do: io.github.shephouse-actors/shephouse-yt-mcp · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.