A
licenseNot graded
qualityA
maintenanceEnables looking up genes, fetching sequences, predicting variant consequences, finding orthologs, and cross-database xrefs via Ensembl REST API through MCP.
120 npm
3
Apache 2.0
VEPmcp
Related Servers
Alternatives to VEPmcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables querying Ensembl genomic data including gene lookup, sequence retrieval, homology, variation, and variant effect prediction via MCP tools.24 npmMIT
- AlicenseBqualityDmaintenanceProvides access to the Ensembl genomics REST API with 30+ tools for genomic data including gene lookup, sequence retrieval, genetic variants, cross-species homology, phenotypes, and regulatory features.2597 npmISC
- AlicenseNot gradedqualityDmaintenanceProvides access to BioThings.io APIs for comprehensive gene and variant annotations, enabling seamless integration of biological data into workflows.2,686 npm6MIT
- AlicenseAqualityAmaintenanceEnables AI-powered genomic variant analysis including variant impact prediction, regulatory element discovery, and batch variant scoring. Currently operates in mock mode as a proof-of-concept awaiting the public release of Google DeepMind's AlphaGenome API.2419 npm2MIT
- FlicenseAqualityFmaintenanceProvides interpretable variant effect predictions for 4.2 million ClinVar variants using the EVEE API. Enables searching, comparing, and analyzing genetic variants with AI-generated mechanistic interpretations and disruption profiles.618-
TDQS
A3.6/5.0
Scored across 9 tools
Disambiguation5/5
Each tool targets a distinct action and input type. The three 'get_' tools retrieve metadata, while the six 'vep_' tools annotate variants and are clearly separated by input format (HGVS, ID, region) and batching mode. No two tools overlap in purpose.
Naming Consistency5/5
Naming follows a consistent pattern: 'get_' for informational queries and 'vep_<format>_<mode>' for annotation tools. All names use snake_case and clearly convey the action and target resource, making the set predictable.
Tool Count5/5
With nine tools, the server is well-scoped for its domain. The three metadata tools and six annotation tools (covering three input formats, each with batch and single variants) provide a complete set without excessive or insufficient endpoints.
Completeness5/5
The tool set covers core VEP functionality: metadata retrieval (assembly, consequences, species) and annotation via common input formats (HGVS, identifiers, regions) with both single and batch modes. No obvious gaps exist for a standard VEP annotation server.
Maintenance
ActivityInactive
ResponsivenessNo issues