Luogu MCP Server vs Mydisease — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Luogu MCP Server vs Mydisease
In-depth architectural comparison of the Luogu MCP Server 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
Luogu MCP Server
Developer Tools · Local stdio
Quality: 52/100 (Good) | Auth: No auth required
Mydisease
Developer Tools · Local stdio
Quality: 40/100 (Fair) | Auth: No auth required
Verdict Summary: Choose Luogu MCP Server 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?
Choose Luogu MCP Server 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).
Luogu MCP Server is categorized under Developer Tools and uses a local stdio subprocess. In contrast, Mydisease belongs to Developer Tools using local stdio subprocess. Select Luogu MCP Server when you need capabilities focused on developer tools and Mydisease when you require tools for developer tools.
Find topic practice problems using aliases, tag ids, deduplication, and match reasons.
luogu_search_problem_sets
Search Luogu training/problem sets by keyword. Supports `type: "all"
luogu_fetch_problem_set
Fetch one Luogu training/problem set and problem summaries by id.
luogu_recommend_problems
Return seed recommendations from a topic or student pain point.
luogu_get_user_profile
Fetch public Luogu user profile data by uid.
luogu_get_capabilities
Report which LeetCode-style route features are available, auth-required, or planned.
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.