Plugged.in Proxy vs Msha Mines
Plugged.in Proxy is an MCP server published by VeriTeknik. Marketplaces we read that list it: 1 (Docker MCP Catalog). Msha Mines is an MCP server published by pipeworx-io. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-08. 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 | ||
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:b7c32590b270 Forks (GitHub): 29 Pulls (Docker Hub): 36 655 Stars (Docker Hub): 3 Stars (GitHub): 139 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.2.1 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 | Plugged.in Proxy | Msha Mines |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 139 (better) | 0 (worse) |
| Pulls (Docker Hub) (differs) | 36 655 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 29 (better) | 0 (worse) |
| Last release (differs) | Not published | 2026-11-03 |
| Where it runs (differs) | On your machine (mcp/pluggedin-mcp-proxy) | Remote server (gateway.pipeworx.io/msha-mines/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares (differs) | 6 | Not published |
| Environment variables it asks for (differs) | 2, secrets among them: 1 | 1, secrets among them: 1 |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | github.com/veriteknik/pluggedin-mcp-proxy | github.com/pipeworx-io/mcp-msha-mines |
| Changes in the last 7 days (differs) | 0 | 1 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 2 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
Plugged.in Proxy
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.
Msha Mines
MSHA mine records — search a US mine by operator or mine name, or look up a known MSHA Mine ID for…
How to run each
Plugged.in Proxy As a local MCP server: Docker image
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)
Msha Mines As a remote MCP server
claude mcp add --transport http msha-mines https://gateway.pipeworx.io/msha-mines/mcp
Requires: PIPEWORX_API_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Msha Mines has a remote endpoint we check. How we check endpoints
Tools each declares
Only Plugged.in Proxy has
pluggedin_ask_knowledge_basepluggedin_delete_notificationpluggedin_discover_toolspluggedin_list_notificationspluggedin_mark_notification_donepluggedin_send_notification
Only Msha Mines has
ai_visibility_checkarchive_comparearchive_evidenceask_pipeworxask_pipeworx_betaask_pipeworx_groundedbet_researchclassify_rowcompany_factscompany_register_searchcompare_entitiesdeep_research
Show the remaining 32
discover_toolsentity_profileforgetgenerate_llms_txtkalshi_weather_edgelist_subscriptionsmsha_mine_detailmsha_mine_searchmsha_violation_countspipeworx_feedbackpipeworx_trendingpolymarket_arbitragepolymarket_edge_trackerpolymarket_edgespolymarket_fill_riskpolymarket_kalshi_spreadrecallrecent_alertsrecent_changesrelease_calendar_marketsrememberresearch_rowresolution_auditresolution_diffresolve_entityscan_competitor_ai_presencescan_dependencysearch_withinsubscribesuggest_questionsunsubscribevalidate_claim
Both have
None
Tool names as the marketplaces declare them and as Ext Ops observed them on the endpoints (Msha Mines as of 2026-10-20). More tools is not better in itself: compare what each needs for the job.
Settings each asks for
Only Plugged.in Proxy asks for
PLUGGEDIN_API_BASE_URLPLUGGEDIN_API_KEY (secret)
Only Msha Mines asks for
PIPEWORX_API_KEY (secret)
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: Plugged.in Proxy · What it can do: Msha Mines · 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.