Home / MCP registry index / io.github.rootsbymenda/pharma-regulatory

Pharma Regulatory

io.github.rootsbymenda/pharma-regulatory in the official MCP registry. Endpoint https://pharma-mcp-server.rootsbybenda.workers.dev/mcp. Source: github.com/rootsbymenda/pharma-mcp-server.

The registry describes it as: Drug safety: DrugBank, interactions, FAERS, WHO, TGA. 7 databases. Free.

We could not reach this server's endpoint on 2026-10-27. Nothing was checked.

Rather than checking back: subscribe to this server's tool changes (a feed, no account and no address needed). Tool names and dates only, never what a tool says.

Run this server? Show the check in your README

The badge reflects the latest read: MCP tool check badge

Markdown
[![MCP tool check](https://lazaretto.dev/mcp-registry/io-github-rootsbymenda-pharma-regulatory/badge.svg)](https://lazaretto.dev/mcp-registry/io-github-rootsbymenda-pharma-regulatory)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. How tool poisoning works. What we found across the registry. Check another server.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.

Related

Database MCP servers

QuintaDB
com.quintadb/mcp
159 tools, nothing matched
2026-10-28
QuintaDB
ru.quintadb/mcp
159 tools, nothing matched
2026-11-04
QuintaDB
ua.com.quintadb/mcp
159 tools, nothing matched
2026-11-04
Shiply
now.shiply/shiply
114 tools, nothing matched
2026-11-04
Redu
cloud.redu/mcp
91 tools, nothing matched
2026-10-28
Chembl
io.github.pipeworx-io/chembl
51 tools, nothing matched
2026-11-04