Ext Ops Panel
Open dashboard
Comparison

Plugged.in Proxy vs com.sociahive/sociahive

Plugged.in Proxy is an MCP server published by VeriTeknik. Marketplaces we read that list it: 1 (Docker MCP Catalog). com.sociahive/sociahive is an MCP server published by sociahive.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-25. 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
MarketplacePlugged.in Proxycom.sociahive/sociahive
Docker MCP Catalog Listed
Version: sha256:b7c32590b270
Forks (GitHub): 30
Pulls (Docker Hub): 36 074
Stars (Docker Hub): 3
Stars (GitHub): 137
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.2
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

Plugged.in Proxy vs com.sociahive/sociahive
FactPlugged.in Proxycom.sociahive/sociahive
Marketplaces that list it11
Stars (GitHub) (differs)137No figure on GitHub
Pulls (Docker Hub) (differs)36 074No figure on Docker Hub
Forks (GitHub) (differs)30No figure on GitHub
Last release (differs)Not published2026-10-20
Where it runs (differs)On your machine (mcp/pluggedin-mcp-proxy)Remote server (www.sociahive.com/api/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declares (differs)6Not published
Environment variables it asks for (differs)2, secrets among them: 1Not published
Licence (differs)Apache-2.0Not stated
Repository (differs)github.com/veriteknik/pluggedin-mcp-proxyNot stated
Changes in the last 7 days (differs)04
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 33 h ago, requires a key

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

Plugged.in Proxy

In its own words, on Docker MCP Catalog:

A unified MCP proxy that aggregates multiple MCP servers into one interface, enabling seamless tool discovery and management across all your AI interactions. Manage all your MCP servers from a single connection point with RAG capabilities and real-time notifications.

com.sociahive/sociahive

In its own words, on Official MCP Registry:

Run social media from AI: schedule posts on 22 networks, DM automations, analytics.

How to run each

Plugged.in Proxy As a local MCP server: Docker image

Claude Code
claude mcp add --env "PLUGGEDIN_API_KEY=<YOUR_PLUGGEDIN_API_KEY>" --transport stdio pluggedin-mcp-proxy -- docker run -i --rm -e PLUGGEDIN_API_KEY mcp/pluggedin-mcp-proxy

Requires: PLUGGEDIN_API_KEY (secret)

com.sociahive/sociahive As a remote MCP server

Claude Code
claude mcp add --transport http sociahive https://www.sociahive.com/api/mcp

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only com.sociahive/sociahive has a remote endpoint we check. How we check endpoints

Tools each declares

The marketplaces of com.sociahive/sociahive publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of com.sociahive/sociahive publish no settings it asks for, so we do not compare settings.

What it can do: Plugged.in Proxy · What it can do: com.sociahive/sociahive · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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