HealthChain vs Swissmedic
A side-by-side look at the HealthChain and Swissmedic MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose HealthChain for biology & bioinformatics work as a local process; choose Swissmedic 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 HealthChain 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 Swissmedic when
- You need dedicated capabilities in the Biology & Bioinformatics domain.
- You prefer a local stdio subprocess transport.
- You want tools like
total_matches, match_type.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Biology & Bioinformatics | Biology & Bioinformatics |
| Quality signal | 59/100 · Good | 52/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | No auth required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 229 | 0 |
| Directory activity | 5 views 1 installs 1 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | 2 |
| Full listing | View HealthChain | View Swissmedic |
Tools & capabilities
HealthChain tools
No tool names declared yet. Check the project README from the listing page.
Swissmedic tools 2
total_matchesmatch_type
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.
HealthChain
{
"mcpServers": {
"healthchainai-healthchain": {
"command": "uvx",
"args": [
"healthchain"
]
}
}
}
Swissmedic
{
"mcpServers": {
"swissmedic": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-swissmedic"
]
}
}
}
Frequently asked questions
HealthChain is categorized under Biology & Bioinformatics and uses a local stdio subprocess. Swissmedic belongs to Biology & Bioinformatics and uses a local stdio subprocess. Pick HealthChain for biology & bioinformatics work and Swissmedic 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.
HealthChain is listed as free. Auth: no auth required. Swissmedic 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 healthchainai-healthchain and swissmedic as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, HealthChain has a quality signal of 59/100 (Good) with 5 views, 1 installs and 229 GitHub stars. Swissmedic has 52/100 (Good) with 0 views, 0 installs and 0 GitHub stars.