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.

Trials & Drug Resolver

NPM · TRIALS-DRUG-RESOLVER-MCP

Harmonise drug names and clinical trials using public licence-clean APIs.

0 this week 65 Trust /100

Last scanned (23 hours ago)

Scores higher than 37% 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
  • 0 of 3 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency19
  • Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 17 days ago).Pass
  • Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability75
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 419 tokens (~104/item across 4 items; 4 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

What we tested

Checks we ran (14)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Schema quality
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (2)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Security disclosure in Provenance & TransparencySecurity-disclosure policy not yet verified: we couldn't inspect the source repository.
  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

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.

  • 29 Oct 26 +15
    • Malware scan: unverified → pass ▲ security
  • 28 Oct 26 50

    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 21 Nov 2026 · Analysed npm/trials-drug-resolver-mcp@1.0.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 3 packages
Packages resolved 3
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 4 exposed · ~419 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
competitive_landscape ~125

List drugs in development for a target or an indication, with sponsors and trial phases, using ChEMBL mechanisms and ClinicalTrials.gov. Results are capped and are a sample, not a complete registry extract.

NameTypeReqDescription
indicationstring–Disease or condition, for example melanoma.
maxDrugsinteger–Maximum drugs to return. Default 8.
maxTrialsPerDruginteger–Maximum trials to attach to each drug. Default 3.
targetstring–Gene, protein, or target name, for example PD-1 or EGFR.

No output schema declared.

No examples provided.

drug_profile ~62

Return one resolved drug with synonyms, verified identifiers, ChEMBL mechanisms, linked ClinicalTrials.gov studies, and sponsors.

NameTypeReqDescription
maxTrialsinteger–Maximum linked trials. Default 15.
querystringyesDrug name, code name, or brand.

No output schema declared.

No examples provided.

resolve_drug ~91

Resolve a drug name, code name, brand, or misspelling to verified UNII, ChEMBL, and RxCUI identifiers. Code names such as MK-3475 are exact-only and are never fuzzy-matched. Returns status none when the match is ambiguous or below the confidence threshold.

NameTypeReqDescription
querystringyesDrug name, code name, brand, combination, or misspelling.

No output schema declared.

No examples provided.

search_trials ~141

Search ClinicalTrials.gov API v2. A drug argument is resolved first and the search uses verified synonyms. Duplicate NCT records are merged and sponsor names are normalised.

NameTypeReqDescription
conditionstring–Condition or disease query.
drugstring–Drug name or code. Resolved to synonyms before search.
overallStatusarray–ClinicalTrials.gov overall status values.
pageSizeinteger–Page size, default 20, maximum 50.
pageTokenstring–nextPageToken from a previous page.
querystring–Additional free-text trial query.
sponsorstring–Sponsor or collaborator query.

No output schema declared.

No examples provided.

Install

How do I install the Trials & Drug Resolver MCP server?

Trials & Drug Resolver runs locally as an npm package, launched with npx -y trials-drug-resolver-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · trials-drug-resolver-mcp

# add to Claude Code
claude mcp add postlytllp-trials-drug-resolver -- npx -y trials-drug-resolver-mcp
Common questions

What is the Trials & Drug Resolver MCP server?

Trials & Drug Resolver is an MCP server listed in the public MCP registry as io.github.Postlytllp/trials-drug-resolver. Harmonise drug names and clinical trials using public licence-clean APIs. This page covers its npm package (trials-drug-resolver-mcp).

Is the Trials & Drug Resolver MCP server safe to use?

Trials & Drug Resolver scores 65 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. It declares no install or post-install scripts. 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 Trials & Drug Resolver MCP server expose?

Trials & Drug Resolver exposes 4 tools: resolve_drug, search_trials, competitive_landscape, drug_profile. Their descriptions and schemas cost roughly 419 tokens of context every time the server is loaded.

Is the Trials & Drug Resolver MCP server still maintained?

Trials & Drug Resolver is still listed as active in the MCP registry. We last reached this channel on 21 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 Trials & Drug Resolver MCP server under?

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

What did VerifyMCP test on the Trials & Drug Resolver MCP server?

VerifyMCP ran 14 checks on Trials & Drug Resolver, covering Malware scan, Known CVEs, Install scripts, Dependency health and 10 more. 2 items could not be completed, a gap on our side rather than a finding about Trials & Drug Resolver: Security disclosure and Stability. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.