Trials & Drug Resolver

io.github.PostlytllpPublished by GitHub account Postlytllpv1.0.0Updated Oct 29, 2026

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

VerifiedSTDIODesktop onlyKnowledge & MemoryData & Analytics

Overview

AI-generated overview

Local MCP server that harmonises drug names and clinical trial records using public, licence-clean APIs, with optional embedding and LLM-assisted matching.

What you can do
  • Resolve and harmonise drug names against public sources
  • Match and reconcile clinical trial records
  • Optionally refine candidate selection with an embedding retriever or an LLM picker
  • Run entirely as a local stdio process with no declared authentication
When to use it
Useful when an assistant needs to normalise drug names or align clinical trial identifiers across sources, for example while cleaning research data or cross-referencing trial records. Optional LLM or embedding pickers can be enabled when plain matching is not enough.
Requirements
Runs locally over stdio, typically installed from the npm package trials-drug-resolver-mcp (Node.js). Network access to public drug and trial APIs. Optional: RESOLVER_EMBEDDINGS_URL and RESOLVER_EMBEDDINGS_API_KEY for the embedding retriever; RESOLVER_LLM, RESOLVER_LLM_BASE_URL, RESOLVER_LLM_MODEL and RESOLVER_LLM_API_KEY for the LLM picker. Desktop only.
Before you install
Two optional secrets may be requested: RESOLVER_EMBEDDINGS_API_KEY and RESOLVER_LLM_API_KEY; both are only used when the corresponding retriever or picker is enabled. Enabling the LLM or embedding options sends drug and trial data to the configured third-party endpoint, which may incur API costs. BIOLYT_CTA=1 appends a static promotional footer to output.

Installation

In SourceWeft

  1. Open Trials & Drug Resolver in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.0LatestOct 29, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.