# Cybergenic (remote · cybergenic.im)

Cancer gene co-occurrence and exclusivity in tumour cohorts, with confound controls and exact tests.

- Trust score: 86/100 (high trust)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `cybergenic.im`: 86/100 (this document), [markdown](https://verifymcp.io/servers/im-cybergenic-mcp/cybergenic.md), [page](https://verifymcp.io/servers/im-cybergenic-mcp/cybergenic)

## Channel facts

- Endpoint: `https://cybergenic.im/mcp?via=mcpregistry`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 65/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 2315 tokens (~257/item across 9 items; 9 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 99/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 97% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the Cybergenic MCP server?

Cybergenic is a hosted endpoint at https://cybergenic.im/mcp?via=mcpregistry, 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.

### Claude

```bash
claude mcp add --transport http im-cybergenic-mcp 'https://cybergenic.im/mcp?via=mcpregistry'
```

### Cursor

```json
{
  "mcpServers": {
    "im-cybergenic-mcp": {
      "url": "https://cybergenic.im/mcp?via=mcpregistry"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "im-cybergenic-mcp": {
      "type": "http",
      "url": "https://cybergenic.im/mcp?via=mcpregistry"
    }
  }
}
```

### Codex

```toml
[mcp_servers.im-cybergenic-mcp]
url = "https://cybergenic.im/mcp?via=mcpregistry"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "im-cybergenic-mcp": {
      "type": "remote",
      "url": "https://cybergenic.im/mcp?via=mcpregistry",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add im-cybergenic-mcp --url 'https://cybergenic.im/mcp?via=mcpregistry' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  im-cybergenic-mcp:
    url: "https://cybergenic.im/mcp?via=mcpregistry"
```

### Netclaw

```json
{
  "McpServers": {
    "im-cybergenic-mcp": {
      "Transport": "http",
      "Url": "https://cybergenic.im/mcp?via=mcpregistry"
    }
  }
}
```

### Vellum

```bash
assistant mcp add im-cybergenic-mcp -t streamable-http -u 'https://cybergenic.im/mcp?via=mcpregistry'
```

### Other

```json
{
  "mcpServers": {
    "im-cybergenic-mcp": {
      "type": "http",
      "url": "https://cybergenic.im/mcp?via=mcpregistry"
    }
  }
}
```

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

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-28 (score 86, +1)

- [security] Stability: 0.97 → pass

### 2026-10-26 (score 85, +1)

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

### 2026-10-24 (score 84, +1)

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

### 2026-10-22 (score 83, +1)

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

### 2026-10-20 (score 82, +1)

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

### 2026-10-18 (score 81, +1)

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

### 2026-10-15 (score 80, +1)

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

### 2026-10-13 (score 79, +1)

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

## MCP tools (9)

### `lookup_gene_pair` (~339 tokens)

Look up a gene pair across tumour cohorts

Measured co-alteration statistics for two genes in every tumour cohort where Cybergenic's discovery scan tested the pair: tumours with both genes altered against the number expected, odds ratio, p-value and Benjamini-Hochberg q over that cohort's whole family of tested pairs, the confound control applied (molecular subtype, lineage or histology strata, with mutation burden conditioned on), and whether the pair passes the scan's own discovery gates. A direction is stated only where it is significant, consistent and at least a two-fold odds ratio, and cohorts are also counted by independent patient source (the two MSK cohorts overlap). Also returns Cybergenic's published findings on the pair with their verdicts and permalinks. Use it to answer whether two genes' driver mutations co-occur or are mutually exclusive in patient tumours. Associations in tumour sequencing, not causal or clinical evidence.

Input parameters:

- `cancer` (string): Optional cancer filter: a name or part of one ('breast', 'colorectal cancer', 'lung') or an abbreviation (NSCLC, LUAD, CRC, PDAC, GBM, UCEC, HCC).
- `gene_a` (string, required): HGNC gene symbol, for example KRAS, STK11 or CDKN2A (case-insensitive).
- `gene_b` (string, required): HGNC gene symbol, for example KRAS, STK11 or CDKN2A (case-insensitive).
- `max_cohorts` (integer): Cohorts returned in full detail, strongest first (default 12); every other tested cohort still comes back as a one-line row.

### `gene_partners` (~339 tokens)

Find a gene's strongest co-alteration partners

The genes whose driver mutations co-occur with, or are mutually exclusive with, a given gene in patient tumours, strongest first by Benjamini-Hochberg q, from every pair Cybergenic's discovery scan tested: one row per partner and independent patient source, with the tumours, observed and expected co-alteration and the odds ratio. By default only pairs the scan's own gates keep (significant, a real effect size, a consistent direction, enough tumours); set passing_only to false to include significant pairs that fail a gate. Filter by cancer, direction and q threshold. Use it to survey a gene's co-alteration landscape before looking up a specific pair. Associations in tumour sequencing, not causal or clinical evidence.

Input parameters:

- `cancer` (string): Optional cancer filter: a name or part of one ('breast', 'colorectal cancer', 'lung') or an abbreviation (NSCLC, LUAD, CRC, PDAC, GBM, UCEC, HCC).
- `direction` (string): Keep only co-occurring or only mutually exclusive partners. Default: either.
- `gene` (string, required): HGNC gene symbol, for example KRAS, STK11 or CDKN2A (case-insensitive).
- `limit` (integer): Most partners to return. Default 20.
- `max_q` (number): Largest Benjamini-Hochberg q to include, up to 0.25. Default 0.05.
- `passing_only` (boolean): Keep only pairs that pass all of the scan's gates (default). False also lists significant pairs that fail one.

### `search_findings` (~232 tokens)

Search Cybergenic's published findings

Search Cybergenic's published findings: gene-pair co-occurrence and mutual exclusivity, survival associations, CRISPR gene dependencies and single-gene leads, each with the verdict the engine measured (strengthened, weakened, inconclusive, artifact risk or novel lead) and the reason for it. The query works like the site's search: exact gene symbols, cancer names or abbreviations (NSCLC, CRC, PDAC, TNBC), or both, and every term must match. Returns permalinks to cite and ids for get_finding.

Input parameters:

- `kind` (string): Keep only one kind of finding.
- `limit` (integer): Results per page. Default 10.
- `page` (integer)
- `query` (string): Genes, cancers or both, for example 'KRAS pancreatic', 'TP53 breast' or 'NSCLC'. Omit to list everything.
- `sort` (string): recent: newest first; signal: strongest corrected q first; novelty: least studied first; papers: most studied first.
- `verdict` (string): Keep only findings with this verdict.

### `get_finding` (~138 tokens)

Read one finding's full record

The full record of one Cybergenic finding, by id or permalink: what was measured and in which cohort, the statistics (the 2x2 table, odds ratio, p and q), the verdict and why, the confound checks, how many papers mention the genes together, CRISPR dependency and survival facts when measured, the prediction locked for it in the hash-chained registry, the same question in other cohorts, and a citation. The hypothesis text is a model-written annotation, not evidence.

Input parameters:

- `id` (string, required): A finding id (UUID) or its permalink, https://cybergenic.im/findings/<id>.

### `get_track_record` (~94 tokens)

Read the engine's live track record

Cybergenic's live track record: how many predictions it has locked in its hash-chained registry before re-testing them, how many replicated in an independent cohort against matched controls (including the less-studied-pair subset), and how many findings currently pass every check as both strong and overlooked. Read it before describing how reliable the engine is; it states its own limits, including whether the replication comes from well-known biology.

### `fisher_exact_test` (~260 tokens)

Fisher's exact test (2x2)

Fisher's exact test for a 2x2 table [[a, b], [c, d]]: two-sided and both one-sided p-values (computed in log space, so a tiny p keeps its real exponent), the sample odds ratio, and the conditional maximum-likelihood odds ratio with its exact confidence interval (what R's fisher.test reports). For two genes: a = tumours with both altered, b = gene A only, c = gene B only, d = neither. Up to 100,000 observations. The same implementation as cybergenic.im/tools/fisher-exact-test.

Input parameters:

- `a` (integer, required): Row 1, column 1 (for two genes: both altered).
- `alternative` (string): Which p-value is the headline and which interval is reported. greater: odds ratio above 1.
- `b` (integer, required): Row 1, column 2 (gene A only).
- `c` (integer, required): Row 2, column 1 (gene B only).
- `confidence_level` (number): Confidence level for intervals, between 0.5 and 0.9999. Default 0.95.
- `d` (integer, required): Row 2, column 2 (neither).

### `chi_square_test` (~132 tokens)

Chi-square test of independence

Pearson chi-square test of independence for an r x c table of counts (2x2 up to 10x10), with Yates' correction for 2x2 tables and the G-test: statistic, degrees of freedom, p-value, expected counts, adjusted residuals, Cramér's V, whether Cochran's rule for the approximation holds, and Fisher's exact test when the table is 2x2. Empty rows and columns are dropped and reported.

Input parameters:

- `table` (array, required): Rows of whole-number counts, for example [[20, 15], [30, 35]].

### `odds_ratio_relative_risk` (~202 tokens)

Odds ratio, relative risk and NNT

Effect sizes for a 2x2 table [[a, b], [c, d]] whose rows are two groups and whose columns are outcome yes and no: the odds ratio (Woolf interval, and the conditional exact interval), the relative risk (Katz interval), the risk difference (Newcombe interval) and the number needed to treat, at the chosen confidence level, plus Fisher's exact p. A zero cell applies the Haldane-Anscombe correction to the Woolf and Katz estimates, and the result says so.

Input parameters:

- `a` (integer, required): Group 1 with the outcome.
- `b` (integer, required): Group 1 without the outcome.
- `c` (integer, required): Group 2 with the outcome.
- `confidence_level` (number): Confidence level for intervals, between 0.5 and 0.9999. Default 0.95.
- `d` (integer, required): Group 2 without the outcome.

### `fdr_correction` (~205 tokens)

FDR and multiple-testing correction

Multiple-testing correction for a list of p-values: Benjamini-Hochberg q-values and Benjamini-Yekutieli, Holm, Hochberg and Bonferroni adjusted p-values, the number of discoveries at alpha for each method, and the Benjamini-Hochberg cutoff rank. Pass family_size when more tests were run than the p-values supplied (for example only the top hits were kept). Up to 10,000 p-values per call; the same implementation as cybergenic.im/tools/fdr-correction, verified against R p.adjust and statsmodels.

Input parameters:

- `alpha` (number): Significance level for counting discoveries. Default 0.05.
- `family_size` (integer): Total number of tests run, when larger than the number of p-values supplied.
- `labels` (array): Optional names for the tests, in the same order as p_values.
- `p_values` (array, required): The raw p-values, one per test.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/im-cybergenic-mcp/cybergenic#diagnostics

## Score history

- 2026-11-05: 86
- 2026-11-04: 86
- 2026-11-03: 86
- 2026-11-02: 86
- 2026-11-01: 86
- 2026-10-31: 86
- 2026-10-30: 86
- 2026-10-29: 86
- 2026-10-28: 86
- 2026-10-27: 85
- 2026-10-26: 85
- 2026-10-25: 84
- 2026-10-24: 84
- 2026-10-23: 83
- 2026-10-22: 83
- 2026-10-21: 82
- 2026-10-20: 82
- 2026-10-19: 81
- 2026-10-18: 81
- 2026-10-17: 80
- 2026-10-16: 80
- 2026-10-15: 80
- 2026-10-14: 79
- 2026-10-13: 79
- 2026-10-12: 78
- 2026-10-10: 77
- 2026-10-06: 75
- 2026-10-04: 74
- 2026-10-03: 74
- 2026-10-02: 73

## Common questions

### What is the Cybergenic MCP server?

Cybergenic is an MCP server listed in the public MCP registry as im.cybergenic/mcp. Cancer gene co-occurrence and exclusivity in tumour cohorts, with confound controls and exact tests. This page covers its hosted endpoint (https://cybergenic.im/mcp?via=mcpregistry).

### Is the Cybergenic MCP server safe to use?

Cybergenic scores 86 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 Cybergenic MCP server expose?

Cybergenic exposes 9 tools: lookup_gene_pair, gene_partners, search_findings, get_finding, get_track_record, and 4 more. Their descriptions and schemas cost roughly 1,941 tokens of context every time the server is loaded.

### Does the Cybergenic MCP server require authentication?

No. We connected to Cybergenic without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Cybergenic MCP server still maintained?

Cybergenic is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://cybergenic.im/mcp?via=mcpregistry
- Website: https://cybergenic.im/connect?utm_source=mcpregistry&utm_medium=listing&utm_campaign=mcp-agent-channel
- Changelog RSS feed: https://verifymcp.io/servers/im-cybergenic-mcp/cybergenic.xml
- Changelog JSON feed: https://verifymcp.io/servers/im-cybergenic-mcp/cybergenic.json
- HTML version of this page: https://verifymcp.io/servers/im-cybergenic-mcp/cybergenic