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.

Civic

NPM · @PIPEWORX/MCP-CIVIC · 2 COMPONENTS

CIViC — Clinical Interpretation of Variants in Cancer.

+4 this week 83 Trust /100

Last scanned (10 hours ago)

Scores higher than 76% of npm servers

Category Health and Science

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-civic). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 5 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability66
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 759 tokens (~189/item across 4 items; 4 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 Management23
  • Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 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.

  • 5 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

  • 3 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

  • 1 Nov 26 +1
    • Security disclosure: unverified → fail ▼ functional
  • 31 Oct 26 0
    • Security disclosure: fail → unverified ▼ functional
    • Package version: 0.2.0 → 0.2.1 functional
  • 30 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 0 to 3. That category is still filling its 30-day observation window: 0 days of observed history at the previous scan, 1 at this one. The score rises as the window fills, whether or not the server changes.

  • 29 Oct 26 79

    First indexed and scored.

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 5 Nov 2026 · Analysed npm/@pipeworx/mcp-civic@0.2.1

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo pipeworx-io/mcp-civic
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/pipeworx-io/mcp-civic/.github/workflows/publish.yml@refs/heads/main
Rekor log index 3606807848
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:52e438718681c40dd538ea1460c12e3a103603eb581e43aca4297c6b3c61deab83d5dd1880eaeedd532d0051624a5816a5ed1da6f40cab0601ad3ed86

Background: How many MCP packages publish verified provenance →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 4 exposed · ~708 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
civic_assertions ~161

CIViC assertions — the curated, AMP/ASCO/CAP-tiered and ACMG-classified clinical summaries that roll up multiple evidence items into a single actionable statement, including FDA companion-test and regulatory-approval flags. AUTHORITATIVE for "is this variant clinically actionable in this disease, and at what tier". Filter by molecular profile, disease or therapy.

NameTypeReqDescription
diseasestring–Disease name substring (e.g. "Melanoma")
limitnumber–Max assertions to return, 1-100 (default 25)
molecular_profilestring–Molecular profile name, e.g. "BRAF V600E"
therapystring–Therapy name substring (e.g. "Vemurafenib")

No output schema declared.

No examples provided.

civic_gene_variants ~130

Curated variants of a cancer gene in CIViC — the specific alterations (missense, fusion, amplification, exon-level) that have published clinical interpretations, each with its evidence count, associated diseases and therapies. AUTHORITATIVE for "which variants of this gene are clinically actionable". Pass the gene symbol.

NameTypeReqDescription
genestringyesGene symbol (e.g. "BRAF")
limitnumber–Max variants to return, 1-100 (default 25)
variant_namestring–Optional substring filter on the variant name (e.g. "V600")

No output schema declared.

No examples provided.

civic_search_genes ~142

Find cancer genes and fusions in CIViC by name or symbol, with how much curated clinical evidence each carries (variant count, evidence-item count, assertion count). AUTHORITATIVE starting point for "what does CIViC know about gene X" — CIViC is the open expert-curated knowledgebase of clinically actionable somatic cancer variants. Returns the numeric CIViC feature id you pass to the other tools.

NameTypeReqDescription
limitnumber–Max features to return, 1-100 (default 25)
querystringyesGene symbol or partial name (e.g. "BRAF", "EGFR", "ALK")

No output schema declared.

No examples provided.

civic_variant_evidence ~275

Individual CIViC evidence items for a molecular profile — the graded, source-linked statements that a variant predicts response or resistance to a therapy, carries prognostic or diagnostic weight, or is oncogenic. Each item carries evidence type, level (A-E), direction, significance, 1-5 star rating, disease, therapies and the PubMed/ASCO source. AUTHORITATIVE for the clinical evidence behind a variant claim, rather than a summary of it. Pass a molecular profile name such as "BRAF V600E", or a numeric CIViC variant id.

NameTypeReqDescription
diseasestring–Filter by disease name substring (e.g. "Melanoma")
evidence_typestring–Filter: PREDICTIVE | DIAGNOSTIC | PROGNOSTIC | PREDISPOSING | ONCOGENIC | FUNCTIONAL
limitnumber–Max evidence items to return, 1-100 (default 25)
molecular_profilestring–Molecular profile name, e.g. "BRAF V600E" or "EGFR L858R"
therapystring–Filter by therapy name substring (e.g. "Vemurafenib")
variant_idnumber–Numeric CIViC variant id (alternative to molecular_profile)

No output schema declared.

No examples provided.

Install

How do I install the Civic MCP server?

Civic runs locally as an npm package, launched with npx -y @pipeworx/mcp-civic. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @pipeworx/mcp-civic

# add to Claude Code
claude mcp add pipeworx-io-civic -- npx -y @pipeworx/mcp-civic
Common questions

What is the Civic MCP server?

Civic is an MCP server listed in the public MCP registry as io.github.pipeworx-io/civic. CIViC, Clinical Interpretation of Variants in Cancer. This page covers its npm package (@pipeworx/mcp-civic).

Is the Civic MCP server safe to use?

Civic scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Civic MCP server expose?

Civic exposes 4 tools: civic_search_genes, civic_gene_variants, civic_variant_evidence, civic_assertions. Their descriptions and schemas cost roughly 708 tokens of context every time the server is loaded.

Is the Civic MCP server still maintained?

Civic is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the Civic MCP server under?

Civic declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.