Skip to content
Back to the index

nci-evs

pipeworx.ioInfrastructure

No liveness check has reached it yet; it has been in the index since 10 Oct 2026. How this is checked

nci-evs is an HTTP JSON-RPC MCP server exposing tools for searching NCI Enterprise Vocabulary Services terminologies and retrieving individual concepts. It supports NCIt and other biomedical vocabularies, including cross-terminology mappings used by clinical and research systems.

Inferred · not functionally tested

WebAPICloud-managed
nci-evs preview
Visit pipeworx.io

Overview

6 features

Purpose: Querying authoritative NCI biomedical terminologies and retrieving standardized concept codes and definitions.

Inferred · not functionally tested

Audience: clinical researchers, biomedical developers, and healthcare data teams

Inferred · not functionally tested

Functions: data_extraction

Inferred · not functionally tested

Interfaces: API: indicated (inferred, not tested) · MCP: indicated (inferred, not tested) · CLI: unknown · Self-hosting: unknown

Recorded constraints: pricing: unknown · license: Proprietary · platforms: WEB · deployment: browser, api_only, cloud_managed

Constraint provenance is unknown; confirm requirements with the publisher.

Record sources: gateway.pipeworx.io. These links do not verify the individual claims.

nci-evs is an API design, testing & docs project. Inferred · not functionally tested: It focuses on querying authoritative NCI biomedical terminologies and retrieving standardized concept codes and definitions. Inferred · not functionally tested: It is built as a B2B product for clinical researchers, biomedical developers, and healthcare data teams. Basis unknown · not verified: nci-evs is available on the web and API.

Behind nci-evs is Pipeworx. Inferred · not functionally tested: Among its 6 catalogued features are concept search, concept lookup, and terminology listing. Inferred · not functionally tested: Catalogued interfaces include an MCP server and a public API.

Summary written by a language model from the project’s public pages.

Tasks: Inferred · not functionally tested

  • Concept search
  • Concept lookup
  • Terminology listing
  • Version lookup
  • Cross-terminology maps
  • Synonym retrieval

Topics: Inferred · not functionally tested

Tags
nci-thesaurusbiomedical-terminologyclinical-codesmcp-server

JSON profile · Text profile · Access guide

Built with & integrations

Hosting
Cloudflare
Connectors
MCPAPI
Runs on
BrowserAPI-onlyCloud-managed
Detected from
Cloudflare
cf-ray header

Trust & compliance

Public signals
HTTPS

Indexing history

1

What PulseGate has recorded for this listing

  1. Indexed10 Oct · 00:02 UTC
    Nci Evs seen via MCP Registry (official)
    Source: MCP Registry (official) · Open

Frequently asked questions about nci-evs

What is nci-evs?
Inferred · not functionally tested: Nci-evs focuses on querying authoritative NCI biomedical terminologies and retrieving standardized concept codes and definitions. It is catalogued under API design, testing & docs on PulseGate.
Who should use nci-evs?
Inferred · not functionally tested: nci-evs is a B2B product built for clinical researchers, biomedical developers, and healthcare data teams.
What platforms does nci-evs run on?
Basis unknown · not verified: nci-evs runs on the web and API.
Is nci-evs still maintained?
Unverified. nci-evs has not been re-checked since it entered the index, so there is no finding either way — and only a positive finding would say otherwise.
Who develops nci-evs?
nci-evs is developed by Pipeworx.
Does nci-evs have an API or integrations?
Inferred · not functionally tested: Yes — nci-evs exposes an MCP server and a public API.

Similar projects

Closest matches by what these projects do