Who Ictrp vs Medical MCP
A side-by-side look at the Who Ictrp and Medical MCP 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 Who Ictrp for biology & bioinformatics work as a local process; choose Medical MCP 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?
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.
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.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | W Who Ictrp | |
|---|---|---|
| Category | Biology & Bioinformatics | Biology & Bioinformatics |
| Quality signal | 41/100 · Fair | 61/100 · Good |
| 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 | 0 | 119 |
| Directory activity | 0 views 0 installs 0 upvotes | 4 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Who Ictrp | View Medical MCP |
Tools & capabilities
Who Ictrp tools
No tool names declared yet. Check the project README from the listing page.
Medical MCP 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.
Who Ictrp
{
"mcpServers": {
"who-ictrp": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-who-ictrp"
]
}
}
}
Medical MCP
{
"mcpServers": {
"jamesanz-medical-mcp": {
"command": "npx",
"args": [
"-y",
"medical-mcp"
]
}
}
}
Frequently asked questions
Who Ictrp is categorized under Biology & Bioinformatics and uses a local stdio subprocess. Medical MCP belongs to Biology & Bioinformatics and uses a local stdio subprocess. Pick Who Ictrp for biology & bioinformatics work and Medical MCP 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.
Who Ictrp is listed as free. Auth: no auth required. Medical MCP 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 who-ictrp and jamesanz-medical-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Who Ictrp has a quality signal of 41/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Medical MCP has 61/100 (Good) with 4 views, 0 installs and 119 GitHub stars.