Hub MCP vs Relvato — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Hub MCP vs Relvato
In-depth architectural comparison of the Hub MCP and Relvato 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
Relvato
Developer Tools · Remote HTTP/SSE
Quality: 52/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 Relvato 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, Relvato belongs to Developer Tools using remote streaming HTTP/SSE transport. Select Hub MCP when you need capabilities focused on developer tools and Relvato 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
Relvato Tools (57)
list_sites
List the account's websites and whether each is ready to run monitors.
add_site
Add a website and get its setup step: connect the WordPress plugin, or verify the domain.
verify_site
Check that setup step: the plugin connection, or the domain-verification DNS record or meta tag.
start_monitoring_for_goals
Pick what matters (checkout, security, search, speed, …) and get the monitors that cover it on your plan.
list_checks
The monitors you can add to a site: what each catches, whether your plan includes it, and which are recommended.
add_checks
Add monitors to a site; each one reports added, already there, or why not.
dismiss_recommendation
Stop recommending a monitor for a site, or bring dismissed recommendations back.
calibrate_site
WooCommerce: read the store again (a product to buy, checkout type, currency) after it changed.
verify_vitals_beacon
Check the real-user Web Vitals beacon is installed.
site_overview
Plain-language health verdict: what needs attention, every monitor with its latest run and schedule, plan usage and, on WordPress, the site's AI abilities.
get_site_health
Pass rate now and over 30 days, the trend over 28–182 days, each group's briefing, and probe uptime with incidents.
get_performance
Lab and real-user Core Web Vitals, what slows the site down, and the top fixes with steps.