Seshat MCP vs HealthChain
A side-by-side look at the Seshat MCP and HealthChain MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
S
Seshat MCPBiology & Bioinformatics · Local subprocess (stdio)Structural code intelligence for AI agents: real call graphs, blast radius, and change history.52GoodAuth: not declaredVerdict: choose Seshat MCP 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?
SChoose Seshat MCP when
- You need dedicated capabilities in the Biology & Bioinformatics domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
SESHAT_API_KEY. - You want tools like
list_projects, list_modules, query_entities.
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 | S Seshat MCP | |
|---|---|---|
| Category | Biology & Bioinformatics | Biology & Bioinformatics |
| Quality signal | 52/100 · Good | 59/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | SESHAT_API_KEY |
Tools & capabilities
Seshat MCP tools 15
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,- +3 more on 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.
Seshat MCP
{
"mcpServers": {
"seshat-mcp": {
"command": "npx",
"args": [
"-y",
"@papyruslabsai/seshat-mcp"
],
"env": {
"SESHAT_API_KEY": "YOUR_SESHAT_API_KEY_HERE"
}
}
}
}
HealthChain
{
"mcpServers": {
"healthchainai-healthchain": {
"command": "uvx",
"args": [
"healthchain"
]
}
}
}
Frequently asked questions
Seshat MCP is categorized under Biology & Bioinformatics and uses a local stdio subprocess. HealthChain belongs to Biology & Bioinformatics and uses a local stdio subprocess. Pick Seshat MCP 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.
Seshat MCP has no declared pricing — check the project's own site. 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 seshat-mcp and healthchainai-healthchain as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Seshat MCP has a quality signal of 52/100 (Good) with 0 views, 0 installs and 0 GitHub stars. HealthChain has 59/100 (Good) with 4 views, 1 installs and 229 GitHub stars.