Inxight Drugs
NPM · @PIPEWORX/MCP-INXIGHT-DRUGS · 2 COMPONENTS
Inxight Drugs — NCATS drug development status by indication.
Available components
Last scanned (10 hours ago)
Scores higher than 72% 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 & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-inxight-drugs). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 3 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability63
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 718 tokens (~239/item across 3 items; 3 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 Management20
- Stability observed for 6 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 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 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +1
- Security disclosure: unverified → fail ▼ functional
- 2 Nov 26 +1
- Security disclosure: fail → unverified ▼ functional
- Stability: unverified → 0.10 ▲ functional
- Package version: 0.2.0 → 0.2.1 functional
- 31 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 30 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-inxight-drugs@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-inxight-drugs |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-inxight-drugs/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3637465548 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:fe35ddb74fe6d5e51a9950cd5e7a29a82ed69983bc8215cbf262d06caf249918e6aa52f3f3a68f1183fca236172d1479cdcb28fb6f5b205a04134a93d |
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 →
inxight_indication ~214
Drugs and substances approved for or in clinical development for a condition, from NCATS Inxight Drugs: give a disease or indication (e.g. "stroke", "major depressive disorder", "migraine") and get each substance with the highest phase it has reached FOR THAT CONDITION, the trial or label URL behind it, and its FDA UNII. Narrow with development_status "Clinical" to see only investigational drugs. Also returns the related condition labels Inxight uses (e.g. "Ischemic stroke", "Acute ischemic stroke") so a caller can drill down.
| Name | Type | Req | Description |
|---|---|---|---|
| condition | string | yes | Disease or indication, e.g. "stroke", "Alzheimer disease" |
| development_status | string | – | Only substances whose overall development status is this value; "Clinical" = investigational only |
| limit | number | – | Substances to return, 1-25 (default 10) |
| offset | number | – | Substances to skip, for paging (default 0) |
No output schema declared.
No examples provided.
inxight_search ~209
Search NCATS Inxight Drugs substances by free text (drug name, synonym, code, company or condition words), optionally narrowed to a development status (US Approved Rx, US Approved OTC, US Previously Marketed, Possibly Marketed Outside US, Clinical, Other). Returns matching substances with FDA UNII and class, the total hit count, and breakdowns of the matches by development status, highest phase and top conditions. Use it to find the UNII to pass to inxight_substance or to scan, e.g., which psychedelics are in clinical development.
| Name | Type | Req | Description |
|---|---|---|---|
| development_status | string | – | Only substances whose overall development status is this value |
| limit | number | – | Results to return, 1-50 (default 10) |
| offset | number | – | Results to skip, for paging (default 0) |
| query | string | yes | Free-text query, e.g. "psilocybin", "GLP-1", "tryptamine" |
No output schema declared.
No examples provided.
inxight_substance ~237
Drug development status by indication from NCATS Inxight Drugs: for one drug or substance (by name or FDA UNII), every condition it is approved for or in clinical trials for with the highest phase reached per condition (Approved, Phase III, Phase II, Phase I) and the trial or label behind it, plus the overall highest development event, first approval year and source, originator company, molecular targets with pharmacology and potency, synonyms, and cross-reference ids (ChEMBL, DrugBank, PubChem, CAS, MeSH, RxCUI). Answers "what is psilocybin being developed for and how far along", "which indications is this drug approved for", "is this compound still in trials".
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | – | Drug or substance name, brand or generic (e.g. "psilocybin", "aspirin", "semaglutide"). Give name or unii. |
| unii | string | – | FDA Unique Ingredient Identifier, 10 characters (e.g. "2RV7212BP0" for psilocybin). Takes precedence over name. |
No output schema declared.
No examples provided.
How do I install the Inxight Drugs MCP server?
Inxight Drugs runs locally as an npm package, launched with npx -y @pipeworx/mcp-inxight-drugs. 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-inxight-drugs
claude mcp add pipeworx-io-inxight-drugs -- npx -y @pipeworx/mcp-inxight-drugs
What is the Inxight Drugs MCP server?
Inxight Drugs is an MCP server listed in the public MCP registry as io.github.pipeworx-io/inxight-drugs. Inxight Drugs, NCATS drug development status by indication. This page covers its npm package (@pipeworx/mcp-inxight-drugs).
Is the Inxight Drugs MCP server safe to use?
Inxight Drugs scores 82 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 Inxight Drugs MCP server expose?
Inxight Drugs exposes 3 tools: inxight_substance, inxight_search, inxight_indication. Their descriptions and schemas cost roughly 660 tokens of context every time the server is loaded.
Is the Inxight Drugs MCP server still maintained?
Inxight Drugs 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 Inxight Drugs MCP server under?
Inxight Drugs declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.