Git vs Healthpoint Rs
A side-by-side look at the Git and Healthpoint Rs MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Git for other tools and integrations work as a local process; choose Healthpoint Rs for biology, medicine and bioinformatics. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Git when
- You need dedicated capabilities in the Other Tools and Integrations domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
create_entities, create_relations, add_observations.
Choose Healthpoint Rs when
- You need dedicated capabilities in the Biology, Medicine and Bioinformatics domain.
- You have the keys it needs:
HEALTHPOINT_MODE, HEALTHPOINT_API_KEY, HEALTHPOINT_BASE_URL, HEALTHPOINT_AUTH_SCHEME, HEALTHPOINT_GEO_SEARCH_MODE, HEALTHPOINT_TIMEOUT_SECS, HEALTHPOINT_EXPORT_POLICY. - You want tools like
healthpoint.diagnostic.status, healthpoint.access.notes, healthpoint.access.policy.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Other Tools and Integrations | Biology, Medicine and Bioinformatics |
| Quality signal | 89/100 · Excellent | 45/100 · Fair |
| Install command | Confirmed | Not confirmed yet |
| Transport | Local subprocess (stdio) | — |
| Auth | No auth required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | HEALTHPOINT_MODEHEALTHPOINT_API_KEYHEALTHPOINT_BASE_URLHEALTHPOINT_AUTH_SCHEMEHEALTHPOINT_GEO_SEARCH_MODEHEALTHPOINT_TIMEOUT_SECSHEALTHPOINT_EXPORT_POLICY |
| Verified owner | Verified | Community listing |
| GitHub stars | 91,289 | 1 |
| Directory activity | 39 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 9 | 10 |
| Full listing | View Git | View Healthpoint Rs |
Tools & capabilities
Git tools 9
create_entitiesCreate multiple new entities in the knowledge graphcreate_relationsCreate multiple new relations between entities in the knowledge graph. Relations should be in active voiceadd_observationsAdd new observations to existing entities in the knowledge graphdelete_entitiesDelete multiple entities and their associated relations from the knowledge graphdelete_observationsDelete specific observations from entities in the knowledge graphdelete_relationsDelete multiple relations from the knowledge graphread_graphRead the entire knowledge graphsearch_nodesSearch for nodes in the knowledge graph based on a queryopen_nodesOpen specific nodes in the knowledge graph by their names
Healthpoint Rs tools 10
healthpoint.diagnostic.statusShow redacted runtime mode, configuration, and readiness.healthpoint.access.notesShow non-secret endpoint, auth, and documentation notes.healthpoint.access.policyShow the conservative access/export policy before reuse.healthpoint.services.searchSearch HealthcareService records by text, codes, region filters, cursor, and limit.healthpoint.services.search_snomedSearch HealthcareService records by SNOMED CT code in type, category, or specialty.healthpoint.services.nearbyFind HealthcareService records near a latitude/longitude point.healthpoint.service.getRead one HealthcareService by FHIR id.healthpoint.location.getRead one Location by FHIR id.healthpoint.organization.getRead one Organization by FHIR id.healthpoint.resource.readRead a supported `healthpoint://` resource URI.
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.
Git
{
"mcpServers": {
"git": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-memory"
]
}
}
}
Healthpoint Rs
No confirmed install command for Healthpoint Rs yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
Git is categorized under Other Tools and Integrations and uses a local stdio subprocess. Healthpoint Rs belongs to Biology, Medicine and Bioinformatics and uses an install path we have not confirmed yet. Pick Git for other tools and integrations work and Healthpoint Rs for biology, medicine and 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. Healthpoint Rs has no confirmed install command yet — follow its own setup instructions.
Git is listed as free. Auth: no auth required. Healthpoint Rs 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 git and healthpoint-rs as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Git has a quality signal of 89/100 (Excellent) with 39 views, 0 installs and 91,289 GitHub stars. Healthpoint Rs has 45/100 (Fair) with 0 views, 0 installs and 1 GitHub stars.