Reactome MCP Server

Related Servers

Alternatives to Reactome MCP Server

No user-submitted related servers found.

Related Servers

io.github.marcorusc/NeKoofficial
Bioinformatics Biology & Medicine
marcorusc
A
license
Not graded
quality
A
maintenance
Enables building and analyzing signalling networks from interaction databases through a Model Context Protocol server.
Updated 3 days ago (2026-09-10 05:54 UTC)
18
MIT
biothings-mcp
Bioinformatics Biology & Medicine
longevity-genie
A
license
A
quality
F
maintenance
Provides a Model Context Protocol server for accessing and querying biomedical data from BioThings services, including gene, variant, chemical, and taxon annotations.
Updated 10 months ago (2025-11-03 20:05 UTC)
19
34
MIT
mcp-omics
Bioinformatics Biology & Medicine Research & Data
colbyford
A
license
Not graded
quality
D
maintenance
A Model Context Protocol server that enables retrieval of -omics data from sources like PDB, ChEMBL, UniProt, PubChem, and HUGO.
Updated a year ago (2025-07-13 01:22 UTC)
5
GPL 3.0
BioOntology MCP Server
Bioinformatics Research & Data Biology & Medicine
Augmented-Nature
F
license
B
quality
D
maintenance
A production-ready Model Context Protocol (MCP) server that provides comprehensive access to the BioOntology API for searching, annotating, and exploring over 1,200 biological ontologies.
Updated 9 months ago (2025-12-21 10:10 UTC)
10
9
-
Reexpress MCP Serverofficial
RAG Systems Code Execution Developer Tools
ReexpressAI
A
license
Not graded
quality
A
maintenance
Reexpress Model-Context-Protocol (MCP) Server
Updated 10 days ago (2026-09-02 22:53 UTC)
9
Apache 2.0
Biomart MCP
Bioinformatics Databases Search
jzinno
A
license
A
quality
D
maintenance
A Model Context Protocol server that interfaces with Biomart databases, allowing models to discover biological datasets, explore attributes/filters, retrieve biological data, and translate between different biological identifiers.
Updated a year ago (2025-05-21 20:53 UTC)
8
8
MIT

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A3.5/5.0

Scored 2026-04-18 09:30 across 8 tools

Disambiguation5/5

Every tool has a clearly distinct purpose with no ambiguity. For example, find_pathways_by_disease and find_pathways_by_gene target different entry points, while get_pathway_details, get_pathway_hierarchy, get_pathway_participants, and get_pathway_reactions each focus on specific aspects of pathway information. The descriptions reinforce these distinctions, making misselection unlikely.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern with snake_case, such as find_pathways_by_disease, get_pathway_details, and search_pathways. The naming is predictable and readable throughout the set, with no deviations in style or convention.

Tool Count5/5

With 8 tools, the count is well-scoped for a biological pathway server. Each tool earns its place by covering distinct operations like searching, retrieving details, and analyzing components, without being overly sparse or bloated. This aligns with typical MCP server ranges of 3-15 tools.

Completeness5/5

The tool surface provides complete coverage for querying and exploring biological pathways. It includes search (search_pathways, find_pathways_by_disease/gene), retrieval (get_pathway_details, get_pathway_hierarchy), and analysis (get_pathway_participants, get_pathway_reactions, get_protein_interactions), with no obvious gaps that would cause agent failures in this domain.