Medical RAG - Clinical Decision Support & Healthcare Knowledge Retrieval

io.github.maxi-mossPublished by GitHub account maxi-mossv1.0.1Updated Oct 24, 2026

Medical RAG: semantic search for clinical guidelines, drug interactions, diagnoses & EHR data.

The publisher's own server: [PREPROD] Clinical.ly Research Suite

VerifiedStreamable HTTPWeb executableKnowledge & Memory

Overview

AI-generated overview

A remote MCP endpoint offering semantic search over clinical guidelines, drug interactions, diagnoses and EHR data for medical knowledge retrieval.

What you can do
Search clinical guidelines and healthcare knowledge semantically to support clinical decisions. Look up drug interactions and diagnoses. Retrieve relevant EHR data. The manifest lists no individual tools, so exact operations are not documented.
When to use it
Useful when an assistant needs to look up clinical guidance, check drug interactions, or pull relevant healthcare knowledge and EHR context during medical research or decision-support conversations.
Requirements
A remote streamable HTTP endpoint; no package installation is needed. The manifest declares no authentication, environment variables or headers, so no credentials appear to be required.
Before you install
The server handles medical and EHR-related content, which is sensitive; consider privacy and compliance before sending patient data. No authentication is declared, so anyone reaching the endpoint may be able to query it. Output is retrieval only and should not be treated as medical advice.

Installation

In SourceWeft

  1. Open Medical RAG - Clinical Decision Support & Healthcare Knowledge Retrieval in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.maxi-moss%2Ftest-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "medical-rag-clinical-decision-support-he": {
      "type": "http",
      "url": "https://mcp-registry-test-server-513943347567.europe-west1.run.app/mcp"
    }
  }
}

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.0.1LatestSep 16, 2026

Score

67% 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 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 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.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.

Other Clinical integrations