Hub MCP vs Wickworks

In-depth architectural comparison of the Hub MCP and Wickworks MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

Which MCP Server Should You Choose?

Choose Hub MCP when:

• You need dedicated capabilities in the Cloud Platforms domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: API Key required (Free / Open Source).
• You have access to required keys: HUB_PAT_TOKEN, MCP_AUTH_TOKEN.
• Primary tools included: search, query, architectures.

Explore Hub MCP Details

Choose Wickworks when:

• You need dedicated capabilities in the Cloud Platforms domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).

Explore Wickworks Details

Feature & Specification Comparison

Specification	Hub MCP docker VerifiedCloud Platforms	Wickworks Cloud Platforms
Summary	Official MCP server to interact with Docker Hub, providing access to repositories, hub search and Docker Hardened Images	Self-hosted MCP server: technical indicators + smart-money-concepts from OHLC bars.
Category & Scope

Tools & Capabilities Breakdown

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

{
  "mcpServers": {
    "docker-hub-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/inspector"
      ],
      "env": {
        "HUB_PAT_TOKEN": "YOUR_HUB_PAT_TOKEN_HERE",
        "MCP_AUTH_TOKEN": "YOUR_MCP_AUTH_TOKEN_HERE"
      }
    }
  }
}

{
  "mcpServers": {
    "wickworks": {
      "command": "npx",
      "args": [
        "-y",
        "wickworks"
      ]
    }
  }
}

Related MCP Server Comparisons