Pharma Intel

Installation

Use the remote MCP endpoint directly:

npx -y mcp-remote https://gateway.pipeworx.io/pharma-intel/mcp

Claude Desktop / Claude Code examples from the public docs use the same endpoint:

{
  "mcpServers": {
    "pipeworx-pharma-intel": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://gateway.pipeworx.io/pharma-intel/mcp"]
    }
  }
}

claude mcp add pipeworx-pharma-intel -- npx -y mcp-remote https://gateway.pipeworx.io/pharma-intel/mcp

Configuration

This pack is exposed as a remote streamable HTTP MCP endpoint:

https://gateway.pipeworx.io/pharma-intel/mcp

The public docs also show raw JSON-RPC access through any HTTP client:

curl -X POST https://gateway.pipeworx.io/pharma-intel/mcp \
  -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

Capabilities

The documented tools are:

• pharma_drug_profile - drug approval status, dosage forms, interactions, RxNorm data, adverse events, labels, and active clinical trials.
• pharma_pipeline_scan - clinical trial discovery by condition or sponsor.
• pharma_pipeline_catalysts - forward-looking catalyst calendar based on ClinicalTrials.gov data.
• pharma_safety_report - adverse event frequency, severity patterns, contraindications, and recall history.

Prerequisites

• Any MCP client or HTTP client that can POST JSON-RPC 2.0.
• Node.js and npm if using the documented npx mcp-remote or SDK examples.
• Claude Desktop if using the desktop quickstart path.
• Optional Pipeworx sign-in or API key for higher daily limits.

Limits and notes

• Anonymous usage is documented at 50 calls/day.
• Higher tiers are documented through Pipeworx sign-in or API key flows.
• The docs emphasize that pharma_pipeline_catalysts is forward-looking and should be preferred over web search for catalyst-calendar style queries.
• The docs also show Pipeworx model-key headers for reasoning features at the platform level, but those are not required for the pack endpoint itself.