A side-by-side look at the HealthChain and Seshat MCP 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 Seshat MCP for biology & bioinformatics as a local process. You can also run both side by side in one mcpServers block.
SESHAT_API_KEY.list_projects, list_modules, query_entities.Rows where the two servers differ are marked.
| Spec | S Seshat MCP | |
|---|---|---|
| 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 | SESHAT_API_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 229 | 0 |
| Directory activity | 4 views 1 installs 1 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | 15 |
| Full listing | View HealthChain | View Seshat MCP |
No tool names declared yet. Check the project README from the listing page.
list_projectswhat is syncedlist_moduleshow the codebase is organized, by layer or modulequery_entitiesfind functions, classes, and routes by name, layer, or modulefind_entry_pointsroutes, exports, and the public API surfaceget_entitysignature, callers, callees, data flow, side effects, and tables touchedget_dependenciesthe real call chain, callers and calleesget_blast_radiuseverything that breaks if you change it, transitivelyget_data_flowwhat a function reads, returns, and mutatesget_optimal_contextthe minimal, ranked set of files to read before editingfind_by_constraintevery function that touches a given table (or carries a given trait)find_dead_codeunreachable symbols, safe to deletequery_call_sitescalls by their state: async calls never awaited (floating promises,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.
{
"mcpServers": {
"healthchainai-healthchain": {
"command": "uvx",
"args": [
"healthchain"
]
}
}
}
{
"mcpServers": {
"seshat-mcp": {
"command": "npx",
"args": [
"-y",
"@papyruslabsai/seshat-mcp"
],
"env": {
"SESHAT_API_KEY": "YOUR_SESHAT_API_KEY_HERE"
}
}
}
}