Truthstack Mcp

io.github.TruthStack1Published by GitHub account TruthStack1v2.1.1Updated Oct 24, 2026

Supplement-drug interaction safety API for AI agents with FDA adverse event data.

VerifiedSTDIODesktop onlyLocation & Lifestyle

Overview

AI-generated overview

Lets an assistant look up supplement-drug interaction safety information drawn from FDA adverse event data.

What you can do
The registry describes it as a supplement-drug interaction safety API for AI agents, using FDA adverse event data as its source. No tools are listed in the manifest and no README is available, so the exact operations cannot be confirmed from the supplied material. It is intended to give an assistant a way to check interaction and adverse-event information while answering health-related questions.
When to use it
Worth considering when an assistant needs to answer questions about supplement and drug interactions or adverse event reports and you want that lookup available as a tool. Less useful if you need general medical reference, prescribing guidance, or a documented tool surface, since none is described here.
Requirements
Runs as a local process over stdio, installed from the npm package truthstack-mcp, so Node.js and npm are needed. The manifest declares no authentication, environment variables, or headers. Desktop only; no web executable. Network access is likely needed to reach the underlying safety API, though this is not stated.
Before you install
No credentials, payments, or write actions are declared, and no environment variables or headers are requested. The registry description is the only source of detail: no tool list, README, or privacy documentation is available, so it is unclear what data is sent to the upstream API or how results are sourced. Treat interaction and adverse-event output as reference information, not medical advice.

Installation

In SourceWeft

  1. Open Truthstack Mcp 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. v2.1.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.