Clinicaltrialsgov MCP Server vs Pharma Regulatory
A side-by-side look at the Clinicaltrialsgov MCP Server and Pharma Regulatory MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Clinicaltrialsgov MCP Server for biology & bioinformatics work as a local process; choose Pharma Regulatory for biology & bioinformatics over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Clinicaltrialsgov MCP Server when
- You need dedicated capabilities in the Biology & Bioinformatics domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
clinicaltrials_search_studies, clinicaltrials_get_study_record, clinicaltrials_get_study_count.
Choose Pharma Regulatory when
- You need dedicated capabilities in the Biology & Bioinformatics domain.
- You prefer a remote HTTP/SSE transport.
- You want tools like
check_drug, check_drug_interactions, check_adverse_events.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Biology & Bioinformatics | Biology & Bioinformatics |
| Quality signal | 63/100 · Good | 47/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | No auth required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 99 | 0 |
| Directory activity | 2 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 7 | 4 |
| Full listing | View Clinicaltrialsgov MCP Server | View Pharma Regulatory |
Tools & capabilities
Clinicaltrialsgov MCP Server tools 7
clinicaltrials_search_studiesSearch studies with full-text and field-specific queries, status/phase/geographic filters, pagination, sorting, and field selectionclinicaltrials_get_study_recordFetch a single study by NCT ID — full protocol record with optional location/outcome/reference capsclinicaltrials_get_study_countFast total study count for a query, without fetching dataclinicaltrials_get_field_valuesDiscover valid values for API fields, with per-value study countsclinicaltrials_get_field_definitionsResolve valid field names — keyword search, path drill-down, or top-level overviewclinicaltrials_get_study_resultsFetch posted results — outcomes, adverse events, participant flow, baseline — for completed studiesclinicaltrials_find_eligibleMatch patient demographics and conditions to candidate recruiting trials, without checking inclusion/exclusion criteria
Pharma Regulatory tools 4
check_drugLook up a drug, medicine, active ingredient, or CAS number across DrugBank, WHO Essential Medicines, Australian TGA ARTG, and FDA NDI notifications. Returns identifiers, targets, schedules, dosage forms, indications, and regulatory records.check_drug_interactionsCheck drug-drug interactions for one drug or a specific pair. Returns interaction severity, mechanism, clinical effect, evidence level, and management recommendations for medication safety review.check_adverse_eventsCheck FDA FAERS adverse-event records for a drug or active ingredient. Returns total reports, serious outcomes, death reports, top adverse reactions, and common patient age groups.search_pharmaSearch across pharmaceutical regulatory and safety databases by keyword. Use for broad discovery across DrugBank, WHO Essential Medicines, TGA ARTG, FAERS, FDA NDI, drug interactions, and ChEMBL bioactivity.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Clinicaltrialsgov MCP Server
{
"mcpServers": {
"clinicaltrialsgov-mcp-server": {
"command": "npx",
"args": [
"-y",
"clinicaltrialsgov-mcp-server"
]
}
}
}
Pharma Regulatory
{
"mcpServers": {
"pharma-regulatory": {
"url": "https://pharma-mcp-server.rootsbybenda.workers.dev/mcp"
}
}
}
Frequently asked questions
Clinicaltrialsgov MCP Server is categorized under Biology & Bioinformatics and uses a local stdio subprocess. Pharma Regulatory belongs to Biology & Bioinformatics and uses a remote HTTP/SSE transport. Pick Clinicaltrialsgov MCP Server for biology & bioinformatics work and Pharma Regulatory for biology & bioinformatics.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Clinicaltrialsgov MCP Server is listed as free. Auth: no auth required. Pharma Regulatory has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add clinicaltrialsgov-mcp-server and pharma-regulatory as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Clinicaltrialsgov MCP Server has a quality signal of 63/100 (Good) with 2 views, 0 installs and 99 GitHub stars. Pharma Regulatory has 47/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.