Side-by-Side Model Context Protocol Comparison
Mydisease vs Data Providence
In-depth architectural comparison of the Mydisease and Data Providence MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Mydisease
Developer Tools · Local stdio
Quality: 40/100 (Fair) | Auth: No auth required
Data Providence
Developer Tools · Local stdio
Quality: 44/100 (Fair) | Auth: No auth required
Verdict Summary: Choose Mydisease if you need specialized Developer Tools tools running via a local process. Choose Data Providence if your workspace requires Developer Tools integration with local subprocess execution. Both servers can be configured concurrently in your client's
mcpServers manifest.Which MCP Server Should You Choose?
M
Choose Mydisease when:
- You need dedicated capabilities in the Developer Tools domain.
- You prefer local stdio subprocess transport architecture.
- Your security boundary fits: No auth required (Free / Open Source).
- Primary tools included: query, disease, metadata.
D
Choose Data Providence when:
- You need dedicated capabilities in the Developer Tools domain.
- You prefer local stdio subprocess transport architecture.
- Your security boundary fits: No auth required (Free / Open Source).
- Primary tools included: datasets, query, metadata.
Feature & Specification Comparison
Tools & Capabilities Breakdown
Mydisease Tools (3)
query
Search MyDisease.info for diseases by free-text name or fielded query. Returns matching hits, each keyed by a MONDO disease id (e.g. "MONDO:0015967") with the best-matching ontology and annotation keys. Use this to resolve a disease name to canonical ontology ids before calling the "disease" tool.…
disease
Fetch the full aggregated annotation object for a single disease id. Accepts MONDO ("MONDO:0015967"), DOID ("DOID:9351"), OMIM ("OMIM:125853") and other supported ontology ids. Returns cross-referenced data including MONDO ontology (labels, synonyms, xrefs, parents/children), gene-disease associati…
metadata
Returns MyDisease.info build metadata: total disease document count, available annotation sources (MONDO, DOID, OMIM, DisGeNET, HPO, CTD), and their current release versions.
Data Providence Tools (3)
datasets
Search the Providence Open Data catalog of open datasets by keyword. Returns each dataset's resource_id, name, description, category and update date — pass the resource_id to query/metadata.
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Mydisease Configuration
Data Providence Configuration
Frequently Asked Questions
More alternatives to MydiseaseMore alternatives to Data ProvidenceDeveloper Tools category hubCanonical compare URL