EMBL-EBI MCP Server
Related Servers
Alternatives to EMBL-EBI MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceThis server provides access to InterPro protein family, domain, and functional-site classification data from EBI. It allows querying protein annotations through natural language or direct tool calls.522 npmMIT
- FlicenseNot gradedqualityCmaintenanceProvides protein family, domain, and functional annotation using InterProScan, supporting local or API backends.-
- AlicenseBqualityDmaintenanceProvides seamless access to UniProtKB protein database, enabling queries for protein entries, sequences, Gene Ontology annotations, full-text search, and ID mapping across 200+ database types.52MIT
- AlicenseNot gradedqualityBmaintenanceProvides access to UniProt protein sequence and function knowledge base, enabling search and retrieval of protein entries, proteomes, taxonomy, and feature annotations.197 npmMIT
- AlicenseNot gradedqualityAmaintenanceSearch UniProtKB by protein function, fetch curated records, map IDs across databases, and pull reference proteomes, taxonomy, and sequences via MCP. Supports both STDIO and Streamable HTTP transports.204 npm2Apache 2.0
- AlicenseNot gradedqualityAmaintenanceEnables agents to search protein family, domain, and functional-site entries, read entry metadata and clan relationships, map a UniProt protein's annotations to residue coordinates, and find proteins carrying a given signature. Runs over STDIO or Streamable HTTP with no credentials required.739 npm1Apache 2.0
TDQS
Scored across 1 tool
Only one tool exists, so there is no possibility of confusion between tools. The methods within the tool are clearly distinct and cover separate domains or operations.
The method names follow a consistent verb_noun pattern (e.g., search_interpro, get_protein_features), but the tool name 'embl_data' is a generic noun that does not convey an action or purpose, resulting in minor inconsistency.
With only a single tool for a wide range of bioinformatics APIs, the tool surface is too thin. The multiple methods effectively act as sub-tools, but consolidating them into one tool makes the server feel under-scoped and reduces usability.
The methods cover essential read operations (search and retrieval) for major EMBL-EBI resources like InterPro, Pfam, UniProt features, and NCBI taxonomy. Minor gaps exist (e.g., no direct method to fetch a Pfam entry by ID), but the core querying needs are addressed.