Catalyst evidence graph
REMOTE · CATALYSTPROJECT.AI · SCANNED OCT 10
Findings on what compounds and supplements do in the body, with evidence strength, quote and paper.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability79
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1947 tokens (~216/item across 9 items; 7 tools + 2 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
- Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage93
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 79% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
- Supports UI / widget rendering.Pass
How do I install the Catalyst evidence graph MCP server?
Catalyst evidence graph is a hosted endpoint at https://catalystproject.ai/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · catalystproject.ai
claude mcp add --transport http ai-catalystproject-evidence-graph 'https://catalystproject.ai/mcp'
{
"mcpServers": {
"ai-catalystproject-evidence-graph": {
"url": "https://catalystproject.ai/mcp"
}
}
} {
"servers": {
"ai-catalystproject-evidence-graph": {
"type": "http",
"url": "https://catalystproject.ai/mcp"
}
}
} [mcp_servers.ai-catalystproject-evidence-graph] url = "https://catalystproject.ai/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ai-catalystproject-evidence-graph": {
"type": "remote",
"url": "https://catalystproject.ai/mcp",
"enabled": true
}
}
} openclaw mcp add ai-catalystproject-evidence-graph --url 'https://catalystproject.ai/mcp' --transport streamable-http
mcp_servers:
ai-catalystproject-evidence-graph:
url: "https://catalystproject.ai/mcp" {
"McpServers": {
"ai-catalystproject-evidence-graph": {
"Transport": "http",
"Url": "https://catalystproject.ai/mcp"
}
}
} assistant mcp add ai-catalystproject-evidence-graph -t streamable-http -u 'https://catalystproject.ai/mcp'
{
"mcpServers": {
"ai-catalystproject-evidence-graph": {
"type": "http",
"url": "https://catalystproject.ai/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 10 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 20. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 13. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 5 Oct 26 +3
- The server rewrote its instructions, which are the text every model session reads security
- Tool coverage: 72% → 79% ▲ functional
- Schema quality: 250 → 216 ▲ functional
- Stability: unverified → 0.03 ▲ functional
- The server now declares the “prompts” capability functional
- The server now declares the “resources” capability functional
- First check of Capabilities: pass functional
- First check of Schema quality: 100 functional
- New prompt “answer_with_evidence” functional
- New resource “evidence-card” functional
- New resource “guide” functional
- New tool “find_evidence” functional
- “get_findings” added an optional parameter “detail” cosmetic
- 4 Oct 26 71
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 10 Oct 2026 · Probed https://catalystproject.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=catalystproject.ai | CN=YR2,O=Let's Encrypt,C=US | 6 Sept 2026 | 5 Dec 2026 | RSA 2048 | SHA256-RSA | 6dc327f0f7e708c799c5f5e2467b212f6c5 |
| SANs: catalystproject.ai | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of catalystproject.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| catalystproject.ai. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' https://vercel.live; style-src 'self' 'unsafe-inline'; img-src 'self' data: blob:; font-src 'self' data:; connect-src 'self' https://*.supabase.co https://vercel.live; worker-src 'self' blob:; frame-src https://vercel.live; frame-ancestors 'none'; base-uri 'self'; form-action 'self'; object-src 'none'; upgrade-insecure-requests |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), interest-cohort=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://catalystproject.ai/mcp | Verified | 200 | |
| http (plaintext) | http://catalystproject.ai/mcp | HTTPS enforced | 308 | https://catalystproject.ai/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
find_evidence Find the evidence on a substance or a question ~339
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 node that has findings and returns them, each with its evidence strength in words, the study design, the quote, the paper, a permalink and a citation to quote as it stands. Without about, summary lists everything the node has findings about. If nothing matches, it says so: tell the person Catalyst has no findings on it rather than answering from memory as though from Catalyst. An evidence strength says how well the evidence supports a finding; it is not a recommendation.
| Name | Type | Req | Description |
|---|---|---|---|
| about | string | – | Optional: the specific effect or outcome asked about (e.g. "sleep", "blood pressure"), or a node id. |
| detail | string | – | 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. |
| evidence_strength | string | – | Optional floor: only findings with at least this evidence strength. |
| limit | integer | – | Findings to return, strongest evidence first. |
| query | string | yes | The substance or outcome the person asked about, in their words (e.g. "magnesium", "vitamin D", "sleep"), or a node id. |
No output schema declared.
No examples provided.
get_finding One finding, with its evidence strength explained ~125
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 than by guessing.
| Name | Type | Req | Description |
|---|---|---|---|
| finding_id | string | yes | A 26-character finding id, from a permalink or get_findings. |
No output schema declared.
No examples provided.
get_findings Findings about a node, with their evidence strength ~350
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 the findings on one thing. Each finding carries its evidence strength, one of five named levels from strong to insufficient (strong, moderate, limited, very_limited, insufficient), the verbatim sentence it was drawn from, the paper, the population and dose, and a permalink. An evidence strength says how well the evidence supports the finding; it is not a recommendation. Always give the evidence strength with the claim, and link the permalink. An empty list means nothing has been curated yet, not that the compound does nothing.
| Name | Type | Req | Description |
|---|---|---|---|
| about | string | – | 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"). |
| detail | string | – | 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. |
| evidence_strength | string | – | Optional floor: return only findings with at least this evidence strength. |
| limit | integer | – | Findings to return, strongest evidence first. |
| node_id | string | yes | A node id from search_nodes, e.g. CHEBI:16919 (creatine). |
No output schema declared.
No examples provided.
get_reactions Reactions a compound or protein takes part in (inferred) ~241
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 compound flagged is_hub (water, ATP, protons and the like) returns its reaction count only, because it participates in nearly everything and a row list would not be biology anyone reads. Coverage: the whole of one Rhea release and one Human-GEM release, each reaction counted once; a participant that is not a node in this graph is listed but not linked, and only human enzymes that are nodes are listed at all. An empty result means no reaction in those releases names this node, not that the body has none.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| node_id | string | yes | A node id from search_nodes, e.g. CHEBI:16919 (creatine). |
| offset | integer | – | – |
No output schema declared.
No examples provided.
get_relations Reference-database relations (hypotheses) ~144
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| node_id | string | yes | A node id from search_nodes, e.g. CHEBI:16919 (creatine). |
| offset | integer | – | – |
| predicate | string | – | Limit to one relation type, e.g. transports. |
No output schema declared.
No examples provided.
reach What a compound can become, and through what (inferred, a hypothesis) ~353
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, or a claim that the body actually does this. For measured effects, use get_findings. Common cofactors and currency species (water, ATP, protons and the like) are excluded as intermediate steps, so a route never reads 'reaches everything through ATP'. A currency species is also never materialised as from_id or to_id itself — asking about one returns reachable: null with a coverage note explaining that, not a checked "0 routes". Give to_id to check one target compound; omit it to list everything from_id reaches. A route not being found can mean three different things, and the result's coverage field says which: reachability may not have been BUILT for this scope yet (nothing has been checked); it may have been checked and found NOT REACHABLE through the reactions loaded — never read that as "the body cannot make it"; or the compound asked about may be a currency species, structurally excluded rather than searched.
| Name | Type | Req | Description |
|---|---|---|---|
| depth | integer | – | Longest route to consider, in reaction steps (1-3). |
| from_id | string | yes | The compound to start from. |
| limit | integer | – | Rows to return when to_id is omitted. |
| offset | integer | – | – |
| to_id | string | – | A target compound. Omit to list everything from_id reaches. |
No output schema declared.
No examples provided.
search_nodes Find a compound, outcome or protein ~107
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.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | A name, synonym or phrase. |
No output schema declared.
No examples provided.
What is the Catalyst evidence graph MCP server?
Catalyst evidence graph is an MCP server listed in the public MCP registry as ai.catalystproject/evidence-graph. Findings on what compounds and supplements do in the body, with evidence strength, quote and paper. This page covers its hosted endpoint (https://catalystproject.ai/mcp).
Is the Catalyst evidence graph MCP server safe to use?
Catalyst evidence graph scores 76 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Catalyst evidence graph MCP server expose?
Catalyst evidence graph exposes 7 tools: find_evidence, search_nodes, get_findings, get_finding, get_relations, and 2 more. Their descriptions and schemas cost roughly 1,659 tokens of context every time the server is loaded.
Does the Catalyst evidence graph MCP server require authentication?
No. We connected to Catalyst evidence graph without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Catalyst evidence graph MCP server still maintained?
Catalyst evidence graph is still listed as active in the MCP registry. We last reached this channel on 10 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.