Nexonco

Created By
Nexgene-Researcha year ago
A MCP Server for accessing and analyzing clinical evidence data, with flexible search options to support precision medicine and oncology research.
Overview

What is Nexonco?

Nexonco is an advanced MCP Server designed for accessing and analyzing clinical evidence data, specifically from the CIViC (Clinical Interpretation of Variants in Cancer) database, to support precision medicine and oncology research.

How to use Nexonco?

To use Nexonco, set up the server by following the provided setup guides, and utilize the search_clinical_evidence tool to query clinical evidence data based on various parameters such as disease, therapy, and molecular profile.

Key features of Nexonco?

  • Fast and flexible search options for clinical evidence.
  • Ability to filter evidence by disease, therapy, gene, and phenotype.
  • Returns formatted reports with summary statistics and top evidence entries.

Use cases of Nexonco?

  1. Finding predictive evidence for therapies related to specific cancers.
  2. Analyzing clinical evidence for drug efficacy in oncology.
  3. Supporting research in precision medicine by providing detailed evidence reports.

FAQ from Nexonco?

  • Is Nexonco suitable for all types of cancer research?

Yes! Nexonco is tailored for oncology research and can handle various cancer types and related therapies.

  • What are the prerequisites for setting up Nexonco?

You need either uv or Docker and Claude Desktop for MCP integration.

  • Is Nexonco free to use?

Yes! Nexonco is open-source and available for free on GitHub.

Server Config

{
  "mcpServers": {
    "nexonco": {
      "command": "uv",
      "args": [
        "--directory",
        "/full/path/to/nexonco/nexonco",
        "run",
        "server.py"
      ]
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Nexgene-Research
Star
-
Language
-
License
-
Category

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

2 days ago