STRING Database MCP Server

Measured conclusion: Deep-tested. L2 outcome: tools_ok.

Query STRING interactions, enrichment, annotations, homology, and PPI networks.

Add to your agent

Copy this into your MCP client config:

{
  "mcpServers": {
    "STRING Database MCP Server": {
      "url": "https://mcp.string-db.org/",
      "transport": "streamable-http"
    }
  }
}

Measured tools (17)

• string_resolve_proteins

  Maps one or more protein identifiers to their corresponding STRING metadata, including: gene symbol, description, sequence, domains, species, and internal STRING ID. This method is useful for translating raw identifiers into readable, annotated protein entries. Example input: "TP53%0dSMO"

  Parameters:

  • proteins (required) — string — One or more input protein identifiers (gene symbols, UniProt IDs, etc.), separated by carriage return (%0d).
  • species — string — NCBI taxonomy ID (e.g. 9606 for human) or STRING genome ID (e.g. STRG0AXXXXX for uploaded genomes).
  • show_sequence — Include sequences. Use only if the user requests sequence data.

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• string_interactions_query_set

  Retrieves the interactions between the query proteins. Use this method only when you specifically need to list the interactions between all proteins in your query set. - For a **single protein**, the network includes that protein and its top 10 most likely interaction partners, plus all interactions among those partners. - For **multiple proteins**, the network includes all direct interactions between them. - STRING does not store or report information about self-interactions/homomers; if asked, explain the limitation. If few or no interactions are returned, consider reducing the `required_score`. For large query sets (>50 proteins), consider increasing the `required_score` (e.g. ≥700) to focus on high-confidence interactions and avoid overly dense networks. - Expand the names of score sources: `nscore` (neighborhood), `fscore` (fusion), `pscore` (phylogenetic profile), `ascore` (coexpression), `escore` (experimental), `dscore` (database), `tscore` (text-mining)

  Parameters:

  • proteins (required) — string — One or more protein identifiers, separated by carriage return (%0d).
  • species — string — NCBI taxonomy ID (e.g. 9606 for human) or STRING genome ID (e.g. STRG0AXXXXX for uploaded genomes).
  • network_type — Omit for the default functional network. Its typed view can include physical and directed regulatory attributes when STRING returns them; inspect `physical` and `regulatory.directions` before claiming those edge types. Set physical for binding, complex, or co-complex questions. Set regulatory for directed regulatory relationships between proteins.
  • extend_network — Number of additional proteins to add to the network based on their connectivity. Default is 10 for a single protein query and 0 for multiple proteins. Set only if the user asks to add, extend, include a neighborhood, or show connecting proteins.
  • network_flavor — Defaults are typed for functional networks, evidence for physical networks, and confidence for regulatory networks. Typed returns functional pairs with any physical and directed regulatory attributes that STRING reports; it does not make every pair physical or regulatory. Typed is available only for functional networks. Set evidence or confidence only when the user requests that edge display style.
  • required_score — Minimum confidence score for an interaction. Omit unless a confidence threshold is requested or a broader/narrower threshold is needed.

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• string_all_interaction_partners

  Retrieves all interaction partners for one or more proteins from STRING. This tool returns all known interactions between your query protein(s) and **any other proteins in the STRING database**. - Use this when asking **“What does TP53 interact with?”** - It differs from `string_interactions_query_set`, which only shows interactions **within the input set** or a limited extension of it. You can filter for strong interactions using `required_score`. - Evidence scores: `nscore` (neighborhood), `fscore` (fusion), `pscore` (phylogenetic profile), `ascore` (coexpression), `escore` (experimental), `dscore` (database), `tscore` (text mining)

  Parameters:

  • identifiers (required) — string — One or more protein identifiers, separated by carriage return (%0d).
  • species — string — NCBI taxonomy ID (e.g. 9606 for human) or STRING genome ID (e.g. STRG0AXXXXX for uploaded genomes). Only set when required.
  • network_type — Omit for the default functional network. Its typed view can include physical and directed regulatory attributes when STRING returns them; inspect `physical` and `regulatory.directions` before claiming those edge types. Set physical for binding, complex, or co-complex questions. Set regulatory for directed regulatory relationships between proteins.
  • network_flavor — Defaults are typed for functional networks, evidence for physical networks, and confidence for regulatory networks. Typed returns functional pairs with any physical and directed regulatory attributes that STRING reports; it does not make every pair physical or regulatory. Typed is available only for functional networks. Set evidence or confidence only when the user requests that edge display style.
  • required_score — Minimum interaction score to include. Omit unless a confidence threshold is requested or a broader/narrower threshold is needed.

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• string_visual_network

  Retrieves a URL to a **STRING interaction network image** for one or more proteins. - For a single protein: includes the protein and its top 10 most likely interactors. - For multiple proteins: includes all known interactions **within the query set**. The input may include one numeric value per protein, such as fold change, effect size, or score. These values are visualized as colored halos around the nodes, allowing overlay of protein-level measurements on the network. Example: PTEN 2.1 SMO -1.3 If numeric values are provided: - positive values are shown in blue - negative values are shown in red - larger absolute values produce stronger halo intensity If the user provides numeric values together with the proteins, preserve them in the query. If few or no interactions are shown, consider lowering `required_score`. For large queries (>100 proteins): - use `network_flavor="confidence"` - increase `required_score` (e.g. 700) Always ask if the user also wants a link to the interactive STRING network page. Input parameters should match those used in related STRING tools (e.g. `string_interactions_query_set`), unless otherwise specified.

  Parameters:

  • proteins (required) — string — One or more protein IDs, optionally followed by one numeric value per protein. Use newline (%0d) between entries. Tabs and spaces are accepted as separators.
  • species — string — NCBI/STRING taxon (e.g. 9606 for human, or STRG0AXXXXX).
  • network_type — Omit for the default functional network. Its typed view can include physical and directed regulatory attributes when STRING returns them; inspect `physical` and `regulatory.directions` before claiming those edge types. Set physical for binding, complex, or co-complex questions. Set regulatory for directed regulatory relationships between proteins.
  • extend_network — Add specified number of nodes to the network, based on their scores. Default: 0, or 10 for single protein queries.
  • network_flavor — Defaults are typed for functional networks, evidence for physical networks, and confidence for regulatory networks. Typed returns functional pairs with any physical and directed regulatory attributes that STRING reports; it does not make every pair physical or regulatory. Typed is available only for functional networks. Set evidence or confidence only when the user requests that edge display style.
  • required_score — Threshold of significance to include an interaction. Omit for STRING default filtering. Set only when a threshold is requested or a broader/narrower threshold is needed.
  • center_node_labels — Center protein names on nodes. Set only if the user asks to center labels.
  • do_not_show_structures — Remove small protein structure previews from inside the node bubbles. Set only if the user asks to remove or hide structure previews.
  • hide_disconnected_nodes — Hide proteins not connected to any other protein. Set only if the user asks to hide disconnected or unconnected proteins.

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• string_network_clustering

  Performs **network clustering** on a STRING interaction network and returns a network image URL, an interactive STRING network URL, and details about each detected cluster. Provide a table with each detected cluster’s color, STRING-derived functional description, and any returned features that distinguish it from the others. Use the same parameters as in the network creation step to ensure consistency. If the network already contains disconnected subgraphs, the resulting number of clusters may differ from the requested value. Inter-cluster edges are faded by default. Use `inter_cluster_edge_visibility` to select a different display style. Notes: - For small queries (≤5 proteins), the `required_score` parameter is automatically lowered to 0. - If only a single cluster is produced, try increasing `required_score`, adjusting the clustering parameter, or switching to a physical network for a sparser interaction map.

  Parameters:

  • proteins (required) — string — One or more protein identifiers (optionally with values). Separate entries with newline (%0d). Numeric values (e.g. expression data) can be provided after identifiers.
  • species — string — NCBI/STRING taxonomy ID (e.g. 9606 for human, or STRG0AXXXXX for uploaded genomes).
  • network_type — Omit for the default functional network. Its typed view can include physical and directed regulatory attributes when STRING returns them; inspect `physical` and `regulatory.directions` before claiming those edge types. Set physical for binding, complex, or co-complex questions. Set regulatory for directed regulatory relationships between proteins.
  • extend_network — Add specified number of additional nodes to the network based on their interaction scores. Default: 0, or 10 for single-protein queries.
  • network_flavor — Defaults are typed for functional networks, evidence for physical networks, and confidence for regulatory networks. Typed returns functional pairs with any physical and directed regulatory attributes that STRING reports; it does not make every pair physical or regulatory. Typed is available only for functional networks. Set evidence or confidence only when the user requests that edge display style.
  • required_score — Minimum interaction confidence score. Omit for STRING default filtering. Set only when a threshold is requested or a broader/narrower threshold is needed.
  • center_node_labels — Center protein labels on nodes. Set only if the user asks to center labels.
  • clustering_algorithm — Leiden identifies natural communities based on network connectivity and is the default. MCL identifies densely connected subnetworks based on connectivity flow. kmeans partitions proteins into a fixed number of clusters.
  • clustering_parameter — Controls clustering granularity. For Leiden: resolution parameter 0.1-10.0, default 1.0; higher values produce more, smaller clusters. For MCL: inflation parameter 1.0-10.0, default 3.0. For kmeans: number of clusters, integer >=2, default 3.
  • hide_disconnected_nodes — Hide unconnected nodes. Set only if the user asks to hide disconnected or unconnected proteins.
  • inter_cluster_edge_visibility — How to display edges between clusters: faded, dotted, solid, or noshow. Defaults to faded.

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• string_network_link

  Retrieves a stable URL to an interactive STRING network for one or more proteins. - For a single protein: includes the protein and its top 10 most likely interactors. - For multiple proteins: includes all known interactions **within the query set**. The input may include one numeric value per protein, such as fold change, effect size, or score. These values are visualized as colored halos around the nodes, allowing overlay of protein-level measurements on the network. Example: PTEN 2.1 SMO -1.3 If numeric values are provided: - positive values are shown in blue - negative values are shown in red - larger absolute values produce stronger halo intensity If the user provides numeric values together with the proteins, preserve them in the query. If few or no interactions are shown, consider lowering `required_score`. For large queries (>100 proteins): - use `network_flavor="confidence"` - increase `required_score` (e.g. 700) Always display the link as a markdown hyperlink (hide the raw URL). Input parameters should match those used in related STRING tools unless otherwise specified.

  Parameters:

  • proteins (required) — string — One or more protein IDs, optionally followed by one numeric value per protein. Use newline (%0d) between entries. Tabs and spaces are accepted as separators.
  • species — string — NCBI/STRING taxon (e.g. 9606 for human, or STRG0AXXXXX).
  • network_type — Omit for the default functional network. Its typed view can include physical and directed regulatory attributes when STRING returns them; inspect `physical` and `regulatory.directions` before claiming those edge types. Set physical for binding, complex, or co-complex questions. Set regulatory for directed regulatory relationships between proteins.
  • extend_network — Add white nodes to network, based on scores. Default: 0.
  • network_flavor — Defaults are typed for functional networks, evidence for physical networks, and confidence for regulatory networks. Typed returns functional pairs with any physical and directed regulatory attributes that STRING reports; it does not make every pair physical or regulatory. Typed is available only for functional networks. Set evidence or confidence only when the user requests that edge display style.
  • required_score — Threshold of significance to include an interaction. Omit for STRING default filtering. Set only when a threshold is requested or a broader/narrower threshold is needed.
  • hide_disconnected_nodes — Hide proteins not connected to any other protein. Set only if the user asks to hide disconnected or unconnected proteins.

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• string_homology

  Retrieves pairwise protein similarity scores (Smith–Waterman bit scores) for the query proteins. - If no target species (`species_b`) is provided, results are intra-species (within the query species). - To retrieve homologs in other species or clades (e.g. vertebrates, yeast, plants), specify one or more NCBI taxon IDs in `species_b`. - Multiple target species are supported; ask the user to clarify if needed. - Always report species names together with their taxon IDs. - Bit scores < 50 are not reported. - Results are truncated to the top 50 proteins per input protein.

  Parameters:

  • proteins (required) — string — One or more protein identifiers, separated by %0d.
  • species — string — NCBI/STRING taxon (e.g. 9606 for human, or STRG0AXXXXX for uploaded genomes).
  • species_b — One or more NCBI taxon IDs for target species, separated by comma (e.g. 9606,7227,4932 for human, fly, and yeast).

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• string_interaction_evidence

  Retrieves direct links to STRING evidence pages for protein–protein interaction pairs. Use this tool only when a STRING evidence page/link is needed. To determine whether an interaction is supported, use `string_interactions_query_set`. It returns URLs linking to STRING’s evidence pages, which display the underlying data sources (experimental results, publications, and curated databases) supporting each predicted interaction. A URL can be generated even for unsupported pairs; the URL is not itself an interaction verdict. The returned page lets the user explore functional, physical, and regulatory relationship views through its tabs. Parameters: - **identifier_a**: Query protein identifier (Protein A) - **identifiers_b**: One or more target protein identifiers (Protein B), separated by `%0d` - **species**: NCBI taxonomy ID (e.g. `9606` for human or `10090` for mouse) - **network_type**: Set to `physical` for physical evidence or `regulatory` for directed regulatory evidence. Typical user questions that should trigger this tool: - "Can you show me the STRING evidence for this interaction?" - "Show me the details supporting this interaction." - "What supports the interaction between TP53 and MDM2?" - "Where can I find the STRING evidence for this pair?"

  Parameters:

  • identifier_a (required) — string — Protein A identifier.
  • identifiers_b (required) — string — One or more protein B identifiers, separated by %0d.
  • species — string — NCBI/STRING taxon (e.g. 9606 for human, or STRG0AXXXXX for uploaded genomes).
  • network_type — Set physical for physical-interaction evidence or regulatory for directed regulatory evidence. Omit for the functional interaction evidence page.

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• string_enrichment

  This tool retrieves functional enrichment for a set of proteins using STRING. - If queried with a single protein, the tool expands the query to include the protein’s 10 most likely interactors; enrichment is performed on this set, not the original single protein. - For two or more proteins, enrichment is performed on the exact input set. - When calling related tools, use the same input parameters unless otherwise specified. - Focus summaries on the top categories and most relevant terms for the results. Always report FDR for each claim. - Report FDR as a human-readable value (e.g. 2.3e-5 or 0.023). - IMPORTANT: Remember to suggest showing an enrichment graph for a specific category of user interest (e.g., GO, KEGG) - Very large responses are capped while preserving category diversity. - Use `expand_category` to return only one category with expanded term coverage and per-term gene details. - If a row has `preferredNames_omitted: true`, do not infer which proteins are in that term from the returned rows. Use `string_functional_annotation` with the same proteins/species and `detail_for_term` set to the exact term ID. Output fields (per enriched term): - category: Term category (e.g., GO Process, KEGG pathway) - term: Enriched term (GO ID, domain, or pathway) - number_of_genes: Number of input genes with this term - number_of_genes_in_background: Number of background genes with this term - ncbiTaxonId: NCBI taxon ID - preferredNames: Canonical protein names, only when the full per-term list is short enough to show - proteinCount: Number of proteins matching this term - preferredNames_omitted: True when the gene list was omitted instead of showing a misleading partial list - p_value: Raw p-value - fdr: False Discovery Rate (B-H corrected p-value) - strength: Enrichment effect size, calculated as log10(observed genes / expected genes) - signal: Balanced enrichment-ranking metric combining the observed/expected ratio and -log(FDR) - description: Description of the enriched term Response metadata: - input_gene_name_mapping: Only included when displayed gene lists contain submitted identifiers that differ from STRING preferred names. - category_summary: Total and returned term counts per category; use `expand_category` for categories where `truncated` is true or where the user wants deeper category-specific detail. - truncated_categories / omitted_categories: Categories with terms not shown in the current response.

  Parameters:

  • proteins (required) — string — One or more protein identifiers, separated by %0d.
  • species — NCBI/STRING taxon (e.g. 9606 for human, or STRG0AXXXXX). Use only when required.
  • expand_category — Return only this enrichment category with expanded term coverage and a larger per-term gene-list cutoff. Use a category from metadata.category_summary.

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• string_functional_annotation

  This tool retrieves curated functional annotations for a set of proteins. Each input protein is mapped to known biological terms from ontologies, pathway databases, tissues, compartments and domains — such as Gene Ontology (GO), KEGG, and UniProt Keywords. - Use this when the user asks what a protein does, where it's localized, expressed, or which pathways it participates in. - Keep the output short and focused by highlighting a few diverse and specific annotations for each protein. - This tool does not perform statistical enrichment — use the enrichment tool for that. Output fields (per protein): - stringId: STRING protein identifier - preferredName: Gene name or alias - annotation: Functional description or keyword - category: Source category (e.g. GO, KEGG, Keyword) - term: Functional term or ID

  Parameters:

  • identifiers (required) — string — Separate multiple protein queries by %0d.
  • species — string — NCBI/STRING taxon (e.g. 9606 for human, or STRG0AXXXXX for uploaded genomes).
  • detail_for_term — Exact functional term ID to return with the full list of matching input proteins. Use this when a previous result says a protein list was shortened, omitted, or replaced with 'many'.

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• string_enrichment_image_url

  Retrieves a STRING enrichment figure (image URL) for a set of proteins. For the enriched terms and FDR values, use `string_enrichment`. - Each figure shows a single enrichment category; call again with another `category` to show a different one. - Use the same proteins and species as the network and enrichment results already shown to the user, so the figure matches them.

  Parameters:

  • identifiers (required) — string — Protein identifiers, separated by %0d.
  • x_axis — Value shown on the X-axis; also selects and orders the terms. If omitted, STRING uses signal.
  • species — string — NCBI/STRING taxon (e.g. 9606 for human, or STRG0AXXXXX).
  • category — Term category for enrichment. If omitted, STRING uses Process. Use Process/Function/Component for GO, KEGG for KEGG pathways, RCTM for Reactome, and PMID for publications.
  • graph_type — Plot type: dotplot or barplot (horizontal bar chart). If omitted, STRING uses dotplot.
  • color_palette — Color palette for FDR. If omitted, STRING uses mint_blue.
  • group_by_similarity — Visually groups terms based on term similarity. Default: 0.8. Details: string_help topic 'enrichment_grouping'.
  • number_of_terms_shown — Max number of terms shown on plot. Default: 10.

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• string_ppi_enrichment

  This tool tests if your network is enriched in protein-protein interactions compared to the background proteome-wide distribution (i.e., if your proteins are more functionally connected than expected by chance). - The enrichment is assessed using the actual observed edges versus expected edges in a random network of the same size. - The p-value reflects the likelihood that your observed number of interactions would occur by chance. - Report the p-value as a human-readable value (e.g. 2.3e-5 or 0.023). When calling related tools use the same input parameters unless otherwise specified. Output fields: - number_of_nodes: Number of proteins in your network - number_of_edges: Number of observed edges/interactions - average_node_degree: Mean degree (average number of interactions per node) - local_clustering_coefficient: Average clustering coefficient in the network - expected_number_of_edges: Expected number of edges in a random network of the same size - p_value: p-value for network enrichment (smaller = more enriched) Example identifiers: "SMO%0dTP53"

  Parameters:

  • identifiers (required) — string — One or more protein identifiers, separated by %0d.
  • species — string — NCBI/STRING taxon (e.g. 9606 for human, or STRG0AXXXXX for uploaded genomes).
  • required_score — Minimum interaction confidence score. Omit unless a confidence threshold is requested or a broader/narrower threshold is needed.

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• string_proteins_for_term

  Retrieve proteins annotated with a functional term or descriptive text in a single species. You can query for tissues, compartments, diseases, processes, pathways, and domains. IMPORTANT: For cross-species comparisons, run this tool separately for each species. Select relevant model organisms to search or ask user to provide the selection. The results reflect annotation depth within each category; use caution when interpreting. If no results are found, try simplifying the query. For tissue queries, follow BRENDA tissue nomenclature and omit the word "tissue" (e.g. use "skin" instead of "skin tissue"). Output fields: - category: Source database of the matched functional term (e.g. GO, KEGG, Reactome, Pfam, InterPro). - term: Exact identifier for the functional term. - description: The free text description of the term. - proteinCount: Number of proteins annotated with that term - preferredNames: Full protein-name list when `detail_for_term` is set - stringIds: STRING protein identifiers when returned - preferredNames_omitted: True when a row omits the protein-name list - stringIds_omitted: True when STRING identifiers are omitted

  Parameters:

  • term_text (required) — string — Functional term identifier (GO, KEGG, Reactome, etc.) or descriptive free text.
  • species — string — NCBI/STRING taxonomy ID. This tool only supports one species per call. It cannot return results across multiple species or identify the species with the most/fewest proteins. For such questions, run this tool separately for each species and then compare the results. Default is 9606 (human). Examples: 10090 for mouse, or STRG0AXXXXX for uploaded genomes.
  • detail_for_term — Exact term ID to return as one full protein-name list.

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• string_sequence_search

  Searches the STRING database using **amino acid sequences** to identify matching proteins. - Accepts a single sequence or multiple sequences in FASTA format. - Returns the most similar STRING protein(s) for the specified species, based on sequence similarity. - Use this when the protein identifier is unknown or unresolvable by `string_resolve_proteins`.

  Parameters:

  • sequences (required) — string — One or more protein sequences in plain or FASTA format.For multiple sequences, use standard FASTA headers (lines beginning with '>'). Only amino acid sequences are supported — nucleotide sequences are not accepted.
  • species — string — NCBI or STRING taxonomy ID. You can query with a clade or species. eg.g 2 for bacteria, 7742 for vertebrates, 511145 for E. coli

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• string_query_species

  Search for species or clades available in STRING by free-text query and return their NCBI taxonomy IDs. - Use this when the user asks which species or clades are present in STRING, or when you need the correct NCBI taxon ID to pass to other tools. - use this to resolve NCBI taxons IDs to their scientific names. - Accepts up to 100 taxon IDs separated by `%0d`. - The results are limited to the top 50 matches per query. - When the user asks for a species list, do not list clades. - If the requested species cannot be matched (i.e. the correct species is not present in the results), **immediately invoke the 'string_help' tool with topic='missing_species'**.

  Parameters:

  • species_text (required) — string — One species/clade search term or multiple NCBI taxon IDs separated by carriage return (%0d). For multiple queries, use taxon IDs rather than free-text names.

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• string_create_file

  Creates a downloadable file for STRING-derived results. Use this tool when the user explicitly asks to download, save, export, or receive a file containing STRING data, tables, protein lists, enrichment results, networks, etc. When a response would otherwise include a publication-style or supplementary result table, or another table clearly intended for reuse outside chat, mention that a downloadable TSV/CSV file can be generated on request. Ask whether they want the file, unless they already requested it. Do not create the file until the user asks for it. Do not store unrelated data or full conversation transcripts.

  Parameters:

  • filename (required) — string — Suggested output filename with a safe extension such as .tsv, .csv, .json, .md, or .txt. Match content to the extension; prefer .tsv for reusable tabular STRING data. Use a concise name that reflects the STRING analysis result.
  • content (required) — string — STRING-derived file content. For .tsv/.csv: one rectangular table, one header row, matching delimiter, no Markdown/prose/repeated headers/multiple tables. Use one row per entity, edge, cluster member, annotation, or enrichment term. Use bare numeric scores/FDR/p-values; put interpretation and caveats in chat or .md/.txt.

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• string_help

  Provides explanatory text for STRING features and limitations. Use this tool when the user question involves: - What is STRING is or how to use the tool (how_to_use_string, cytoscape) - functionality not available via MCP tools (e.g. GSEA or large datasets). - meaning of network edges and their visual encoding (network_edge_legend) - interpretation of enrichment strength and signal (enrichment_scores) - grouping of terms in enrichment figures (enrichment_grouping)

  Parameters:

  • topic — Help topic to display. If omitted, returns the available topics.

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

Publisher website Repository

Measured by MCPYP probing. Untested fields are omitted, never estimated. Listing is always free; MCPYP never proxies calls or stores user tokens.