Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/yesc97/biopharma-catalyst-mcpWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/yesc97/biopharma-catalyst-mcp/biopharma-catalyst-mcp)<a href="https://agentmods.dev/mcp/yesc97/biopharma-catalyst-mcp/biopharma-catalyst-mcp"><img src="https://agentmods.dev/badge/mcp/yesc97/biopharma-catalyst-mcp/biopharma-catalyst-mcp/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/yesc97/biopharma-catalyst-mcp/biopharma-catalyst-mcp"><img src="https://agentmods.dev/badge/mcp/yesc97/biopharma-catalyst-mcp/biopharma-catalyst-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
biopharma-catalyst-mcp scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 11d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"biopharma-catalyst-mcp": {
"command": "npx",
"args": [
"-y",
"biopharma-catalyst-mcp"
],
"env": {
"SEC_USER_AGENT": ""
}
}
}What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 11d ago First seen · 12 lines scan A 3e9d892761fd
biopharma-catalyst-mcp is an MCP server published in the GitHub repository yesc97/biopharma-catalyst-mcp (5 stars, last pushed 4mo ago), licensed ISC. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other mcp servers, from other repositories
clinicaltrialsgov-mcp-server
Search ClinicalTrials.gov — find studies, retrieve results, match patients to eligible trials. Runs locally from the clinicaltrialsgov-mcp-server npm package. Needs 4 environment variables to run.
pyomop
OMOP CDM utils in Python. Runs locally from the pyomop Python package.
biopharma-mcp
Enterprise-grade MCP server for Biopharma software infrastructure, FDA 21 CFR Part 11 audit logging, CDISC SDTM exports, 4PL curves, and HIPAA PII redaction. Runs locally from the @seosiri/biopharma-mcp npm package.
nigeria-imf-weo
IMF World Economic Outlook for Nigeria (growth, inflation, debt, more). Keyless. Runs locally from the @braynexservices/nigeria-mcp-imf-weo npm package. Needs 1 environment variable to run.
clinicaltrials-mcp
Conversational access to ClinicalTrials.gov — an MCP server for pharma analysts, CRO teams, and health-tech builders. Runs locally from the clinicaltrials-mcp Python package.
phasefolio
PhaseFolio MCP client — biotech rNPV / probability-of-success engine for AI agents. One-line install for Claude, Codex, Cursor, and any MCP-compatible client. Runs locally from the @phasefolio/mcp npm package. Needs 1 environment variable to run.