Helix GenoSphere

Ask population-genomics questions across 500,000+ exome-sequenced participants with linked EHR.

Add to Agentman Studio

Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.

Paste it into any MCP client. Setup docs

Resources

What the Helix GenoSphere connector does

The Helix GenoSphere MCP server answers population-genomics questions from Claude against a research cohort of more than 500,000 exome-sequenced participants with linked electronic health records. Five read-only tools return carrier counts, condition prevalence and dataset coverage. Helix states every result is a de-identified aggregate, never an individual record.

Verified connector

Listed by Anthropic as a partner connector in its Connectors Directory.

Connection checked by Agentman on .

Anthropic states this reflects the level of review a connector received, not a security audit.

Helix GenoSphere tools (5)

  • get_variant_frequency
  • check_gene_availability
  • get_dataset_overview
  • search_concepts
  • get_patient_count

Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.

Limits

  • The aggregate-only guarantee is Helix's claim, not our finding. Helix states it in two documents and the five tool names are consistent with it. But the endpoint refused every anonymous request, so we read no tool schema and cannot confirm that no parameter accepts a participant identifier. Treat it as a documented design, not a tested boundary — and if your use is governed, ask Helix for the de-identification methodology in writing.
  • We could not verify the authentication posture. The host returned a byte-identical 118-byte AWS load balancer 403 to every path we tried — the endpoint itself, four .well-known metadata paths, the site root, and a deliberately nonsensical control path. That is a blanket edge block, not an MCP authentication challenge: there was no www-authenticate header and no JSON error body. Anthropic's own probe of this server recorded the same 403. So authMode here reflects Helix's documentation of Okta sign-in, not our observation, and authVerified is false.
  • No OAuth scopes are readable, so none can be assessed. With every metadata path blocked we cannot say whether a boundary exists between the five reads — though on a surface with no write tool, the scope question carries much less weight than it would elsewhere.
  • Helix publishes no tool list. The five names come from Anthropic's directory. The correspondence with Helix's prose capabilities is one-to-one, but no vendor enumeration exists to diff against.
  • The queryable gene panel is a curated subset of the exome. A gene returning unavailable is a statement about the panel, not about Helix's data holdings. Do not read absence as evidence.
  • A zero is not a negative result. Helix states explicitly that an empty result means nothing matched within the dataset's scope rather than that the answer is definitively none. Suppressed small counts and true zeros are not distinguished in the output, so neither can be cited as an absence of carriers. This is the most likely way to draw a wrong scientific conclusion from this connector.
  • Cohort composition is not a general population. The dataset is drawn from health systems across North America, and Helix's therapeutic-area cohorts are deliberately enriched — over 230,000 cardiovascular and metabolic patients, more than 54,000 on GLP-1 agonists, 25,000+ MASH-enriched records. Prevalence figures reflect this cohort, not the general population. Run get_dataset_overview before generalising from any count.
  • Repeated narrow queries are the residual privacy risk, not any single one. Suppression protects small groups per response. An agent that issues many finely-sliced queries in sequence is doing the thing cell suppression exists to resist, and nothing in the tool surface would show you it happened. Do not point an autonomous agent at this connector to enumerate a space — keep genomic queries deliberate and reviewed.
  • How an aggregate-only connector sits on a row-level cohort tool is undocumented. Helix's press release says the connector hooks directly into Cohort Builder, which stratifies individual patients. Helix does not explain where aggregation is enforced in that path, and we could not establish it either way.
  • Access is gated to agreement-bound partners, so most readers cannot use this connector at all, and licensing the underlying dataset is a separate commercial conversation with Helix.
  • This is research data. Helix positions GenoSphere for research and drug development, and its participant materials frame the network as a research study. Nothing here is a clinical or diagnostic result about any person.

Frequently asked questions

Does the Helix GenoSphere connector return individual-level genetic data?

Helix states twice that it does not. Its connector page says every result is a de-identified aggregate statistic, a count or a percentage over the cohort, and that the connector never returns individual records, genotypes tied to a person, or protected health information. Its July 2026 press release repeats the claim. We could not test it — the endpoint refused us.

What are the five Helix GenoSphere tools?

Anthropic's directory lists get_variant_frequency, check_gene_availability, get_dataset_overview, search_concepts and get_patient_count. All five read. Helix publishes no tool list of its own, so these names come from the directory, but each maps onto one capability Helix describes in prose and no described capability lacks a name.

Whose genomes are in the Helix GenoSphere dataset?

Participants in the Helix Research Network who signed a research consent form. Helix documents that participants agree their coded information may be studied by researchers outside the network, who will not receive directly identifying information, and that participants can withdraw and stop sharing at any time. The cohort exceeds 500,000 exome-sequenced records linked to EHR data.

Why does a Helix GenoSphere query return a suppressed or empty result?

That is the privacy floor working, not a fault. Helix documents that small groups are masked to protect participant privacy, so a low count is withheld rather than reported. Helix also states a zero or empty result means nothing matched within the dataset's scope rather than that the true answer is definitively none.

Can anyone connect to the Helix GenoSphere MCP server?

No. Helix restricts access to named health system and life sciences partners bound by agreement, not the general public. You need a Helix-provisioned account assigned to the connector before sign-in works. Helix states that enabling the connector without a provisioned account returns a message directing you to contact Helix rather than any data.

Can the Helix GenoSphere connector write or delete anything?

No tool name in the listing writes. Helix describes the connector as read-only, Anthropic's directory records its permissions as Read, and all five names are queries — get, check and search verbs. There is no create, update, delete or export verb anywhere in the surface, and no parameter detail was readable to check for a hidden one.

Why does a gene come back as unavailable in Helix GenoSphere?

The queryable panel is a curated subset, not the whole exome. Helix states plainly that it holds exome-wide data beyond the panel, so a gene's absence from the panel does not mean Helix lacks data on it. Helix directs coverage questions for a specific gene to mcp@helix.com rather than treating absence as an answer.

What OAuth scopes does the Helix GenoSphere MCP server request?

Unknown — we could not read them. Every path on the endpoint host, including the RFC 9728 descriptor paths and a nonsense control path, returned a byte-identical AWS load balancer 403 with no www-authenticate header. Helix documents sign-in through its Okta identity provider, but publishes no scope list and the server would not tell us.

Sources

More Healthcare connectors

  • AdisInsight

    Query Springer Nature's drug-pipeline and trial database from an AI agent.

  • AdvancedMD

    Look up patients, find open slots, book appointments, and work denials and remittances in AdvancedMD from your AI agent.

  • AllTrails

    Search AllTrails' trails by place, map bounds or name and pull details and a 7-day trailhead forecast from your AI…

Browse all MCP connectorsClaude and ChatGPT setup guideBrowse AI skills

Product names and logos belong to their owners. Agentman is not affiliated with a connector's maker unless the page says the connector is built and run by Agentman.

Use it in an agent

Put Helix GenoSphere to work.

Connect Helix GenoSphere once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.

Open in Agentman Studio
Call (650) 285-1019Our AI receptionist answers.