
Pharma Signal Api
io.github.NiteowlptPublished by GitHub account Niteowlptv1.0.1Updated Oct 25, 2026
Drug safety intelligence: 358 drugs, 1M+ FDA adverse events, PV signal detection.
Overview
A local MCP server giving assistants drug safety intelligence: 358 drugs and over 1M FDA adverse events with pharmacovigilance signal detection.
- What you can do
- Look up drug safety information across a dataset of 358 drugs and more than one million FDA adverse events, as described in the registry entry. Surface pharmacovigilance signals derived from those adverse event reports. No individual tools are listed in the manifest, so the exact operations available are not documented here.
- When to use it
- Useful when an assistant needs to answer questions about drug safety, adverse event reports, or potential safety signals for a set of drugs, for example during pharmacovigilance research or literature review.
- Requirements
- Runs as a local process over stdio, installed from the npm package pharma-signal-mcp, so a Node.js runtime is needed. Requires a Pharma Signal API key supplied through the PHARMA_SIGNAL_API_KEY environment variable. Desktop client only.
Installation
In SourceWeft
- Open Pharma Signal Api in the dashboard and add it to a workspace.
- 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
0Version history
1- v1.0.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.