Companies House vs UISandbox — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Companies House vs UISandbox
In-depth architectural comparison of the Companies House and UISandbox 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
Companies House
Developer Tools · Local stdio
Quality: 47/100 (Fair) | Auth: No auth required
UISandbox
Developer Tools · Local stdio
Quality: 44/100 (Fair) | Auth: No auth required
Verdict Summary: Choose Companies House if you need specialized Developer Tools tools running via a local process. Choose UISandbox if your workspace requires Developer Tools integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Companies House when:
You need dedicated capabilities in the Developer Tools domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
You have access to required keys: COMPANIES_HOUSE_API_KEY.
Primary tools included: Company and officer search, Company profiles and statutory records, Ownership, appointments and disqualification lookup.
You need dedicated capabilities in the Developer Tools domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Primary tools included: Loads ZIP files by local path or URL, Adjusts detected CSS and runtime style values, Verifies original and tokenized computed styles.
Companies House is categorized under Developer Tools and uses a local stdio subprocess. In contrast, UISandbox belongs to Developer Tools using local stdio subprocess. Select Companies House when you need capabilities focused on developer tools and UISandbox when you require tools for developer tools.