Вход

Показывает данные о действии соединений и добавок в организме с указанием силы доказательств, цитатами и статьями.

готов к вызову Работает Удалённый · Streamable HTTP Без авторизации Разработка ИИ и модели Исследования Официальный реестр · 9 просмотров

Что умеет

Показывает данные о действии соединений и добавок в организме с указанием силы доказательств, цитатами и статьями.

Перевод каталога (LLM) · показать оригинал автора

Findings on what compounds and supplements do in the body, with evidence strength, quote and paper.

Подключение

Удалённый сервер: клиент обращается по адресу, код на вашей машине не запускается.

Claude Desktop

claude_desktop_config.json

Cursor

~/.cursor/mcp.json

Windsurf

~/.codeium/windsurf/mcp_config.json

Вставьте блок mcpServers в файл конфигурации своего клиента. Ключи не входят в файл: вместо SET_LOCALLY подставьте свои значения.

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

Вызов без установки — через шлюз

Агент вызывает инструменты этого сервера через https://www.n2j.ru/mcphub/mcp: hub_call_tool {"server":"ai-catalystproject-evidence-graph","tool":"…","arguments":{…}} Ключ не нужен, но сервер N2J ограничивает частоту анонимных вызовов.

https://catalystproject.ai/mcp

Инструменты

7 схем · ≈ 2 732 условных токенов

find_evidence

Answers "what does X do?" and "does X affect Y?" for a supplement, nutrient, drug, food compound or plant (for example "does magnesium help sleep?", "what is creatine shown to do?", "omega-3 and triglycerides"). Pass the substance as query and the effect or outcome asked about, if there is one, as about. When the person names two substances ("is creatine safe with caffeine"), pass one as query and the other as about, in one call; findings about the pair together come back under in combination. It resolves the name to the node that has findings and returns up to limit findings (default 10), str

Показать схему аргументов
{
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "required": [
        "query"
    ],
    "properties": {
        "about": {
            "type": "string",
            "maxLength": 80,
            "minLength": 2,
            "description": "Optional: the effect, outcome or second substance asked about (e.g. \"sleep\", \"blood pressure\", \"caffeine\"), or a node id from search_nodes."
        },
        "limit": {
            "type": "integer",
            "default": 10,
            "maximum": 50,
            "minimum": 1,
            "description": "Findings to return, strongest evidence first. The default is enough to answer; total_findings says how many match."
        },
        "query": {
            "type": "string",
            "maxLength": 80,
            "minLength": 2,
            "description": "The substance the person asked about, in their words (e.g. \"magnesium\", \"vitamin D\", \"BPC-157\"), or a node id from search_nodes. For a question about an outcome alone (e.g. \"what lowers blood pressure\"), the outcome."
        },
        "detail": {
            "enum": [
                "brief",
                "full"
            ],
            "type": "string",
            "default": "brief",
            "description": "brief (default) returns each finding with its claim, evidence strength, design, population, dose, quote, paper, permalink and a citation to quote as it stands. full adds every other recorded field and is longer; use it only when the person asks for all fields."
        },
        "evidence_strength": {
            "enum": [
                "strong",
                "moderate",
                "limited",
                "very_limited",
                "insufficient"
            ],
            "type": "string",
            "description": "Optional floor: only findings at this evidence strength or stronger, from strong down to insufficient."
        }
    },
    "additionalProperties": []
}

search_nodes

Looks up the node id for a compound, protein, organism or outcome by name or synonym (for example "CoQ10", "caffeine", "CYP1A2", "sleep"). Use it to get the id that get findings, get finding, get relations, get reactions and reach take; for a question about what a substance does, call find evidence instead, which needs no id. Returns up to 10 hits, each with id, label, type and the number of findings; hits with findings come first, so the first hit with findings above 0 is usually the one to use. An enzyme or transporter has type protein. It says nothing about a node beyond its id and how many

