Whimbrel MedTech Analyst vs HEY Research Lab
A side-by-side look at the Whimbrel MedTech Analyst and HEY Research Lab MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Whimbrel MedTech Analyst for legal work; choose HEY Research Lab 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 Whimbrel MedTech Analyst when
- You need dedicated capabilities in the Legal domain.
Choose HEY Research Lab when
- You need dedicated capabilities in the Legal domain.
- You prefer a local stdio subprocess transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Legal | Legal |
| Quality signal | 29/100 · Emerging | 43/100 · Fair |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 0 |
| Directory activity | 0 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Whimbrel MedTech Analyst | View HEY Research Lab |
Tools & capabilities
Whimbrel MedTech Analyst tools
No tool names declared yet. Check the project README from the listing page.
HEY Research Lab 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.
Whimbrel MedTech Analyst
No confirmed install command for Whimbrel MedTech Analyst yet — follow the setup steps linked from its listing page rather than a guessed package name.
HEY Research Lab
{
"mcpServers": {
"hey-research-lab": {
"command": "npx",
"args": [
"-y",
"@hey-research-lab/mcp"
]
}
}
}
Frequently asked questions
Whimbrel MedTech Analyst is categorized under Legal and uses an install path we have not confirmed yet. HEY Research Lab belongs to Legal and uses a local stdio subprocess. Pick Whimbrel MedTech Analyst for legal work and HEY Research Lab 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. Whimbrel MedTech Analyst has no confirmed install command yet — follow its own setup instructions.
Whimbrel MedTech Analyst has no declared pricing — check the project's own site. HEY Research Lab has no declared pricing — check the project's own site. 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 whimbrel-medtech-analyst and hey-research-lab as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Whimbrel MedTech Analyst has a quality signal of 29/100 (Emerging) with 0 views, 0 installs and 0 GitHub stars. HEY Research Lab has 43/100 (Fair) with 1 views, 0 installs and 0 GitHub stars.