Mirobody vs HealthChain
A side-by-side look at the Mirobody and HealthChain MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
M
MirobodyBiology & Bioinformatics · Local subprocess (stdio)Turn scattered health data into answers you can trace. Self-hosted AI health data engine for lab reports, wearables and genetics, with a built-in MCP server. Run it with Docker and one LLM key, or keep every model local on llama.cpp.57GoodAuth: not declaredVerdict: choose Mirobody for biology & bioinformatics work as a local process; choose HealthChain 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?
MChoose Mirobody when
- You need dedicated capabilities in the Biology & Bioinformatics domain.
- You prefer a local stdio subprocess transport.
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.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | M Mirobody | |
|---|---|---|
| Category | Biology & Bioinformatics | Biology & Bioinformatics |
| Quality signal | 57/100 · Good | 59/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | BYOK (pay the provider) | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1,381 | 229 |
| Directory activity | 0 views 0 installs 0 upvotes | 5 views 1 installs 1 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Mirobody | View HealthChain |
Tools & capabilities
Mirobody tools
No tool names declared yet. Check the project README from the listing page.
HealthChain 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.
Mirobody
{
"mcpServers": {
"mirobody": {
"command": "uvx",
"args": [
"--python",
"3.12",
"mirobody"
]
}
}
}
HealthChain
{
"mcpServers": {
"healthchainai-healthchain": {
"command": "uvx",
"args": [
"healthchain"
]
}
}
}
Frequently asked questions
Mirobody is categorized under Biology & Bioinformatics and uses a local stdio subprocess. HealthChain belongs to Biology & Bioinformatics and uses a local stdio subprocess. Pick Mirobody for biology & bioinformatics work and HealthChain 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.
Mirobody is bring-your-own-key: usage is billed by the API provider you supply a key for. HealthChain 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 mirobody and healthchainai-healthchain as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Mirobody has a quality signal of 57/100 (Good) with 0 views, 0 installs and 1,381 GitHub stars. HealthChain has 59/100 (Good) with 5 views, 1 installs and 229 GitHub stars.