Industry solutionsPublic source

mcp-pharmacy

Global drug reference and regulatory intelligence MCP server. Provides federated access to drug labels, safety alerts, adverse events, product registrations, clinical trials, and chemical identity across US, EU, UK, and…

Open the source Read the official guide ↗

What it gives an agent

A purpose-built capability behind one MCP connection.

The server owns its domain logic and publishes a tool contract an MCP client can discover. ADK-Rust can load that contract into an agent, normalize each schema for the chosen model provider, and keep the connection lifecycle outside the agent’s business logic.

Provides pharmacy capabilities through a typed MCP contract.

Architecture

How mcp-pharmacy fits into an agent system.

The model never needs the implementation details or credentials of the system behind the server. It sees reviewed tool definitions. The MCP client handles discovery and calls, while the server keeps ownership of validation, policy, and communication with its domain system.

ADK-Rust agent

Chooses a capability from the reviewed tool catalog.

→

MCP client

Discovers schemas, sends calls, and receives typed content.

→

mcp-pharmacy

Validates the request and owns 19 documented tool contracts.

→

Domain system

Keeps the API, data, credentials, and business rules behind the server.

Connection: stdio · Server framework: ADK MCP SDK + rmcp

This repository does not currently publish a dedicated architecture SVG. The integration diagram above is generated from its documented transport and server boundary; use the official README for implementation-specific details.

Tool catalog

What can an agent ask mcp-pharmacy to do?

Each tool has a stable name, a human-readable purpose, and a JSON input contract discovered during MCP initialization. Risk classes come from the project’s registry manifest when one is available.

19 named tools

openfda_search_labels

Search US drug labels (package inserts) by generic name, brand name, or indication

read only

openfda_get_adverse_events

Search FDA Adverse Event Reporting System (FAERS) for a drug

read only

openfda_search_recalls

Search FDA drug recalls and enforcement actions

read only

openfda_get_ndc

Look up National Drug Code (NDC) directory entries for a drug

read only

dailymed_search_labels

Search DailyMed structured product labels (SPL) by drug name

read only

dailymed_get_label_xml

Retrieve full SPL XML label by setid for detailed section extraction

read only

rxnorm_normalize

Normalize a drug name to RxNorm RxCUI identifier

read only

rxnorm_get_properties

Get drug properties (name, term type, status) by RxCUI

read only

rxnorm_get_atc_classes

Get WHO ATC classification codes for a drug via RxCUI

read only

pubchem_search_compound

Search PubChem for a chemical compound by name, get CID and structure

read only

pubchem_get_properties

Get molecular properties (formula, weight, IUPAC name) for a compound by CID

read only

health_canada_search_products

Search Health Canada Drug Product Database by brand name or active ingredient

read only

Governance

Understand the effect of every tool.

A server connection inherits the authority of its credentials and deployment environment. The declarations below come from this project’s README and MCP registry manifest; your application still decides which tools an agent receives and where approval is required.

19 read only

The registry manifest declares read only tool risk classes.

MCP surface

What the current documentation declares.

MCP can carry tools, resources, prompts, structured results, progress, cancellation, and long-running work. This record highlights the modern protocol features explicitly mentioned by this repository.

The current README concentrates on its tool surface. Check the source and release notes before relying on optional MCP capabilities beyond tool discovery and invocation.

ADK MCP SDKrmcpRegistry manifest

Install and connect

Follow the project’s documented starting point.

Install the server in the environment that owns its credentials and domain access. Add it to your MCP host, verify the discovered tools, and narrow the toolset before giving it to a production agent.

Install

cargo install mcp-pharmacy

ADK-Rust connection shape

let toolset = McpToolset::from_stdio(
    "mcp-pharmacy",
    ["mcp-pharmacy"],
).await?;

let agent = LlmAgentBuilder::new("agent")
    .tools(toolset.tools().await?)
    .build()?;

Commands and configuration are extracted from the public README. Confirm prerequisites, environment variables, and release-specific options in the official documentation before deployment.

Official documentation

Continue with the project maintainers’ source of truth.

This page provides an approachable map of the server. The repository remains authoritative for exact schemas, prerequisites, configuration, examples, tests, releases, and security updates.

Overview ↗README.md CHANGELOG ↗CHANGELOG.md Issues and support ↗github.com issues

Keep exploring

mcp-pharmacy

A purpose-built capability behind one MCP connection.

How mcp-pharmacy fits into an agent system.

ADK-Rust agent

MCP client

mcp-pharmacy

Domain system

What can an agent ask mcp-pharmacy to do?

Understand the effect of every tool.

What the current documentation declares.

Follow the project’s documented starting point.

Continue with the project maintainers’ source of truth.

More in industry solutions.