Fetchwire - Social Data vs Caelario
Fetchwire - Social Data is an MCP server published by fetchwire.dev. Marketplaces we read that list it: 1 (Official MCP Registry). Caelario is an MCP server published by chunkydonut21. 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
| Marketplace |  Caelario | |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.1 No figure published Not marked · First seen |
Listed Version: 0.1.5 Downloads/month (npm): 201 Downloads/week (npm): 35 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 | Fetchwire - Social Data | Caelario |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | No figure on GitHub | 0 |
| Forks (GitHub) (differs) | No figure on GitHub | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (mcp.fetchwire.dev/mcp) | On your machine (caelario-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/chunkydonut21/caelario-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Answered with HTTP 404 (2 days 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
Fetchwire - Social Data
YouTube, TikTok, Instagram, X, Reddit, LinkedIn and Threads: public data in one schema.
Caelario
MCP server for Instagram, TikTok, YouTube, X and Facebook data extraction and automation.
How to run each
Fetchwire - Social Data As a remote MCP server
claude mcp add --transport http social-data https://mcp.fetchwire.dev/mcp --header "X-API-Key: <YOUR_X_API_KEY>"Requires: X-API-Key header
Caelario As a local MCP server: npm package
claude mcp add --env "CAELARIO_API_KEY=<YOUR_CAELARIO_API_KEY>" --transport stdio caelario -- npx -y caelario-mcpRequires: CAELARIO_API_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Fetchwire - Social Data 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 Fetchwire - Social Data publish no settings it asks for, so we do not compare settings.
What it can do: Fetchwire - Social Data · What it can do: Caelario · 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.