india-rx-mcp
An MCP (Model Context Protocol) server for Indian pharma regulatory data — CDSCO drug approvals and NPPA ceiling-price data — for any MCP-compatible LLM client (Claude Desktop, Cursor, Cline, Continue).
Built by a pharma market analyst, for pharma market analysts.
Why this exists
Multiple MCP servers exist for US pharma (openFDA, Orange Book, ClinicalTrials.gov). None exist for Indian pharma. Indian regulatory data is overwhelmingly scrape-not-API, which is exactly why no one has done it. This server fills the gap.
What it gives you
7 tools that map directly to analyst questions:
| Question | Tool |
|---|---|
| "What did Sun Pharma get approved in 2026?" | cdsco_sponsor_pipeline * |
| "What's new in oncology this month?" | search_cdsco_approvals |
| "What's the ceiling price for atorvastatin 10mg?" | get_nppa_ceiling_price |
| "Any recent antibiotic price changes?" | list_nppa_price_changes * |
| "Tell me about the latest CDSCO approval for [drug]" | get_cdsco_approval |
| "What's new in CDSCO approvals?" | list_recent_cdsco_approvals |
| "Which formulations are NPPA-controlled in cardiology?" | search_nppa_scheduled_formulations |
* denotes a v1 limitation — see Limitations below.
2 browseable resources:
cdsco://catalog/approved-drugs— full CDSCO catalog as one documentnppa://catalog/scheduled-formulations— full NPPA ceiling-price list
3 pre-built analyst workflow prompts:
competitor_briefing(sponsor)— written brief on a company's regulatory footprinttherapeutic_area_landscape(therapeutic_area, since_months=12)— landscape view of a TAmonthly_market_update()— digest of recent approvals and price changes
Install (Claude Desktop)
Add to your Claude Desktop config (%APPDATA%\Claude\claude_desktop_config.json on Windows, ~/Library/Application Support/Claude/claude_desktop_config.json on macOS):
{
"mcpServers": {
"india-rx": {
"command": "uvx",
"args": ["india-rx-mcp"]
}
}
}
Restart Claude Desktop. First launch will scrape and cache CDSCO + NPPA data in the background (5-10 minutes). After that, queries are <100ms.
See docs/claude-desktop-setup.md for the full setup including PAT-style alternatives.
CLI
india-rx-mcp version # print version
india-rx-mcp status # show cache status (counts + last refresh per source)
india-rx-mcp refresh # force refresh from gov.in
india-rx-mcp refresh --source cdsco # refresh just CDSCO
Architecture
See docs/architecture.md.
Limitations (v1)
This is v0.1 — first public release. Known gaps you should know about before relying on the data:
- CDSCO sponsor data is missing. CDSCO publishes yearly approval PDFs with
S.No / Drug Name / Indication / Dateonly — no sponsor column. So:cdsco_sponsor_pipeline(...)returns empty for CDSCO-sourced datasearch_cdsco_approvals(sponsor=...)filter won't match CDSCO dataApproval.sponsorisNonefor all CDSCO records- Planned for v1.1 (likely by parsing detailed approval letters or alternative CDSCO endpoints)
- NPPA data is from the 2022 Compendium of Prices (last published comprehensive compilation). Quarterly WPI revisions since then aren't in v1. Adding WPI-revision notification parsing is planned for v1.2.
list_nppa_price_changes(...)returns empty in v1. The compendium is a snapshot. Price-change tracking requires either comparing successive compendiums or parsing WPI revision notifications — both planned for v1.2.therapeutic_areaon NPPA is best-effort substring match on drug name (NPPA formulations don't carry indication metadata). For richer TA filtering usesearch_cdsco_approvals(therapeutic_area=...), which has a built-in keyword-expansion map.- Patents, CTRI clinical trials, FDA cross-reference: out of scope for v1.
Roadmap
- v1.1: CDSCO sponsor data; CTRI clinical trials integration
- v1.2: WPI revision parsing for live price changes; CDSCO ↔ FDA approval-timing comparison tool
- v2.0: Indian Patent Office (inPASS) integration; optional hosted multi-tenant version
Contributing
This is a portfolio project but contributions are welcome. Open an issue describing what you want to add before sending a PR.
License
MIT. See LICENSE.
Metadata
Release files for india-rx-mcp 0.1.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| india_rx_mcp-0.1.1.tar.gz | 2.8 MB | Without provenance | Details for india_rx_mcp-0.1.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| india_rx_mcp-0.1.1-py3-none-any.whl | Python 3 | none | any | Details for india_rx_mcp-0.1.1-py3-none-any.whl |
Total release size: 4.1 MB
Release files / india_rx_mcp-0.1.1.tar.gz
| Download URL | india_rx_mcp-0.1.1.tar.gz |
|---|---|
| Size | 2.8 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
18bd84762c403e8efe0ee3616a08edbe502d75893e888c6940522a1205108be5
|
|
BLAKE2b-256 checksum How to use checksums |
52386ca694a51962ab3e4a8b11719499252550411f2b4d64da43e8d4c26b61ba
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.11.14 {"installer":{"name":"uv","version":"0.11.14","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":null,"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Release files / india_rx_mcp-0.1.1-py3-none-any.whl
| Download URL | india_rx_mcp-0.1.1-py3-none-any.whl |
|---|---|
| Size | 1.3 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
478dfe4443e240bbd0821f259126aa833fc87bf303b22e0ab00d5fdd4075c753
|
|
BLAKE2b-256 checksum How to use checksums |
a743abd3887ef41e771e8788cb7e481b520779d47e2f706da12f93012f046415
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.11.14 {"installer":{"name":"uv","version":"0.11.14","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":null,"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Security for india-rx-mcp 0.1.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.