Clinicaltables
NPM · @PIPEWORX/MCP-CLINICALTABLES · 2 COMPONENTS
NIH Clinical Tables Search Service MCP.
Available components
Last scanned (3 hours ago)
Scores higher than 55% of npm servers
Category Health and Science
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 & Transparency71
- Repository presence not verified: we could not reach the forge to check. This is a gap on our side, not a finding about the repository. View diagnostics → Unverified
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-clinicaltables). 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 Usability62
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2437 tokens (~243/item across 10 items; 10 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 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 11 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
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 −4
- Provenance: pass → unverified ▼ security
- 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 +15
- Malware scan: unverified → pass ▲ security
- 31 Oct 26 −14
- Malware scan: pass → unverified ▼ security
- Package version: 0.2.0 → 0.2.1 functional
- 29 Oct 26 79
First indexed and scored.
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-clinicaltables@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-clinicaltables |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-clinicaltables/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3612108366 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:e459449a0751ffea03d18ae072177a4fc1b2261ea42c41a9916d217163f7af61c4ce6e0a3550d132d6eb4d1422d2f938d911a0ab64e499a650972dd55 |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
conditions ~223
"What is [condition]" / "look up medical condition by name" / "find a disease called [X]" / "patient-friendly medical term for [Y]" — search the NLM patient-friendly medical conditions vocabulary (~700 common conditions written for lay readers). Returns canonical names like "Migraine", "Type 2 diabetes". Use for symptom-to-condition lookup, intake forms, or simplifying clinical text for patients.
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | – | Maximum matches to return. Default 7, max 500. Use 1–3 for typeahead UX, 20–50 for browsing. |
| df | string | – | Comma-separated display fields to use in the `displays` array. Default varies per table; usually the canonical name. |
| ef | string | – | Comma-separated extra fields to include per match. Field names vary per table; check NLM docs at clinicaltables.nlm.nih.gov. |
| terms | string | yes | Search query — prefix/contains match against canonical names. Whitespace-split into AND tokens. Example: "migraine". |
No output schema declared.
No examples provided.
disease_names ~245
"UMLS code for [disease]" / "clinical name for rare disease [X]" / "look up a syndrome by name" / "find CUI for [condition]" — search the NLM Disease Names vocabulary (UMLS-derived, broader than `conditions`; includes rare diseases, syndromes, clinical terminology, ~12k entries). Returns UMLS CUIs (e.g., C0011860) plus canonical names. Use when you need clinical-grade vocabulary linkage rather than patient-friendly labels.
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | – | Maximum matches to return. Default 7, max 500. Use 1–3 for typeahead UX, 20–50 for browsing. |
| df | string | – | Comma-separated display fields to use in the `displays` array. Default varies per table; usually the canonical name. |
| ef | string | – | Comma-separated extra fields to include per match. Field names vary per table; check NLM docs at clinicaltables.nlm.nih.gov. |
| terms | string | yes | Search query — prefix/contains match against canonical names. Whitespace-split into AND tokens. Example: "amyotrophic lateral sclerosis". |
No output schema declared.
No examples provided.
drugs ~289
"Drug name lookup" / "find prescription [X]" / "medication autocomplete" / "RxCUI for [drug]" / "what does [pill] treat" / "available strengths for [drug]" — search RxTerms (NLM prescribing-vocabulary derived from RxNorm, ~22k drug names with route/strength). Returns names like "Aspirin (Chewable)", "Lisinopril (Oral Pill)". Use for prescription entry, drug name autocomplete, or as a stepping-stone to RxNorm RxCUI lookups. Pass ef="STRENGTHS_AND_FORMS,RXCUIS" to include dosage strengths and RxNorm IDs.
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | – | Maximum matches to return. Default 7, max 500. Use 1–3 for typeahead UX, 20–50 for browsing. |
| df | string | – | Comma-separated display fields to use in the `displays` array. Default varies per table; usually the canonical name. |
| ef | string | – | Comma-separated extra fields to include per match. Known fields: STRENGTHS_AND_FORMS,RXCUIS,DISPLAY_NAME_SYNONYM,IS_RETIRED. |
| terms | string | yes | Search query — prefix/contains match against canonical names. Whitespace-split into AND tokens. Example: "aspirin". |
No output schema declared.
No examples provided.
icd10cm ~238
"What's the ICD-10 code for [diagnosis]" / "diagnosis code lookup" / "billing code for [condition]" / "EHR code for [X]" — search ICD-10-CM diagnostic codes (US clinical modification, ~96k codes). Returns code + full description. Use for medical billing, EHR diagnosis coding, claim coding. Example: terms="diab" → E11.9 Type 2 diabetes mellitus without complications.
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | – | Maximum matches to return. Default 7, max 500. Use 1–3 for typeahead UX, 20–50 for browsing. |
| df | string | – | Comma-separated display fields to use in the `displays` array. Default varies per table; usually the canonical name. |
| ef | string | – | Comma-separated extra fields to include per match. Field names vary per table; check NLM docs at clinicaltables.nlm.nih.gov. |
| terms | string | yes | Search query — prefix/contains match against canonical names. Whitespace-split into AND tokens. Example: "type 2 diabetes". |
No output schema declared.
No examples provided.
icd9cm ~204
"Old ICD-9 code for [diagnosis]" / "pre-2015 diagnosis codes" — search legacy ICD-9-CM diagnostic codes. Use ONLY when working with pre-2015 US clinical records; new claims must use icd10cm. Same shape as icd10cm.
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | – | Maximum matches to return. Default 7, max 500. Use 1–3 for typeahead UX, 20–50 for browsing. |
| df | string | – | Comma-separated display fields to use in the `displays` array. Default varies per table; usually the canonical name. |
| ef | string | – | Comma-separated extra fields to include per match. Field names vary per table; check NLM docs at clinicaltables.nlm.nih.gov. |
| terms | string | yes | Search query — prefix/contains match against canonical names. Whitespace-split into AND tokens. Example: "asthma". |
No output schema declared.
No examples provided.
loinc ~225
"LOINC code for [lab test]" / "standard code for blood test [X]" / "lab result identifier lookup" / "normalize lab name [Y]" — search LOINC lab test codes (Logical Observation Identifiers Names and Codes, universal lab test identifiers). Returns codes like "2093-3 Cholesterol [Mass/Vol] Ser/Plas". Use when normalizing lab results across institutions.
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | – | Maximum matches to return. Default 7, max 500. Use 1–3 for typeahead UX, 20–50 for browsing. |
| df | string | – | Comma-separated display fields to use in the `displays` array. Default varies per table; usually the canonical name. |
| ef | string | – | Comma-separated extra fields to include per match. Field names vary per table; check NLM docs at clinicaltables.nlm.nih.gov. |
| terms | string | yes | Search query — prefix/contains match against canonical names. Whitespace-split into AND tokens. Example: "cholesterol". |
No output schema declared.
No examples provided.
npi_individual ~236
"Find a doctor / clinician / physician by name" / "look up NPI for [provider]" / "verify a doctor's credentials" / "what's [Dr. X]'s NPI" — search the NPPES National Provider Identifier registry for individual US healthcare providers (~5M entries). Returns NPI numbers + provider names. terms can be a name fragment, NPI, or specialty. Use ef to include address, specialty, gender.
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | – | Maximum matches to return. Default 7, max 500. Use 1–3 for typeahead UX, 20–50 for browsing. |
| df | string | – | Comma-separated display fields to use in the `displays` array. Default varies per table; usually the canonical name. |
| ef | string | – | Comma-separated extra fields to include per match. Known fields: name.first,name.last,addr_practice.full,licenses.taxonomy.classification. |
| terms | string | yes | Search query — prefix/contains match against canonical names. Whitespace-split into AND tokens. Example: "smith pediatrics". |
No output schema declared.
No examples provided.
npi_organization ~228
"Find a hospital / clinic by name" / "look up NPI for [organization]" / "what's [Mayo Clinic]'s NPI" / "verify a healthcare facility" — search the NPPES NPI registry for organizational providers (~1.8M entries) — hospitals, clinics, group practices. Same shape as npi_individual. terms can be org name, NPI, or city.
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | – | Maximum matches to return. Default 7, max 500. Use 1–3 for typeahead UX, 20–50 for browsing. |
| df | string | – | Comma-separated display fields to use in the `displays` array. Default varies per table; usually the canonical name. |
| ef | string | – | Comma-separated extra fields to include per match. Known fields: name.full,addr_practice.full,licenses.taxonomy.classification. |
| terms | string | yes | Search query — prefix/contains match against canonical names. Whitespace-split into AND tokens. Example: "mayo clinic". |
No output schema declared.
No examples provided.
procedures ~272
"What is the procedure called [X]" / "medical procedure name lookup" / "patient-friendly name for [surgery]" — search clinical procedure names (NLM curated, ~7k entries). Returns short names like "Appendectomy", "Knee replacement". Patient-facing language; use for forms or intake screens. This vocabulary is SMALL and curated, so common terms can legitimately miss ("colonoscopy" and "MRI" both return 0, verified 2026-09-16) — a no_match here means "not in this list", not "no such procedure". For billing codes use icd10cm or a CPT source instead.
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | – | Maximum matches to return. Default 7, max 500. Use 1–3 for typeahead UX, 20–50 for browsing. |
| df | string | – | Comma-separated display fields to use in the `displays` array. Default varies per table; usually the canonical name. |
| ef | string | – | Comma-separated extra fields to include per match. Field names vary per table; check NLM docs at clinicaltables.nlm.nih.gov. |
| terms | string | yes | Search query — prefix/contains match against canonical names. Whitespace-split into AND tokens. Example: "appendectomy". |
No output schema declared.
No examples provided.
ucum ~223
"Unit of measure code for [X]" / "standard UCUM unit for [Y]" / "mg/dL code" — search UCUM (the Unified Code for Units of Measure, used by FHIR, LOINC, and most modern health-IT systems). Returns codes like "mg/dL", "[in_i]" (inch). Use when normalizing lab result units or rendering measurements.
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | – | Maximum matches to return. Default 7, max 500. Use 1–3 for typeahead UX, 20–50 for browsing. |
| df | string | – | Comma-separated display fields to use in the `displays` array. Default varies per table; usually the canonical name. |
| ef | string | – | Comma-separated extra fields to include per match. Field names vary per table; check NLM docs at clinicaltables.nlm.nih.gov. |
| terms | string | yes | Search query — prefix/contains match against canonical names. Whitespace-split into AND tokens. Example: "mg/dL". |
No output schema declared.
No examples provided.
How do I install the Clinicaltables MCP server?
Clinicaltables runs locally as an npm package, launched with npx -y @pipeworx/mcp-clinicaltables. 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-clinicaltables
claude mcp add pipeworx-io-clinicaltables -- npx -y @pipeworx/mcp-clinicaltables
What is the Clinicaltables MCP server?
Clinicaltables is an MCP server listed in the public MCP registry as io.github.pipeworx-io/clinicaltables. NIH Clinical Tables Search Service MCP. This page covers its npm package (@pipeworx/mcp-clinicaltables).
Is the Clinicaltables MCP server safe to use?
Clinicaltables scores 77 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 Clinicaltables MCP server expose?
Clinicaltables exposes 10 tools: conditions, icd10cm, icd9cm, procedures, drugs, and 5 more. Their descriptions and schemas cost roughly 2,383 tokens of context every time the server is loaded.
Is the Clinicaltables MCP server still maintained?
Clinicaltables 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 Clinicaltables MCP server under?
Clinicaltables declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.