hypokrates

io.github.bruno-portfolioPublished by GitHub account bruno-portfoliov0.7.1Updated Oct 24, 2026

Pharmacovigilance hypothesis generation from 15 public drug safety databases

VerifiedSTDIODesktop onlyData & Analytics

Overview

AI-generated overview

A local MCP server that generates pharmacovigilance hypotheses from 15 public drug safety databases, letting an assistant explore drug safety signals.

What you can do
Generate pharmacovigilance hypotheses from public drug safety data, as described by the provider. The server draws on 15 public drug safety databases as its evidence base. No individual tools are listed in the manifest, so the exact operations an assistant can call are not documented here. It runs as a local process over stdio rather than as a remote endpoint.
When to use it
Worth considering when you want an assistant to help form or explore drug safety hypotheses using public pharmacovigilance data, for example in research or safety-review work. It is not aimed at general data analysis or clinical decision-making.
Requirements
Runs as a local process on the user's machine, installed from the PyPI package hypokrates over stdio, so a Python environment is needed. No authentication, environment variables or headers are declared. Desktop use only; no web executable.
Before you install
The manifest lists no tools, so what the server actually does and what data it reads or sends cannot be verified from this listing. Public safety databases are observational and can produce spurious signals; treat generated hypotheses as leads for review, not conclusions. No credentials are requested.

Installation

In SourceWeft

  1. Open hypokrates 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. v0.7.1LatestSep 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.