Healthparse Healthcare Data Gateway vs Slate
A side-by-side look at the Healthparse Healthcare Data Gateway and Slate MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
H
Healthparse Healthcare Data GatewayBiology & BioinformaticsPay-per-call US healthcare data: hospital financials, prices, quality, exclusions, wages.37FairAuth: not declaredS
SlateBiology & BioinformaticsYour own SLATE health data in your AI assistant: read, trend, plan and log. Never suggests a dose.41FairAuth: not declaredVerdict: choose Healthparse Healthcare Data Gateway for biology & bioinformatics work; choose Slate for biology & bioinformatics. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
HChoose Healthparse Healthcare Data Gateway when
- You need dedicated capabilities in the Biology & Bioinformatics domain.
SChoose Slate when
- You need dedicated capabilities in the Biology & Bioinformatics domain.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | H Healthparse Healthcare Data Gateway | S Slate |
|---|---|---|
| Category | Biology & Bioinformatics | Biology & Bioinformatics |
| Quality signal | 37/100 · Fair | 41/100 · Fair |
| Install command | Not confirmed yet | Not confirmed yet |
| Transport | — | — |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | — | — |
| Directory activity | 0 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Healthparse Healthcare Data Gateway | View Slate |
Tools & capabilities
Healthparse Healthcare Data Gateway tools
No tool names declared yet. Check the project README from the listing page.
Slate 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.
Healthparse Healthcare Data Gateway
No confirmed install command for Healthparse Healthcare Data Gateway yet — follow the setup steps linked from its listing page rather than a guessed package name.
Slate
No confirmed install command for Slate yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
Healthparse Healthcare Data Gateway is categorized under Biology & Bioinformatics and uses an install path we have not confirmed yet. Slate belongs to Biology & Bioinformatics and uses an install path we have not confirmed yet. Pick Healthparse Healthcare Data Gateway for biology & bioinformatics work and Slate for biology & bioinformatics.
Neither server has a confirmed install command yet, so we don't publish a guessed config. Follow each project's own setup instructions, linked from its listing page.
Healthparse Healthcare Data Gateway has no declared pricing — check the project's own site. Slate 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 healthparse-healthcare-data-gateway and slate as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Healthparse Healthcare Data Gateway has a quality signal of 37/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Slate has 41/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.