Показать схему аргументов
{
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "required": [
        "query"
    ],
    "properties": {
        "query": {
            "type": "string",
            "maxLength": 80,
            "minLength": 2,
            "description": "A name, synonym or short phrase, e.g. \"CoQ10\" or \"vitamin D\". One substance per call."
        }
    },
    "additionalProperties": []
}

get_findings

Lists the curated study findings for one node by id, from search nodes: for a compound, organism or material, what it has been shown to affect; for an outcome, which compounds have been studied against it. Use it to browse a node by id. For a question in words, such as "does X help Y", find evidence answers in one call and needs no id. summary has one row per thing the node has findings about, counted over all its findings and not only the rows returned. The default number of findings, strongest first, is enough to answer. There is no offset: to see a different slice, pass about (an id from su

Показать схему аргументов
{
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "required": [
        "node_id"
    ],
    "properties": {
        "about": {
            "type": "string",
            "maxLength": 80,
            "minLength": 2,
            "description": "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\")."
        },
        "limit": {
            "type": "integer",
            "default": 10,
            "maximum": 50,
            "minimum": 1,
            "description": "Findings to return, strongest evidence first (1 to 50). The default is enough to answer."
        },
        "detail": {
            "enum": [
                "brief",
                "full"
            ],
            "type": "string",
            "default": "brief",
            "description": "brief (default) returns each finding with its claim, evidence strength, design, population, dose, quote, paper, permalink and a citation to quote as it stands. full adds every other recorded field and is longer; use it only when the person asks for all fields."
        },
        "node_id": {
            "type": "string",
            "pattern": "^[A-Za-z_]+:[A-Za-z0-9_./+-]+$",
            "maxLength": 120,
            "minLength": 3,
            "description": "A node id in the form PREFIX:local, e.g. CHEBI:16919 (creatine). Get it from the id field of a search_nodes hit."
        },
        "evidence_strength": {
            "enum": [
                "strong",
                "moderate",
                "limited",
                "very_limited",
                "insufficient"
            ],
            "type": "string",
            "description": "Optional floor: only findings at this evidence strength or stronger, from strong down to insufficient."
        }
    },
    "additionalProperties": []
}

get_finding

Explains one finding by its finding 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. The finding id is 26 characters, from the id field of a find evidence or get findings finding, or the last part of its permalink (/e/{id}). Use it to answer why the evidence behind a finding is as strong as it is, from evidence strength reasons and never by guessing. To find findings, use find evidence or get findings; this tool takes n

Показать схему аргументов
{
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "required": [
        "finding_id"
    ],
    "properties": {
        "finding_id": {
            "type": "string",
            "pattern": "^[0-9A-HJKMNP-TV-Z]{26}$",
            "description": "A 26-character finding id: the id of a finding from find_evidence or get_findings, or the last part of its permalink."
        }
    },
    "additionalProperties": []
}

get_relations

Lists what public reference databases (Reactome, UniProt, Rhea, ChEBI and others) record about one node by id, from search nodes: 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 find evidence. For the reactions a compound or enzyme takes part in, use get reactions; for what a compound can become, use reach. predicate limits the list to one relation type, named as in the predicate field of a row (fo

Показать схему аргументов
{
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "required": [
        "node_id"
    ],
    "properties": {
        "limit": {
            "type": "integer",
            "default": 10,
            "maximum": 50,
            "minimum": 1,
            "description": "Rows to return (1 to 50)."
        },
        "offset": {
            "type": "integer",
            "default": 0,
            "maximum": 10000,
            "minimum": 0,
            "description": "Rows to skip, to page past limit."
        },
        "node_id": {
            "type": "string",
            "pattern": "^[A-Za-z_]+:[A-Za-z0-9_./+-]+$",
            "maxLength": 120,
            "minLength": 3,
            "description": "A node id in the form PREFIX:local, e.g. CHEBI:16919 (creatine). Get it from the id field of a search_nodes hit."
        },
        "predicate": {
            "enum": [
                "transported_by",
                "substrate_of",
                "inhibits",
                "activates",
                "binds",
                "metabolized_by",
                "converted_to",
                "participates_in",
                "regulates",
                "expressed_in",
                "absorbed_at",
                "accumulates_in",
                "affects",
                "depletes",
                "requires_cofactor",
                "contraindicated_with",
                "alters_exposure_of",
                "contradicts",
                "has_adi",
                "response_varies_by",
                "has_functional_parent",
                "enantiomer_of",
                "has_hepatotoxicity_likelihood",
                "regulates_expression_of",
                "interacts_with",
                "covaries_with",
                "affects_phenotype",
                "has_phenotype",
                "has_germline_basis_in",
                "located_in",
                "part_of",
                "affects_relative_to"
            ],
            "type": "string",
            "description": "Limit to one relation type, as in the predicate field of a row, e.g. transported_by."
        }
    },
    "additionalProperties": []
}

get_reactions

Lists the biochemical reactions from Rhea and Human-GEM that a compound is a substrate or product of, or that a protein (enzyme) catalyses or transports, by node id from search nodes. It lists reactions and does not answer a route question: for "can X become Y" or "what can X become", use reach. 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 find evidence. Returns total and up to limit reactions (defa

Показать схему аргументов
{
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "required": [
        "node_id"
    ],
    "properties": {
        "limit": {
            "type": "integer",
            "default": 10,
            "maximum": 50,
            "minimum": 1,
            "description": "Reactions to return (1 to 50). Each carries its participants and enzymes; the default is enough to answer."
        },
        "offset": {
            "type": "integer",
            "default": 0,
            "maximum": 10000,
            "minimum": 0,
            "description": "Reactions to skip, to page past limit."
        },
        "node_id": {
            "type": "string",
            "pattern": "^[A-Za-z_]+:[A-Za-z0-9_./+-]+$",
            "maxLength": 120,
            "minLength": 3,
            "description": "A node id in the form PREFIX:local, e.g. CHEBI:16919 (creatine). Get it from the id field of a search_nodes hit."
        }
    },
    "additionalProperties": []
}

reach

Answers a route question: "can X become Y in the body" (give from id and to id) and "what can X become" (give only from id). Both ids are compound node ids from search nodes, so a question that names two compounds needs one search nodes call for each first. It searches the reactions two public databases (Rhea, Human-GEM) record, up to depth steps (1 to 3, default 3), and returns the routes with the reactions and enzymes along each. Every route is assertion class 'inferred': a hypothesis drawn from reference databases, never a measured or reported effect. Present it as known biochemical connect

Показать схему аргументов
{
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "required": [
        "from_id"
    ],
    "properties": {
        "depth": {
            "type": "integer",
            "default": 3,
            "maximum": 3,
            "minimum": 1,
            "description": "Longest route to consider, in reaction steps (1 to 3)."
        },
        "limit": {
            "type": "integer",
            "default": 10,
            "maximum": 50,
            "minimum": 1,
            "description": "Routes to return when to_id is omitted (1 to 50)."
        },
        "to_id": {
            "type": "string",
            "pattern": "^[A-Za-z_]+:[A-Za-z0-9_./+-]+$",
            "maxLength": 120,
            "minLength": 3,
            "description": "A target compound: a compound node id from search_nodes. Omit to list everything from_id reaches."
        },
        "offset": {
            "type": "integer",
            "default": 0,
            "maximum": 10000,
            "minimum": 0,
            "description": "Routes to skip when to_id is omitted, to page past limit."
        },
        "from_id": {
            "type": "string",
            "pattern": "^[A-Za-z_]+:[A-Za-z0-9_./+-]+$",
            "maxLength": 120,
            "minLength": 3,
            "description": "The compound to start from: a compound node id from search_nodes."
        }
    },
    "additionalProperties": []
}