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.

Cybergenic

REMOTE · CYBERGENIC.IM

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

Available components

0 this week 86 Trust /100

Last scanned (23 hours ago)

Scores higher than 93% of remote servers

Reachable. Last reached 4 Nov 2026.

Category Health and Science

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 Security80
Transport & Reachability100
Schema Quality & AI Usability65
  • AI-judged instruction clarity (excellent).Pass
  • 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. 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 Coverage99
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 97% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 10 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
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.

  • 28 Oct 26 +1
    • Stability: 0.97 → pass security
  • 26 Oct 26 +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.

  • 24 Oct 26 +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.

  • 22 Oct 26 +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.

  • 20 Oct 26 +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.

  • 18 Oct 26 +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.

  • 15 Oct 26 +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.

  • 13 Oct 26 +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.

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 4 Nov 2026 · Probed https://cybergenic.im/mcp?via=mcpregistry

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=cybergenic.im CN=YR2,O=Let's Encrypt,C=US 8 Oct 2026 6 Jan 2027 RSA 2048 SHA256-RSA 574aaa83844579e2efe4d3b55579719a41f
SANs: cybergenic.im
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of cybergenic.im. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
im. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
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
Header Value
strict-transport-security max-age=31536000; includeSubDomains
content-security-policy default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' https://js.stripe.com https://platform.twitter.com; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; img-src 'self' data: blob: https:; media-src 'self' https: blob:; font-src 'self' https://fonts.gstatic.com; connect-src 'self' https://*.supabase.co wss://*.supabase.co https://api.stripe.com; worker-src 'self' blob:; frame-src 'self' https://js.stripe.com https://hooks.stripe.com https://www.youtube-nocookie.com https://www.youtube.com https://player.vimeo.com https://www.loom.com https://www.dailymotion.com https://platform.twitter.com; frame-ancestors 'self' http://localhost:* https://o-mega.ai https://*.o-mega.ai https://founden.ai https://*.founden.ai https://*.founden.co https://*.e2b.app https://*.vercel.app; object-src 'none'; base-uri 'self'
x-content-type-options nosniff
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=(), browsing-topics=()

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://cybergenic.im/mcp?via=mcpregistry Verified 200
http (plaintext) http://cybergenic.im/mcp?via=mcpregistry HTTPS enforced 308 https://cybergenic.im/mcp?via=mcpregistry
MCP tools · 9 exposed · ~1,941 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
chi_square_test ~132

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.

NameTypeReqDescription
tablearrayyesRows of whole-number counts, for example [[20, 15], [30, 35]].

No output schema declared.

No examples provided.

fdr_correction ~205

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.

NameTypeReqDescription
alphanumber–Significance level for counting discoveries. Default 0.05.
family_sizeinteger–Total number of tests run, when larger than the number of p-values supplied.
labelsarray–Optional names for the tests, in the same order as p_values.
p_valuesarrayyesThe raw p-values, one per test.

No output schema declared.

No examples provided.

fisher_exact_test ~260

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.

NameTypeReqDescription
aintegeryesRow 1, column 1 (for two genes: both altered).
alternativestring–Which p-value is the headline and which interval is reported. greater: odds ratio above 1.
bintegeryesRow 1, column 2 (gene A only).
cintegeryesRow 2, column 1 (gene B only).
confidence_levelnumber–Confidence level for intervals, between 0.5 and 0.9999. Default 0.95.
dintegeryesRow 2, column 2 (neither).

No output schema declared.

No examples provided.

gene_partners ~339

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.

NameTypeReqDescription
cancerstring–Optional cancer filter: a name or part of one ('breast', 'colorectal cancer', 'lung') or an abbreviation (NSCLC, LUAD, CRC, PDAC, GBM, UCEC, HCC).
directionstring–Keep only co-occurring or only mutually exclusive partners. Default: either.
genestringyesHGNC gene symbol, for example KRAS, STK11 or CDKN2A (case-insensitive).
limitinteger–Most partners to return. Default 20.
max_qnumber–Largest Benjamini-Hochberg q to include, up to 0.25. Default 0.05.
passing_onlyboolean–Keep only pairs that pass all of the scan's gates (default). False also lists significant pairs that fail one.

No output schema declared.

No examples provided.

get_finding ~138

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.

NameTypeReqDescription
idstringyesA finding id (UUID) or its permalink, https://cybergenic.im/findings/<id>.

No output schema declared.

No examples provided.

get_track_record ~94

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

lookup_gene_pair ~339

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.

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

No output schema declared.

No examples provided.

odds_ratio_relative_risk ~202

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.

NameTypeReqDescription
aintegeryesGroup 1 with the outcome.
bintegeryesGroup 1 without the outcome.
cintegeryesGroup 2 with the outcome.
confidence_levelnumber–Confidence level for intervals, between 0.5 and 0.9999. Default 0.95.
dintegeryesGroup 2 without the outcome.

No output schema declared.

No examples provided.

search_findings ~232

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.

NameTypeReqDescription
kindstring–Keep only one kind of finding.
limitinteger–Results per page. Default 10.
pageinteger––
querystring–Genes, cancers or both, for example 'KRAS pancreatic', 'TP53 breast' or 'NSCLC'. Omit to list everything.
sortstring–recent: newest first; signal: strongest corrected q first; novelty: least studied first; papers: most studied first.
verdictstring–Keep only findings with this verdict.

No output schema declared.

No examples provided.

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.

remote · cybergenic.im

# add to Claude Code
claude mcp add --transport http im-cybergenic-mcp 'https://cybergenic.im/mcp?via=mcpregistry'
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 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.