Health Api

io.github.Nicodemus941Published by GitHub account Nicodemus941v1.0.6Updated Oct 24, 2026

Clinical AI for lab analysis, biomarker scoring, health narratives, and risk insights.

VerifiedSTDIODesktop onlyLocation & LifestyleAI & ML

Overview

AI-generated overview

A local MCP server that gives an assistant clinical AI tools for lab analysis, biomarker scoring, health narratives and risk insights.

What you can do
Analyze laboratory results and produce clinical interpretations through the E-Labus API. Score biomarkers and derive risk insights from health data. Generate health narratives that summarize findings in readable form. The manifest lists no individual tools, so the exact operations are not documented here.
When to use it
Useful when an assistant needs to interpret lab panels, score biomarkers or draft health risk summaries, and you are willing to send that health data to the E-Labus service.
Requirements
Runs as a local process via the npm package @e-labus/mcp over stdio, so a Node.js runtime is needed. Requires an E-Labus API key supplied in the ELABUS_API_KEY environment variable; the manifest says a free key is available from the provider's developer site. Network access to the E-Labus API is implied.
Before you install
The server handles clinical and biomarker data, which is sensitive health information sent to a third-party API. Keep the ELABUS_API_KEY secret and do not share it. Outputs are AI-generated clinical insights and should not be treated as medical advice or a diagnosis.

Installation

In SourceWeft

  1. Open Health Api 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.6LatestSep 16, 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.