Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Folklore Clinical Variant Interpretation MCP

REMOTE · API.HELENA.BIO · SCANNED SEP 20

Bioinformatics MCP for genomic variant interpretation, gene-disease evidence and literature.

Available components

0 this week 83 Trust /100
Trust breakdown (7 categories)

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 Security66
Transport & Reachability100
Schema Quality & AI Usability80
  • 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 1484 tokens (~185/item across 8 items; 7 tools + 1 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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
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
Install

How do I install the Folklore Clinical Variant Interpretation MCP server?

Folklore Clinical Variant Interpretation MCP is a hosted endpoint at https://api.helena.bio/folklore/v1/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 · api.helena.bio

# add to Claude Code
claude mcp add --transport http helena-bioinformatics-folklore 'https://api.helena.bio/folklore/v1/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "helena-bioinformatics-folklore": {
      "url": "https://api.helena.bio/folklore/v1/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "helena-bioinformatics-folklore": {
      "type": "http",
      "url": "https://api.helena.bio/folklore/v1/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.helena-bioinformatics-folklore]
url = "https://api.helena.bio/folklore/v1/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "helena-bioinformatics-folklore": {
      "type": "remote",
      "url": "https://api.helena.bio/folklore/v1/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add helena-bioinformatics-folklore --url 'https://api.helena.bio/folklore/v1/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  helena-bioinformatics-folklore:
    url: "https://api.helena.bio/folklore/v1/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "helena-bioinformatics-folklore": {
      "Transport": "http",
      "Url": "https://api.helena.bio/folklore/v1/mcp"
    }
  }
}
# add to Vellum
assistant mcp add helena-bioinformatics-folklore -t streamable-http -u 'https://api.helena.bio/folklore/v1/mcp'
// mcp.json
{
  "mcpServers": {
    "helena-bioinformatics-folklore": {
      "type": "http",
      "url": "https://api.helena.bio/folklore/v1/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

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.

  • 11 Sept 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “search_variant_evidence” rewrote its description, which is the text the model reads security
    • Schema quality: 1061 → 1484 functional
    • Server version: 1.4.2 → 1.5.0 functional
    • New tool “get_gene_disease_associations” functional
    • New tool “search_disease_genes” functional
  • 10 Sept 26 0
    • Tool “search_variant_evidence” rewrote its description, which is the text the model reads security
    • Server version: 1.4.1 → 1.4.2 functional
  • 9 Sept 26 0
    • Stability: 0.97 → pass security
  • 8 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 6 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

  • 4 Sept 26 +2
    • DNSSEC: fail → pass security
  • 2 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

  • 31 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

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 20 Sept 2026 · Probed https://api.helena.bio/folklore/v1/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=api.helena.bio CN=YE1,O=Let's Encrypt,C=US 31 Jul 2026 29 Oct 2026 ECDSA 256 ECDSA-SHA384 6771d20c762914c9ce8e1bf90853ecaba4c
SANs: api.helena.bio
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC secure

Validation of api.helena.bio. Secure

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
bio. present 16334 8 Verified
helena.bio. present 22743 13 Verified
api.helena.bio. Verified address RRset verified with the apex keys
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

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.helena.bio/folklore/v1/mcp Verified 200
http (plaintext) http://api.helena.bio/folklore/v1/mcp Inconclusive 404
MCP tools · 7 exposed · ~1,243 tokens

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 →

Tool Tokens
get_gene_disease_associations ~169

Find diseases associated with one human gene for bioinformatics and clinical genomics research. Accepts an exact gene symbol or HGNC identifier. Returns ClinGen gene-disease validity assertions, relation-specific inheritance, source reports and snapshot provenance. Preserves conflicting and limited assertions. Gene-disease validity is not variant pathogenicity or a patient diagnosis. Use only a public gene identifier; no patient or case data. Results require professional review.

NameTypeReqDescription
genestringyesOne public human gene symbol or HGNC identifier, for example BRCA1 or HGNC:1100. No patient data.
limitintegerMaximum number of source assertions per page, from 1 to 50.
offsetintegerZero-based assertion offset; use the returned nextOffset when present.
NameTypeReqDescription
associationsarrayyes
contractVersionstringyes
paginationyes
queryyes
sourceyes
statusstringyes
usage_boundaryyes
warningsarrayyes

No examples provided.

get_publication_details ~124

Retrieve the complete public bibliographic record for one PMID from Folklore's PubMed-derived genetics corpus. Returns the full abstract, authors, journal metadata, publication and MeSH terms, gene and variant mentions, retraction status, and PubMed/PMC links. Use after literature search when a user asks to inspect a specific publication. This is read-only professional literature evidence and contains no patient context.

NameTypeReqDescription
pmidstringyesOne PubMed identifier to look up in Folklore's current corpus, as 1 to 12 digits without a PMID prefix.
NameTypeReqDescription
contract_versionstringyes
publicationyes
usage_boundaryobjectyes

No examples provided.

search_disease_genes ~177

Find human genes associated with a disease for genomic analysis and rare-disease research. Accepts an exact MONDO identifier or a disease-name search. Returns matching ClinGen gene-disease validity assertions with inheritance, source reports and snapshot provenance. Name searches may match multiple diseases; preserve their distinct identities and do not infer a diagnosis. Use only a public disease name or identifier; no symptoms, patient or case data. Results require professional review.

NameTypeReqDescription
diseasestringyesOne public disease name or exact MONDO identifier (MONDO: followed by seven digits). A name search may match multiple distinct diseases. No symptoms or patient narrative.
limitintegerMaximum number of source assertions per page, from 1 to 50.
offsetintegerZero-based assertion offset; use the returned nextOffset when present.
NameTypeReqDescription
associationsarrayyes
contractVersionstringyes
paginationyes
queryyes
sourceyes
statusstringyes
usage_boundaryyes
warningsarrayyes

No examples provided.

search_literature_corpus ~229

Semantically search the public scientific Literature Corpus by a natural-language question. A question may include one or more PMID, DOI or PMCID references; those publications become exact anchors for finding related experiments, evidence and concepts across the corpus. Also accepts genes, variants, phenotypes, HPO and OMIM concepts. Include every known publication identifier in the query when the user asks to compare papers or find work related to a specific paper. Returns source-linked evidence candidates for professional review, not diagnoses, causality claims or treatment recommendations.

NameTypeReqDescription
cursorOpaque continuation cursor from the preceding response for the same query and sort order; omit for the first page.
limitintegerMaximum number of publications to return, from 1 to 25.
querystringyesNatural-language literature question or exact PMID, DOI, PMCID, gene, variant, phenotype, HPO, or OMIM query. Include every known publication identifier when comparing or finding related papers.
sortstringResult ordering: relevance-ranked, newest publication first, or oldest publication first.
NameTypeReqDescription
contract_versionstringyes
graph_degraded_reason
graph_usedboolean
graph_version
has_moreboolean
next_cursor
querystringyes
resultsarrayyes
returned_countintegeryes
searchable_fieldsarrayyes
semantic_degraded_reason
semantic_index_usedboolean
usage_boundaryobjectyes

No examples provided.

search_variant_evidence ~266

Interpret this variant, explain what this HGVS means, or review this VUS. Use for human genomic variant analysis within bioinformatics workflows, including review of an already identified WGS/WES variant. Use when a user asks to classify or interpret pathogenicity, review a VUS, check available ClinVar assertions or population-frequency evidence, or resolve a variant notation. Classify, interpret or resolve one public GRCh38 germline SNV or simple indel smaller than 50 bp. Accepts coordinates, genomic/coding/protein HGVS, SPDI or rsID. Returns normalized variant identity, automated ACMG/AMP decision support, evidence, provenance and explicit limitations. This is variant-level decision support for professional review. It does not evaluate patient context and must not be presented as a diagnosis or treatment recommendation. Never choose a candidate when resolution is ambiguous.

NameTypeReqDescription
assemblystringReference genome assembly. Folklore currently accepts GRCh38 only.
querystringyesOne germline nuclear SNV or simple indel to resolve and interpret; accepted forms include coordinates, genomic/coding/protein HGVS, SPDI, rsID, or a returned Folklore canonical_key in GRCh38:chrN:pos…
NameTypeReqDescription
adapter_erroryes
contract_versionstringyes
record_urlstring|nullyes
resultyes
usage_boundaryobjectyes

No examples provided.

search_variant_literature ~219

Resolve one public GRCh38 germline variant and retrieve relevant publications from Folklore's PubMed-derived genetics corpus. Exact variant mentions rank ahead of broader gene associations. Use when a user asks what has been published about a variant, gene or associated condition. Associations do not establish causality, pathogenicity or a diagnosis and do not change Folklore's ACMG/AMP classification.

NameTypeReqDescription
assemblystringReference genome assembly. Folklore currently accepts GRCh38 only.
limitintegerMaximum number of publications to return, from 1 to 25.
querystringyesOne germline nuclear SNV or simple indel to resolve before retrieving its literature; this is a variant identifier, not a natural-language question. Accepts a returned Folklore canonical_key in GRCh3…
questionOptional natural-language focus applied after the variant is resolved, such as a condition or evidence question; do not put the variant identifier here.
NameTypeReqDescription
contract_versionstring
literatureyes
statusstringyes
usage_boundaryobjectyes
variant_resultobjectyes

No examples provided.

support_helena ~59

Learn how an agent can support or spread Helena's free public scientific infrastructure through the separate Helena Good MCP. This is an explicit opt-in information action. It does not initiate payment, create a relay, or change any Folklore scientific result.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

Common questions

What is the Folklore Clinical Variant Interpretation MCP server?

Folklore Clinical Variant Interpretation MCP is listed in the public MCP registry as io.github.helena-bioinformatics/folklore. Bioinformatics MCP for genomic variant interpretation, gene-disease evidence and literature. This page covers its hosted endpoint (https://api.helena.bio/folklore/v1/mcp).

Is the Folklore Clinical Variant Interpretation MCP server safe to use?

Folklore Clinical Variant Interpretation MCP scores 83 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 Folklore Clinical Variant Interpretation MCP server expose?

Folklore Clinical Variant Interpretation MCP exposes 7 tools: search_variant_evidence, search_variant_literature, get_publication_details, search_literature_corpus, support_helena, and 2 more. Their descriptions and schemas cost roughly 1,243 tokens of context every time the server is loaded.

Does the Folklore Clinical Variant Interpretation MCP server require authentication?

No. We connected to Folklore Clinical Variant Interpretation MCP without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Folklore Clinical Variant Interpretation MCP server still maintained?

Folklore Clinical Variant Interpretation MCP is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.