Cybergenic

im.cybergenicPublished by cybergenic.imOfficial publisherv1.0.0Updated Oct 24, 2026

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

VerifiedStreamable HTTPWeb executableData & Analytics

Overview

AI-generated overview

A remote MCP server for exploring cancer gene co-occurrence and exclusivity in tumour cohorts, with confound controls and exact tests.

What you can do
The manifest lists no tools, so capabilities are known only from the registry description. It is presented as a way to examine whether cancer genes occur together or exclude each other across tumour cohorts. It is described as applying confound controls and exact statistical tests to that analysis. No further detail on specific operations is provided.
When to use it
Consider it when an assistant needs to look at cancer gene co-occurrence or mutual exclusivity patterns in tumour cohort data, with statistical testing and confound control in mind. It is a specialised research-oriented service rather than a general-purpose tool.
Requirements
It runs as a remote streamable HTTP endpoint at the provider's host, so network access is needed. The manifest declares no authentication, environment variables, headers or packages.
Before you install
The manifest declares no authentication, so it is unclear what data or access controls apply; confirm with the provider before relying on it. No tools are listed, so the exact operations and any data sent to the service cannot be verified from the available information.

Installation

In SourceWeft

  1. Open Cybergenic in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/im.cybergenic%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

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

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.0.0LatestSep 28, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.