Databases

catalystproject.ai

An MCP server that exposes the Catalyst evidence graph for querying supplements, nutrients, drugs, foods, and compounds, their health effects, study findings, and reference database relations.

1 endpoint7 known toolsFirst detected October 5, 2026Last detected October 18, 2026

ENDPOINT 1

https://catalystproject.ai/mcp

No auth detected

MCP server metadata

Name: catalyst-evidence-graph
Version: 0.2.0

Capabilities

tools.listChangedresources.listChangedprompts.listChanged

Server instructions

Catalyst is building computational infrastructure for human biology, starting with a provenance-aware knowledge graph of biological entities and biomedical findings. The current MCP interface exposes graph search, study findings with their evidence strength, and biological relationships; a research engine and physiological simulation are roadmap capabilities. For a question about what a substance does, or whether it affects something, start with find_evidence: one call resolves the name and returns the findings. Use search_nodes and get_findings to browse, and get_finding to explain one finding. Every evidence strength here is computed from the study behind it (design, population, replication), never written by hand. It is one of five named levels: strong, moderate, limited, very_limited, insufficient. An evidence strength describes how well the evidence supports a finding. It is not a recommendation to take anything, and it is not medical advice. Present each finding with its evidence strength in words, and link its permalink so the reader can check the quote and the paper. A row whose assertion_class is 'inferred' is a hypothesis drawn from a reference database, not a reported result: call it a hypothesis. Do not merge findings into a stronger claim than the strongest evidence supports, and say so when findings contradict each other.

Known tools 7

find_evidence

Use this when someone asks what a supplement, nutrient, drug, food compound or plant does in the body, or whether it affects something specific (for example "does magnesium help sleep?", "what is creatine shown to do?", "omega-3 and triglycerides").

Inferred read-only

search_nodes

Search the Catalyst evidence graph by name or synonym (for example "magnesium", "vitamin D", "sleep", "creatine").

Inferred read-only

get_findings

The curated study findings for one node: for a compound, organism or material, what it has been shown to affect; for an outcome, which compounds have been studied against it.

Inferred read-only

get_finding

One finding by its id (the last part of a permalink, /e/{id}): the claim, its evidence strength and what that level means, the verbatim quote, the study design and the paper, and evidence_strength_reasons: each rule that set the level, in order, and what the assessment does not weigh.

Inferred read-only

get_relations

What public reference databases (Reactome, UniProt, Rhea, ChEBI and others) record about a node: transporters, enzymes, pathways, expression.

Inferred read-only

get_reactions

Biochemical reactions from Rhea and Human-GEM that a compound is a substrate or product of, or that a protein catalyses or transports.

Inferred read-only

reach

Breadth-first reachability through the reactions two public databases (Rhea, Human-GEM) record: what a compound could become, and through which reactions and enzymes, within up to 3 steps.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.catalyst-evidence-graph]
url = "https://catalystproject.ai/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "catalyst-evidence-graph": {
      "type": "http",
      "url": "https://catalystproject.ai/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: catalyst-evidence-graph
Remote MCP URL: https://catalystproject.ai/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "catalyst-evidence-graph": {
      "url": "https://catalystproject.ai/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "catalyst-evidence-graph": {
      "type": "http",
      "url": "https://catalystproject.ai/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "catalyst-evidence-graph",
  "transport": "streamable-http",
  "url": "https://catalystproject.ai/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.