Companies House vs Weckr — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Companies House vs Weckr
In-depth architectural comparison of the Companies House and Weckr 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
Weckr
Developer Tools · Local stdio
Quality: 45/100 (Fair) | Auth: No auth required
Verdict Summary: Choose Companies House if you need specialized Developer Tools tools running via a local process. Choose Weckr 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.
Companies House is categorized under Developer Tools and uses a local stdio subprocess. In contrast, Weckr belongs to Developer Tools using local stdio subprocess. Select Companies House when you need capabilities focused on developer tools and Weckr when you require tools for developer tools.