Companies House vs Tx Medical Exclusions
A side-by-side look at the Companies House and Tx Medical Exclusions MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Companies House for legal work as a local process; choose Tx Medical Exclusions for legal as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Companies House when
- You need dedicated capabilities in the Legal domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
COMPANIES_HOUSE_API_KEY.
Choose Tx Medical Exclusions when
- You need dedicated capabilities in the Legal domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Legal | Legal |
| Quality signal | 48/100 · Fair | 41/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | COMPANIES_HOUSE_API_KEY | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 13 | 0 |
| Directory activity | 4 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Companies House | View Tx Medical Exclusions |
Tools & capabilities
Companies House tools
No tool names declared yet. Check the project README from the listing page.
Tx Medical Exclusions tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Companies House
{
"mcpServers": {
"companies-house": {
"command": "npx",
"args": [
"-y",
"companies-house-mcp"
],
"env": {
"COMPANIES_HOUSE_API_KEY": "YOUR_COMPANIES_HOUSE_API_KEY_HERE"
}
}
}
}
Tx Medical Exclusions
{
"mcpServers": {
"tx-medical-exclusions": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-tx-medical-exclusions"
]
}
}
}
Frequently asked questions
Companies House is categorized under Legal and uses a local stdio subprocess. Tx Medical Exclusions belongs to Legal and uses a local stdio subprocess. Pick Companies House for legal work and Tx Medical Exclusions for legal.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Companies House has no declared pricing — check the project's own site. Tx Medical Exclusions is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add companies-house and tx-medical-exclusions as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Companies House has a quality signal of 48/100 (Fair) with 4 views, 0 installs and 13 GitHub stars. Tx Medical Exclusions has 41/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.