In-depth architectural comparison of the Hub MCP and Scrapeunblocker MCP Remote 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.
At a Glance & Executive Verdict
Hub MCP
Developer Tools · Remote HTTP/SSE
Quality: 77/100 (Great) | Auth: API Key required
Scrapeunblocker MCP Remote
Developer Tools · Remote HTTP/SSE
Quality: 51/100 (Good) | Auth: No auth required
Verdict Summary: Choose Hub MCP if you need specialized Developer Tools tools running via a hosted cloud SSE transport. Choose Scrapeunblocker MCP Remote if your workspace requires Developer Tools integration with remote web transport. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Hub MCP when:
You need dedicated capabilities in the Developer Tools domain.
You prefer remote streaming HTTP/SSE transport architecture.
Your security boundary fits: API Key required (Free / Open Source).
You have access to required keys: HUB_PAT_TOKEN, MCP_AUTH_TOKEN.
Hub MCP is categorized under Developer Tools and uses a remote streaming HTTP/SSE transport. In contrast, Scrapeunblocker MCP Remote belongs to Developer Tools using remote streaming HTTP/SSE transport. Select Hub MCP when you need capabilities focused on developer tools and Scrapeunblocker MCP Remote when you require tools for developer tools.
Number of documents to skip for pagination (number, optional)
images
Filter on image names (string, optional)
operating_systems
Filter on operating systems (string, optional)
order
Change the ordering of results (string, optional)
size
Maximum number of results to return (number, optional)
sort
Sort results by search field (string, optional)
+23 more tools listed on main page
Scrapeunblocker MCP Remote Tools (4)
fetch_html
Fetch the fully rendered HTML of a URL. Optionally pass `steps` to interact with the page (search, click, type, paginate) in a real browser before capture.
fetch_parsed
Fetch a page and return AI-parsed structured JSON.
google_search
Run a Google search and return organic results as JSON.
list_elements
Return a page's interactive elements (buttons, inputs, selects, links, forms) with ready-to-use selectors, as JSON, to build `steps`.