Alphafold Sovereign M… vs Opdstar Nhi MCP | AllMCPs
Side-by-Side Model Context Protocol Comparison
Alphafold Sovereign MCP vs Opdstar Nhi MCP
In-depth architectural comparison of the Alphafold Sovereign MCP and Opdstar Nhi MCP 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
Alphafold Sovereign MCP
Biology, Medicine and Bioinformatics · Local stdio
Quality: 61/100 (Good) | Auth: API Key required
Opdstar Nhi MCP
Biology, Medicine and Bioinformatics · Local stdio
Quality: 63/100 (Good) | Auth: No auth required
Verdict Summary: Choose Alphafold Sovereign MCP if you need specialized Biology, Medicine and Bioinformatics tools running via a local process. Choose Opdstar Nhi MCP if your workspace requires Biology, Medicine and Bioinformatics integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Alphafold Sovereign MCP when:
You need dedicated capabilities in the Biology, Medicine and Bioinformatics domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (Free / Open Source).
AlphaFold MCP server integrating AlphaFold DB with eight additional public biomedical data sources, backed by a local SQLite knowledge graph for structural-confidence, variant, disease/phenotype, drug-target, and orthology workflows. uvx alphafold-sovereign-mcp
Taiwan's first public MCP server for National Health Insurance (NHI) data — 234 rejection codes, 1,497 ICD-10→procedure mappings across 20 specialties, audit indicators (008/014/027/P043), and semantic wiki search over 8,232 chunks of official NHI documentation. Powered by OPDSTAR. Install: npx @opdstar/nhi-mcp.
Tools & Capabilities Breakdown
Alphafold Sovereign MCP Tools (30)
lookup_disease
Retrieve a disease record from the MONDO unified disease ontology.
Returns the canonical MONDO entry with:
- Disease name, definition, synonyms
- ICD-10 / ICD-11 codes (for clinical coding / EHR integration)
- OMIM, Orphanet, MeSH, DOID cross-references
- Immediate parent and child terms in the MONDO hierarchy
Example: ``lookup_disease(mondo_id='MONDO:0004995')``
returns the record for coronary artery disease.
search_diseases
Search for diseases by name or keyword using the MONDO ontology.
Returns a ranked list of matching diseases with MONDO IDs and
cross-references. Useful for resolving a clinical term to a
canonical identifier before querying targets or phenotypes.
Example: ``search_diseases(query='breast cancer', limit=5)``
lookup_phenotype
Retrieve an HPO phenotype term with associated disease annotations.
Returns:
- Phenotype label, definition, synonyms
- Diseases annotated with this phenotype (from HPO + OMIM + Orphanet)
- Parent phenotype terms
Example: ``lookup_phenotype(hpo_id='HP:0001250')``
returns the Seizure phenotype with ~400 associated diseases.
get_gene_phenotype_profile
Return all HPO phenotypes associated with a gene, plus gnomAD constraint.
Useful for understanding the clinical consequences of variants in a gene
before requesting structural context.
Returns:
- HPO phenotypes linked to the gene (from HPO association database)
- gnomAD LOEUF / pLI constraint scores
- Interpretation of constraint (haploinsufficient / tolerant / moderate)
Example: ``get_gene_phenotype_profile(gene_symbol='SCN1A')``
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).
Alphafold Sovereign MCP is categorized under Biology, Medicine and Bioinformatics and uses a local stdio subprocess. In contrast, Opdstar Nhi MCP belongs to Biology, Medicine and Bioinformatics using local stdio subprocess. Select Alphafold Sovereign MCP when you need capabilities focused on biology, medicine and bioinformatics and Opdstar Nhi MCP when you require tools for biology, medicine and bioinformatics.
Return top protein targets for a disease with Open Targets evidence scores.
Evidence score breakdown (0–1 per data type):
- ``genetic_association``: GWAS + rare-variant signals
- ``somatic_mutation``: Cancer somatic variant evidence
- ``known_drug``: Approved or clinical-stage drugs
- ``affected_pathway``: Pathway membership (Reactome, SIGNOR)
- ``literature``: Text-mining evidence (Europe PMC)
- ``animal_model``: Knockout / model organism phenotypes
- ``rna_expression``: Differential expression evidence
Example: ``get_disease_targets(disease_id='MONDO:0007254', limit=15)``
returns top 15 targets for breast carcinoma.
get_target_diseases
Return all diseases associated with a protein target via Open Targets.
Accepts a UniProt accession and returns the full disease landscape
for that target — essential for target-validation and indication-expansion.
Example: ``get_target_diseases(uniprot_id='P04637')``
returns all diseases associated with TP53 / p53.
get_common_disease_targets
Profile the top drug targets for a curated set of common diseases in one call.
Use this for a fast landscape scan across a whole disease area: given a
``category`` (e.g. 'oncology'), it looks up the curated MONDO diseases in that
category and returns each one's top Open Targets evidence-scored targets, in
parallel. To profile a single disease you already have a MONDO ID for, use
``get_disease_targets`` instead — this tool is its category-level,
multi-disease counterpart and does not accept a raw MONDO ID.
Queries Open Targets live. Returns a JSON string with the ``category``, the
number of diseases profiled, and a ``profile`` object mapping each disease to
its MONDO ID and top targets (per-disease errors are reported inline, not
raised). Returns a JSON error object listing the valid values when the category
— or a ``disease_name`` filter within it — is not recognised.
triage_variant_3d
Comprehensive clinical triage for a missense variant.
Fuses the upstream signals this tool currently wires into a single
prioritised report:
1. **Pathogenicity** — ClinVar interpretation + review status. The
``alphamissense_score`` / ``alphamissense_interpretation`` fields
are always ``null`` / "Not available" here: AlphaMissense is not
wired into this tool. For an AlphaMissense pathogenicity score use
``generate_variant_clinical_report``.
2. **Population genetics** — gnomAD LOEUF / pLI gene-constraint
scores. Per-variant allele frequencies and the per-ancestry
breakdown are not wired into this tool.
3. **Disease associations** — a placeholder note pointing at
``get_target_diseases()``; the Open Targets / MONDO traversal is
a roadmap (Wave-3) item.
4. **Structural context** — a text note pointing at
``analyze_structural_confidence`` (resolve the gene to a UniProt
accession first); the AlphaFold pLDDT / PAE join into this report
is a roadmap (Wave-3) item.
Returns a ``pathogenicity_tier``: HIGH / MEDIUM / LOW / UNKNOWN
(derived from ClinVar; the AlphaMissense input is always absent here).
Example: ``triage_variant_3d(hgvs='BRCA1:c.181T>G')``
phenotype_to_structures
Map a clinical phenotype to the protein structures of its disease targets.
Pipeline:
1. Resolve HPO term → associated diseases
2. For each disease → top protein targets (Open Targets)
3. For each target → UniProt ID (for AlphaFold retrieval)
Use the returned UniProt IDs with ``analyze_structural_confidence``
to retrieve AlphaFold structural confidence (pLDDT/PAE).
Example: ``phenotype_to_structures(hpo_id='HP:0002621')``
maps Atherosclerosis → disease targets → UniProt IDs.
get_orphan_disease_atlas
Map an Orphanet rare disease to its MONDO record, HPO phenotypes, and protein targets.
Rare / orphan diseases are often under-studied because their small
patient populations make large trials impractical. This tool aggregates
the available structural and clinical intelligence into one report to
accelerate research.
Returns:
- MONDO record with ICD-10 coding
- HPO phenotype profile of the disease
- Open Targets protein target evidence scores
- UniProt IDs for AlphaFold structural retrieval
Example: ``get_orphan_disease_atlas(orphanet_id='79318')``
returns the Gaucher disease atlas.
compare_disease_target_overlap
Compare the protein target landscapes of two diseases.
Identifies shared and unique targets between two diseases —
a key analysis for drug repurposing, identifying shared mechanisms,
and understanding comorbidity.
Returns:
- Shared targets (present in both disease target sets)
- Unique to Disease A / Disease B
- Jaccard similarity score of target sets
Example: ``compare_disease_target_overlap(
mondo_id_a='MONDO:0004975', # Alzheimer disease
mondo_id_b='MONDO:0005180', # Parkinson disease
)``
resolve_icd10_to_mondo
Resolve an ICD-10 clinical code to MONDO disease ontology terms.
Enables integration between clinical / EHR data (which uses ICD-10)
and the research-grade MONDO ontology used by Open Targets, HPO, and
this MCP.
Example: ``resolve_icd10_to_mondo(icd10_code='I21.0')``
maps ST-elevation MI (ICD-10) to MONDO coronary disease terms.
+18 more tools listed on main page
Opdstar Nhi MCP Tools (27)
lookup_rejection_code
Look up a single Taiwan NHI rejection code (5-character format `NNNNL` — 4 digits + 1 uppercase letter A/B/C/..., e.g. '0317A', '0338A', '0114A'). Returns severity (low / medium / high), category (00 診療品質 · 01 病歷紀錄 · 02 基本診療 · 03 藥品特材 · 04 手術處置 · 05 檢查檢驗 · 06 論病例計酬 · 07 復健精神 · 08 其他 · 09 法令 — first two digits encode the category), and the official Chinese description from 健保署 專業審查不予支付理由代碼. Returns a not-found message (not an error) if the code does not exist. **Use when** an agent encounters a known rejection code in a notice or claim response and needs the human-readable explanation, or when triaging which category a code belongs to. **Typical follow-up**: call `get_drug_rules({rejection_code})` if the code is in category 03 (藥品特材) to surface the drug rule behind the rejection; call `search_audit_guidelines({query: <code>})` for codes in 04 / 05 to read the underlying audit-clause text; call `count_appeal_precedents_for_rejection_code({rejection_code})` to gauge whether disputes for this code are commonly successful. **Don't use** to enumerate codes by category — call `get_rejection_code_category({category})` instead. **Reference only** — the official 健保署 code list is authoritative. Curated by OPDSTAR (https://opdstar.com).
get_procedures_for_icd
Given a Taiwan ICD-10 code and a medical specialty, return the NHI procedure codes plausibly applicable to that diagnosis within that specialty. Each result includes the procedure code, Chinese name, English name, nhi_points (payment points), and audit_notes (specialty-specific review caveats and risk hints). Results are ordered by curated relevance (most commonly applied codes first), capped at `limit` (default 10, max 20). Returns an empty list (not an error) when no curated mapping exists for the given (icd10, specialty) pair — this is common because the mapping is intentionally conservative. **Use when** an agent is drafting SOAP and needs a starting set of procedure codes for the diagnosis within the clinician's specialty context — e.g. dermatologist with `L30.9` (chronic eczema) needs candidate procedure codes. **Typical follow-up**: for each candidate code, call `lookup_fee_code({q: <code>})` to confirm current points and effective dates, and `lookup_audit_clauses_for_procedure({procedure_code})` to surface any audit-clause caveats. **Don't use** as a billing source of truth — the original NHI fee schedule has no ICD field, this is a curated, intentionally conservative mapping that prefers false negatives over false positives; for the canonical fee-schedule entry of a known code, call `lookup_fee_code`. **Reference only** — final code selection remains the clinician's responsibility. Curated by OPDSTAR (https://opdstar.com).
get_indicator
Look up a single Taiwan NHI prescribing-pattern indicator. These are short codes (numeric, or 'P'-prefixed) that encode common over-prescribing patterns such as antibiotic-on-URI, multi-drug co-prescribing, or duration limits. Returns the indicator name, the threshold (e.g. '7-day URI episode'), applicable drugs / diagnoses, and the compliance meaning. Returns a not-found message (not an error) if the code does not exist. **Use when** an agent needs the human-readable explanation for a specific indicator code referenced during a SOAP review or audit response — e.g. an audit notice cites an indicator and the agent needs to surface what it monitors and why a prescription tripped it. **Typical follow-up**: call `get_drug_rules({rejection_code})` with the indicator's downstream rejection code to read the formal payment rule, or `search_audit_guidelines({query})` to read related audit-clause text. **Don't use** for the official 分析審查不予支付指標 (percentage-cap audit) list — that's a different system — call `lookup_audit_indicator` instead. **Reference only** — thresholds and applicable lists reflect published guidance and may change with each NHI release; agents should re-read the indicator each session rather than caching values across sessions. Curated by OPDSTAR (https://opdstar.com).
search_nhi_wiki
Search across Taiwan's official NHI knowledge base (健保署全球資訊網) for natural-language background questions. Covers 9 categories: audit (審查 — review rules / rejection grounds), drugs (藥品特材 — formulary, payment limits), fees (費用 — copay, premiums, contribution), plans (醫療計畫 — disease-management programs), services (醫療服務 — covered benefits), insurance (投保 — enrollment), forms (表單 — applications), records (紀錄 — documentation rules), admin (行政 — contracting, accreditation). Returns up to 10 ranked excerpts (most relevant first); each result includes title, content snippet, source URL, and category tag. Returns an empty list (not an error) when the query has no matches. **Use when** an agent needs broad NHI policy background not tied to a specific code — e.g. '慢性病連續處方箋天數上限' / 'how does balance billing work for orthodontics' / 'what are the rules for telemedicine reimbursement'. **Typical follow-up**: when an excerpt mentions a specific code (e.g. '0317A', '00101B'), call the appropriate code-specific tool (`lookup_rejection_code`, `lookup_fee_code`) for the canonical entry. **Don't use** when you already know a specific rejection code, procedure code, drug name, or audit-clause topic — those have dedicated tools that return structured fields rather than excerpts. **Reference only** — official 健保署 publications are authoritative; ranked excerpts may lag the latest revision and the snippet is not the full document. Curated by OPDSTAR (https://opdstar.com).
search_nhi_interpretations
Search Taiwan's official NHI administrative interpretations (健保署行政函釋 / 函令) — the binding 公告 and 解釋函 issued by the National Health Insurance Administration that clarify how payment rules, drug-formulary provisions, special-material coverage, and review policy apply in practice. Each result returns the official document number (字號), issue date, 主旨 (subject), a content excerpt, and the source URL on the government law portal. Returns up to 10 ranked excerpts (most relevant first); returns an empty list (not an error) when nothing matches. **Use when** a question turns on an official ruling rather than a code definition — e.g. '函釋怎麼說人工水晶體的給付規定' / 'is there an interpretation on continuous-prescription day limits' — or when the user cites a 函釋 文號 directly (e.g. 健保審字第 1090017813 號). **Don't use** when you already have a specific rejection code, fee code, or drug name — those have dedicated lookup tools (`lookup_rejection_code`, `lookup_fee_code`, `lookup_drug`). **Reference only** — the official 健保署 / 衛福部 publication is authoritative; an excerpt may lag the latest revision and is not the full document, so open the source URL for the binding text. Curated by OPDSTAR (https://opdstar.com).
get_drug_rules
Look up Taiwan NHI drug payment rules (藥品給付規定) — when a drug class is / isn't reimbursable, with severity and source citation. Filter by `specialty`, `rejection_code`, or `drug_category_query` (at least one required). **Use when** an agent is checking whether a drug choice will trigger a rejection before submission, or wants to read the rule behind a known rejection code. **Don't use** to identify a specific drug (brand / generic / strength) — call `lookup_drug` instead; for the underlying audit clauses, use `lookup_audit_clauses_for_procedure` or `lookup_audit_clauses_for_specialty`. **Reference only** — official 健保藥品給付規定 is authoritative; curated subset, not exhaustive. Curated by OPDSTAR (https://opdstar.com).
get_safe_phrases
Preview which documentation scenarios have OPDSTAR-curated NHI-safe phrasing patterns for a given specialty (e.g. dermatology + 抗生素) — returns scenario name, high-risk wording to avoid, the key difference, and the first sentence of the safe-phrasing example. Up to 5 scenarios per call. **Use when** an agent is helping draft SOAP wording and needs to flag risky phrasing before submission. **Don't use** to retrieve full ready-to-copy templates (full library is part of the paid OPDSTAR product — link the user to opdstar.com); for the underlying audit rule that motivates a safe phrase, call `search_audit_guidelines`. **Reference only** — phrasing patterns reflect curated review experience, not formal NHI directives. Curated by OPDSTAR (https://opdstar.com).
search_audit_guidelines
Free-text search over Taiwan NHI 審查注意事項 rules — returns reason + suggestion summaries (first sentence only) for up to 10 rules matching a keyword (Traditional Chinese or English). **Use when** an agent is exploring whether any audit rule covers a topic (e.g. '抗生素', '檢查頻率', '慢性病處方') without knowing a specific code. **Don't use** for clauses tied to a known procedure code — call `lookup_audit_clauses_for_procedure` instead. Full SOAP example templates and detailed reasoning are part of the paid OPDSTAR product. **Reference only** — official 健保署 審查注意事項 is authoritative; results are previews. Curated by OPDSTAR (https://opdstar.com).
get_rejection_code_category
Browse Taiwan NHI rejection codes by category (00-09) for discovery — returns code, severity, and short description, up to 50 per call. Categories: 00 診療品質 · 01 病歷紀錄 · 02 基本診療 · 03 藥品特材 · 04 手術處置 · 05 檢查檢驗 · 06 論病例計酬 · 07 復健精神 · 08 其他 · 09 法令. **Use when** an agent needs to enumerate all rejection codes within a workflow domain (e.g. all surgery-handling codes). **Don't use** to look up a known specific code — call `lookup_rejection_code` instead. **Reference only** — official 健保署 不予支付理由代碼 is authoritative. Curated by OPDSTAR (https://opdstar.com).
lookup_drug
Look up the active Taiwan NHI drug catalog by generic name, brand name, NHI drug code, or alias — returns up to 10 matches with strength, dosage form, route, ATC code, therapeutic class, and brand list. **Use when** an agent needs to identify or disambiguate a drug before recommending dosage / formulation in a SOAP draft. **Don't use** to look up payment / reimbursement rules for the drug — call `get_drug_rules` instead; for an audit clause referencing the drug, call `search_audit_guidelines`. **Reference only** — official 健保署 藥品給付項目及支付標準 is authoritative; the catalog is a working snapshot. Curated by OPDSTAR (https://opdstar.com).
lookup_fee_code
Look up the Taiwan NHI fee schedule (全民健康保險醫療服務給付項目及支付標準, current effective edition). Search by exact code (e.g. '00101B', 'P15001') or by Chinese / English name (e.g. '門診診察', 'ICU') — returns code, points, effective dates, and audit notes (truncated to 600 chars). Use `category` prefix to scope ('00' 基本診療, '06' 手術, 'P1' 病例計酬, 'N2' 護理). **Use when** an agent needs the canonical fee entry for a known procedure code, or wants to discover codes by name. **Don't use** for drugs (call `lookup_drug`) or for ICD-10 → procedure suggestions (call `get_procedures_for_icd`). The optional `icd` filter applies an OPDSTAR-curated mapping that is intentionally sparse (the original NHI data has no ICD field) — most codes will return no result with `icd` active. **Reference only** — official 健保署 支付標準 is authoritative. Curated by OPDSTAR (https://opdstar.com).
lookup_audit_clauses_for_procedure
Find Taiwan NHI 審查注意事項 clauses that reference a specific procedure code (e.g. '00101B', '51017C') — each result indicates whether the clause carries an amount limit, frequency rule, or indication restriction (critical signals for rejection-risk assessment). Returns clause summary, specialty, and risk flags. **Use when** an agent has a candidate procedure code and needs to surface the audit context attached to it. **Don't use** for the procedure's fee-schedule entry (points / effective dates) — call `lookup_fee_code`; for browsing all clauses within a specialty, call `lookup_audit_clauses_for_specialty`. **Reference only** — clause summaries are first-sentence previews; official 健保署 審查注意事項 is the source of truth. Curated by OPDSTAR (https://opdstar.com).