QD [Quantify Decisions] Drug Development Platform by Pharm·ology is a Model Context Protocol (MCP) connector that gives an AI assistant structured, traceable access to clinical-trial and regulatory intelligence. It answers questions over a curated database built from public sources — every figure is traceable to its source, and every reference is hyperlinked. QD is read-only.
What you can do
Ask in plain language (the assistant maps it to QD commands) or call commands directly. Capability families:
Search & fetch
find trials, drugs, regulatory approvals, guidances, advisory-committee records, and devices; fetch any record by its identifier (NCT, NDA/BLA, EMEA, guidance, AC, device).
Disease landscapes
one-call landscape of a condition/mechanism/therapy area: pipeline, approvals, recruitment benchmarks, efficacy & safety, regulatory interactions — as a branded HTML page or Excel workbook.
Competitive & pipeline views
mechanism × stage × company matrices; pipeline sankey/timeline/ phase visualizations.
Operational benchmarks
recruitment/accrual medians (ClinicalTrials.gov and EU CTIS, reported separately), trial design benchmarks, site/geography breakdowns, eligibility envelopes.
Regulatory
Approvals and assessment/disciplinary-review findings from major medicines regulators (FDA, EMA, and other national agencies - e.g. MHRA, Health Canada, TGA, PMDA, Swissmedic); an FDA interactions dossier (sponsor-FDA meetings and verbatim Q&A and FDA Advisory Committees).
Evidence
per-endpoint efficacy, adverse events by relative risk, and PubMed references for a trial or a whole scope.
Every quantitative result carries a source attribution to its origin (ClinicalTrials.gov, Drugs@FDA, EMA, PubMed, and the relevant national regulator) and links out to the primary record.
Requirements
A QD subscription.
QD is a paid service: you authenticate with your account and must hold the QD entitlement. Without it you can sign in but cannot run commands. To request access, contact contact@pharmology.dk.
An MCP client
that supports remote connectors with OAuth (e.g. Claude).
Connecting from Claude
In Claude, add the connector — from the Connectors Directory (search "QD [Quantify Decisions] Drug Development Platform") or, if adding manually, use the endpoint URL https://qd-mcp.pharmology.ai/mcp.
Complete the sign-in prompt. Authentication uses OAuth 2.0 (Auth0); approve the requested scopes.
Once connected, ask a question (e.g. "QD, build a competitor landscape of IgA nephropathy") or run qd help to see the command grammar.
Authentication & permissions
Sign-in
Sign-in is OAuth 2.0 / OIDC via Auth0 (PKCE). QD never sees your password.
Entitlements
Entitlements are permission-based: baseline access (mcp:access) enables all read/analysis commands; raw SQL and administrator views are separately gated and off by default.
Data, limits, and provenance
Read-only
QD runs only SELECT queries; it never modifies external systems or stores your data into its corpus.
Sources
public clinical-trial and regulatory data, refreshed on a regular cadence.
Provenance
results cite their source table/record; approvals and trials link out to Drugs@FDA / ClinicalTrials.gov / EMA / MHRA.
Privacy
See the Privacy Policy at https://pharmology.ai/privacy for what we collect (account identity, usage logs) and how we handle it.
Support
Questions or access requests: support@pharmology.dk.
What QD is