INDIVIDUAL MCP TOOL

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.

catalystproject.ainone authenticationAvailability not checked

LIVE ENDPOINT

https://catalystproject.ai/mcp

No auth detected

Connect to this endpoint to inspect the live schema for get_finding and invoke it with your own arguments.

Indexed input schema

{}

Risk classification

Inferred read-only · medium confidence · heuristic, not a guarantee.

No write-capable action terms were found; this is not proof that invocation has no side effects.

Parent server

catalystproject.ai

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.

Related tools

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").
search_nodes — Search the Catalyst evidence graph by name or synonym (for example "magnesium", "vitamin D", "sleep", "creatine").
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.
get_relations — What public reference databases (Reactome, UniProt, Rhea, ChEBI and others) record about a node: transporters, enzymes, pathways, expression.
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.
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.