Side-by-Side Model Context Protocol Comparison
Data Norfolk vs Mydisease
In-depth architectural comparison of the Data Norfolk and Mydisease 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
Data Norfolk
Developer Tools · Local stdio
Quality: 43/100 (Fair) | Auth: No auth required
Mydisease
Developer Tools · Local stdio
Quality: 40/100 (Fair) | Auth: No auth required
Verdict Summary: Choose Data Norfolk if you need specialized Developer Tools tools running via a local process. Choose Mydisease 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?
D
Choose Data Norfolk 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.
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.
Feature & Specification Comparison
Tools & Capabilities Breakdown
Data Norfolk Tools (3)
datasets
Search the Norfolk 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.
query
Run a Socrata SoQL query against a Norfolk Open Data dataset by resource_id (e.g. "cab7-wvn5"). Filter with where/select/group/order (SoQL clauses, without the leading $) plus limit/offset. Returns matching rows as JSON.
metadata
Get a Norfolk Open Data dataset's schema + metadata (columns, types, row count, category, last-updated) by resource_id, e.g. "cab7-wvn5".
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.…
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).
Data Norfolk Configuration
Mydisease Configuration