mcpbeat

Genomic Intelligence MCP Server

ai.genomicintelligence/genomic-intelligence
answering

Genomic Intelligence is answering right now. Last checked 12 min ago. It exposes 15 tools.

Hosted DNA language models: promoter, splice, enhancer, chromatin, expression, annotation

Uptime history 39 hours of history
39 hours agonow
100.0%
Uptime 24h
91 of 91 checks
15
Tools
read from the server
589 ms
Response time
average over 24h
open, no key
Access
streamable-http

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 12 min ago.

run in your terminal
claude mcp add genomic-intelligence --transport http https://mcp.genomicintelligence.ai/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "genomic-intelligence": {
      "url": "https://mcp.genomicintelligence.ai/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.genomic-intelligence]
url = "https://mcp.genomicintelligence.ai/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "genomic-intelligence": {
      "url": "https://mcp.genomicintelligence.ai/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "genomic-intelligence": {
      "url": "https://mcp.genomicintelligence.ai/mcp"
    }
  }
}

Available tools 15

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

predict
predict_chromatin
Chromatin annotation across 919 features (G0 DeepSEA). Up to 500,000 bp.
predict_enhancer
Predict enhancer activity (G0 DeepSTARR). Up to 500,000 bp.
predict_expression
Predict a gene's expression from a TSS-centred input window. Expression is cell-type-specific, so `description` (cell type / assay context, e.g. 'K562 cell line') is REQUIRED — the API rejects requests without it. Requires exactly 9,198 bp centred on the TSS; call fetch_gene_for_expression(gene) to get a correctly-prepared handle. For a raw region or whole gene where you don't already have that window, use find_genes_and_predict_expression (it finds the genes for you).
predict_promoter
Predict promoter regions (G0). Up to 500,000 bp. Returns the {data, meta} envelope: data.regions lists predicted promoters with start/end/score.
predict_splice
Predict splice donor/acceptor sites (G0 BigBird). Up to 500,000 bp.
genes
find_genes
Find genes (transcript intervals) in a genomic region (async, ~8-25s). Gene-finding: detects transcript boundaries (TSS + PolyA) and returns one interval per predicted transcript — start/end, strand, a confidence score, and predicted TSS/PolyA positions (BED-style feature intervals, not free-text notes). Use this for "what genes are here", "find / locate genes", or "annotate this region". Each transcript also carries its type (mRNA/lnc_RNA) and internal exon/intron/CDS structure in `exons`/`introns`/`cds` arrays, plus a browser-ready GFF3 track in `data.formats.gff3`. To get each gene's *expression* from a raw region, use find_genes_and_predict_expression instead — expression needs a per-gene TSS window, so predict_expression cannot run on a whole region. Submits an async job internally. With wait=True (default), blocks and streams progress, then returns the result {data, meta} — it never returns a job_id on this path. (If a generous block ceiling is exceeded it returns a timeout error, not a job handle.) With wait=False (detached), returns {data: {job_id, status: 'submitted'}} immediately — poll it with get_job.
find_genes_and_predict_expression
Find genes in a sequence, then predict each gene's expression (composite). Server-side chaining in ONE call: finds genes (transcript intervals, with their TSS) in the sequence, then predicts expression off each discovered TSS in the given experimental context. This is the right tool whenever you want expression for a raw region or sequence — e.g. "find the genes in chr8:… and predict their expression in K562". You cannot call predict_expression on a whole region, because it needs a single per-gene 9,198 bp TSS window; this tool handles that for you. Runs async internally at every size (the annotate stage is slow even for small inputs), so progress always streams. With wait=True (default), blocks and streams progress, then returns the result {data, meta} — it never returns a job_id on this path. With wait=False (detached), returns {data: {job_id, status: 'submitted'}} immediately — poll it with get_job. Because it ends in expression, `description` (cell type / assay context) is REQUIRED.
ensembl
fetch_ensembl_sequence
Fetch a gene's reference sequence from Ensembl and store it. Returns a handle ({ref, name, length, preview, ...}). Pass the `ref` to predict_* tools — the bases stay server-side. For expression, use fetch_gene_for_expression instead (it prepares the TSS-centred window that model needs).
gene
fetch_gene_for_expression
Fetch a gene's sequence prepared for expression prediction. Resolves the gene's TSS via Ensembl and returns the exact TSS-centred window the expression model needs, as a handle to pass to predict_expression(sequence_ref=...).
job
get_job
Poll an async job once. Returns the {data, meta} result if complete, a progress envelope if still running, or an error envelope if it failed.
jobs
list_jobs
List the caller's recent async jobs (also available as gi://jobs/recent).
load
load_demo_sequence
Load a bundled demo reference sequence and return a handle. The server ships one curated, task-correct positive control per task (list them via the gi://sequences resource) — e.g. `expression_hbb_k562` is a ready-to-use K562 expression window for predict_expression. Stores the demo and returns a handle to pass to a predict_* tool: no Ensembl fetch, no quota. Handy for smoke-testing a prediction end-to-end.
models
list_models
List available models for a task. Use to discover model ids before passing one as the `model` argument to a predict tool. The same catalog is also available as the resource `gi://models`.
region
fetch_region
Fetch a genomic region by coordinates from Ensembl and store it. For "find the genes in chr8:127,680,000-127,800,000"-style requests: resolves a coordinate range to reference sequence and returns a handle ({ref, name, length, ...}) to pass to find_genes / predict_* — the bases stay server-side. Plus strand by default, which is what the gene-finder expects. For a gene by name use fetch_ensembl_sequence; for expression use fetch_gene_for_expression.
store
store_inline_sequence
Store a human-pasted sequence and return a handle to re-use it. For a sequence you've already pasted into the conversation, this gives back a short handle so you can run several tasks on it without re-pasting the bases in each predict_* call. Note that the full sequence still passes through the LLM on THIS call — it does not save context on its own. For large sequences, prefer fetch_ensembl_sequence / fetch_gene_for_expression / load_local_fasta, which acquire the bases server-side and never round-trip them.

Endpoints

URLTransportStateLatencyChecked
https://mcp.genomicintelligence.ai/mcp streamable-http answering 584 ms 12 min ago

Genomic Intelligence — questions

Answers built from our own checks of this server.

What can Genomic Intelligence do?
It exposes 15 tools, read directly from the server on our last check. Among them: fetch_ensembl_sequence, fetch_gene_for_expression, fetch_region, find_genes, find_genes_and_predict_expression, get_job and 9 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
What is Genomic Intelligence mostly used for?
Its tools cluster around predict and genes. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.
Is Genomic Intelligence working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 589 ms. The bar chart above shows every period we have measured.
How do I connect Genomic Intelligence?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Genomic Intelligence need an API key?
No. Genomic Intelligence completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 15 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Genomic Intelligence?
It answers our handshake in 589 ms on average, which is faster than 17% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.