Search arXiv papers, download full text, semantic search, citation graphs, and alerts via MCP.
Catalyst evidence graph is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Findings on what compounds and supplements do in the body, with evidence strength, quote and paper.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http catalyst-evidence-graph-mcp https://catalystproject.ai/mcp
# 2 — ask your agent for something these tools do
# find_evidence, search_nodes, get_findings and 4 more
Catalyst evidence graph costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http catalyst-evidence-graph-mcp https://catalystproject.ai/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
7 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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"). Pass the substance (or an outcome such as "sleep") as query, and the specific effect, if there is one, as about. One call resolves the name to the nod
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | The substance or outcome the person asked about, in their words (e.g. "magnesium", "vitamin D", "sleep"), or a node id. |
| about | string | no | Optional: the specific effect or outcome asked about (e.g. "sleep", "blood pressure"), or a node id. |
| evidence_strength | string | no | Optional floor: only findings with at least this evidence strength. |
| limit | integer | no | Findings to return, strongest evidence first. |
| detail | string | no | brief (default): each finding with its claim, evidence strength, design, population, dose, quote, paper, permalink and a ready-to-quote citation. full: every recorded field. |
Search the Catalyst evidence graph by name or synonym (for example "magnesium", "vitamin D", "sleep", "creatine"). Returns node ids to pass to get_findings or get_relations. Each hit says how many findings it has, and hits with findings come first, so the first hit with findings above 0 is usually the one to use. It finds things; it does not say anything about them.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | A name, synonym or phrase. |
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. summary lists everything the node has findings about, one row each, across ALL its findings and not only the rows returned. Use it to see what is covered, then pass about (an id from summary, or words such as "sleep") to get
| Parameter | Type | Required | Notes |
|---|---|---|---|
| node_id | string | yes | A node id from search_nodes, e.g. CHEBI:16919 (creatine). |
| limit | integer | no | Findings to return, strongest evidence first. |
| about | string | no | Optional: only findings about this, as an id from summary (e.g. CAT:outcome/sleep-onset-latency) or words in its name (e.g. "sleep"). |
| evidence_strength | string | no | Optional floor: return only findings with at least this evidence strength. |
| detail | string | no | brief (default): each finding with its claim, evidence strength, design, population, dose, quote, paper, permalink and a ready-to-quote citation. full: every recorded field. |
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. Use it to explain why the evidence behind a finding is as strong as it is, from evidence_strength_reasons rather t
| Parameter | Type | Required | Notes |
|---|---|---|---|
| finding_id | string | yes | A 26-character finding id, from a permalink or get_findings. |
What public reference databases (Reactome, UniProt, Rhea, ChEBI and others) record about a node: transporters, enzymes, pathways, expression. Every row is assertion_class 'inferred': a hypothesis about how a compound could act, not a result anyone measured in people. Present these as possible mechanisms and never as effects. For effects, use get_findings.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| node_id | string | yes | A node id from search_nodes, e.g. CHEBI:16919 (creatine). |
| predicate | string | no | Limit to one relation type, e.g. transports. |
| limit | integer | no | — |
| offset | integer | no | — |
Biochemical reactions from Rhea and Human-GEM that a compound is a substrate or product of, or that a protein catalyses or transports. Every row is assertion_class 'inferred': a reaction two public databases record, not a result anyone measured in a person. Present these as known biochemistry, never as an effect a compound has, and never as a recommendation. For effects, use get_findings. A compou
| Parameter | Type | Required | Notes |
|---|---|---|---|
| node_id | string | yes | A node id from search_nodes, e.g. CHEBI:16919 (creatine). |
| limit | integer | no | — |
| offset | integer | no | — |
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. Every route is assertion_class 'inferred': a hypothesis drawn from reference databases, never a measured or reported effect. Present it as known biochemical connectivity — never as an effect, a recommendation, o
| Parameter | Type | Required | Notes |
|---|---|---|---|
| from_id | string | yes | The compound to start from. |
| to_id | string | no | A target compound. Omit to list everything from_id reaches. |
| depth | integer | no | Longest route to consider, in reaction steps (1-3). |
| limit | integer | no | Rows to return when to_id is omitted. |
| offset | integer | no | — |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Catalyst evidence graph or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither: the repository linked on this page is where this record was collected from, not a copy of what the address serves, so it is not graded in its place. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 0.2.0.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Catalyst evidence graph can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.