Medical MCP vs Who Ictrp
A side-by-side look at the Medical MCP and Who Ictrp MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
W
Who IctrpBiology & Bioinformatics · Local subprocess (stdio)WHO ICTRP — the International Clinical Trials Registry Platform search41FairAuth: no auth requiredVerdict: choose Medical MCP for biology & bioinformatics work as a local process; choose Who Ictrp for biology & bioinformatics as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Medical MCP when
- You need dedicated capabilities in the Biology & Bioinformatics domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
WChoose Who Ictrp when
- You need dedicated capabilities in the Biology & Bioinformatics 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 | W Who Ictrp | |
|---|---|---|
| Category | Biology & Bioinformatics | Biology & Bioinformatics |
| Quality signal | 61/100 · Good | 41/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | No auth required | No auth required |
| Pricing | Free | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 119 | 0 |
| Directory activity | 4 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Medical MCP | View Who Ictrp |
Tools & capabilities
Medical MCP tools
No tool names declared yet. Check the project README from the listing page.
Who Ictrp 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.
Medical MCP
{
"mcpServers": {
"jamesanz-medical-mcp": {
"command": "npx",
"args": [
"-y",
"medical-mcp"
]
}
}
}
Who Ictrp
{
"mcpServers": {
"who-ictrp": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-who-ictrp"
]
}
}
}
Frequently asked questions
Medical MCP is categorized under Biology & Bioinformatics and uses a local stdio subprocess. Who Ictrp belongs to Biology & Bioinformatics and uses a local stdio subprocess. Pick Medical MCP for biology & bioinformatics work and Who Ictrp for biology & bioinformatics.
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.
Medical MCP is listed as free. Auth: no auth required. Who Ictrp 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 jamesanz-medical-mcp and who-ictrp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Medical MCP has a quality signal of 61/100 (Good) with 4 views, 0 installs and 119 GitHub stars. Who Ictrp has 41/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.