Server data from the Official MCP Registry
CIViC — Clinical Interpretation of Variants in Cancer.
About
CIViC — Clinical Interpretation of Variants in Cancer.
Remote endpoints: streamable-http: https://gateway.pipeworx.io/civic/mcp
Security Report
Valid MCP server (1 strong, 1 medium validity signals). No known CVEs in dependencies. Package registry verified. Imported from the Official MCP Registry. Trust signals: trusted author (2296/2298 approved).
48 tools verified · Open access · 1 issue found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
Permissions Required
This plugin requests these system permissions. Most are normal for its category.
What You'll Need
Set these up before or after installing:
Environment variable: PIPEWORX_API_KEY
How to Install & Connect
Available as Local & Remote
This plugin can run on your machine or connect to a hosted endpoint. during install.
Documentation
View on GitHubFrom the project's GitHub README.
@pipeworx/civic
Expert-curated clinical interpretation of cancer variants from CIViC — which somatic alterations are clinically actionable, in which disease, with which therapy, and the graded published evidence behind each claim.
Part of Pipeworx — an MCP gateway connecting AI agents to 1863+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.
Tools
civic_search_genes(query, limit?)— cancer genes and fusions by name, with variant / evidence / assertion counts and the CIViC feature id.civic_gene_variants(gene, variant_name?, limit?)— the curated variants of a gene, with associated diseases and therapies.civic_variant_evidence(molecular_profile | variant_id, evidence_type?, disease?, therapy?, limit?)— individual evidence items with type, level A-E, direction, significance, 1-5 star rating and the PubMed/ASCO source.civic_assertions(molecular_profile? | disease? | therapy?, limit?)— the AMP/ASCO/CAP-tiered rollups, with FDA companion-test and regulatory-approval flags, ACMG codes and NCCN guideline.
Auth
Keyless. Public GraphQL endpoint; CIViC's content is CC0.
Data sources
- https://civicdb.org/api/graphql — POST,
{query, variables}.
Things that will otherwise cost you an afternoon:
- An explicitly null variable is a FILTER, not an absent filter — and it
returns HTTP 200. Measured 2026-09-17:
evidenceItems(molecularProfileName: "BRAF V600E")reports 249 matches; addingvariantId: nullreports 0,diseaseName: nullreports 245,therapyName: nullreports 313. Unset filters must be omitted from the variables map entirely.omitNulls()insrc/index.tsexists for exactly this and removing it produces a silent zero. browseVariants.totalCountandbrowseFeatures.totalCountignore their own filter arguments.browseVariants(featureName: "BRAF")and an unfilteredbrowseVariantsboth report 5029, the whole catalogue.evidenceItemsandassertionsDO filter their totalCount. This pack only reports the count for the two that mean it.descriptionon theBrowseFeaturetype 500s the entire query. It is in the schema and it is not callable. The gene summary lives on theGenetype, which is whycivic_search_genesmakes a second call.genestakesentrezSymbols/entrezIds, notname. Free-text gene search isbrowseFeatures(featureName:)(substring, unranked — this pack re-ranks exact matches first) orfeatureTypeahead(queryTerm:).- Evidence and assertion
statuscan beSUBMITTEDas well asACCEPTED; a submitted item has not been through CIViC review yet.
Quick Start
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"civic": {
"url": "https://gateway.pipeworx.io/civic/mcp"
}
}
}
What this endpoint actually serves
tools/list at https://gateway.pipeworx.io/civic/mcp returns the tools in the table
above plus the shared Pipeworx meta-tools — ask_pipeworx,
discover_tools, search_within, remember/recall and the rest of the
gateway-wide set. So the tool count you see is larger than this table: a
single-pack endpoint currently lists roughly 30 shared tools alongside the
pack's own. The connection's initialize response states its exact scope, and
is the authoritative answer for a given day.
This is deliberate, not multiplexing by accident. The meta-tools are what let a
scoped connection answer a question this pack does not cover — via
ask_pipeworx, which routes across the whole catalog — without you adding a
second MCP server. There is currently no way to mount a pack endpoint without
them; if the extra schemas cost you more context than the routing is worth,
connect to the full gateway once rather than to several pack endpoints.
Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:
{
"mcpServers": {
"pipeworx": {
"url": "https://gateway.pipeworx.io/mcp"
}
}
}
Both URLs reach the same gateway and the same 1863+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
No MCP client? Call it over HTTP
curl -X POST https://gateway.pipeworx.io/v1/tools/civic_search_genes \
-H 'Content-Type: application/json' \
-d '{"query":"BRAF","limit":5}'
No account needed for the first calls. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/civic_search_genes. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.
Run it from npm
@pipeworx/mcp-civic is a local stdio bridge to the Pipeworx gateway: your MCP client
starts it with npx, and it forwards every call to the same
https://gateway.pipeworx.io/civic/mcp endpoint shown above. It needs network access;
there is no offline mode.
{
"mcpServers": {
"civic": {
"command": "npx",
"args": ["-y", "@pipeworx/mcp-civic"]
}
}
}
Without a key it calls anonymously, capped at 50 calls a day. A free account
raises that to 200 a day: get a key at https://pipeworx.io/signup and add
"env": { "PIPEWORX_API_KEY": "<your key>" } to the server entry.
The key is sent as a Bearer token, the same way a hosted connection sends it,
so calls are metered and billed exactly as they are there.
It lists only this pack's tools by default. Set PIPEWORX_META_TOOLS=1 to
also list ask_pipeworx and the other gateway-wide tools.
Behind an HTTPS proxy: Node's built-in fetch does not read HTTPS_PROXY by
default. Newer Node releases honour it when NODE_USE_ENV_PROXY=1 is set; check
your Node version's documentation.
Using with ask_pipeworx
Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:
ask_pipeworx({ question: "your question about Civic data" })
The gateway picks the right tool and fills the arguments automatically.
More
License
MIT
Reviews
No reviews yet
Be the first to review this server!
More Developer Tools MCP Servers
Rea
Freeby Morluto · Developer Tools
Reverse engineer anything from your terminal or agent with one CLI and MCP server.
Paperclip
Freeby Paperclipai · Developer Tools
Trending hip-hop artist momentum scores across four cultural dimensions.
Scrapling
Freeby D4Vinci · Developer Tools
Web scraping with stealth HTTP, real browsers, and Cloudflare bypass. CSS selectors supported.
Git
Freeby Modelcontextprotocol · Developer Tools
Read, search, and manipulate Git repositories programmatically
Toleno
Freeby Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.
MCP Marketplace
Freeby mcp-marketplace · Developer Tools
Search and install MCP servers from inside your AI client.
