mcp-pharma
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_PHARMA_API_KEY | Yes | API key for Pro access (X-API-Key header) | |
| MCP_PHARMA_TIMEOUT | No | HTTP timeout in seconds (default: 30) | |
| MCP_PHARMA_API_BASE | No | URL of the hosted backend (default: production) | |
| MCP_PHARMA_LOG_LEVEL | No | Logging level (DEBUG/INFO/WARNING/ERROR, default: WARNING) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| check_drug_registrationA | Статус регистрации в ГРЛС: номер РУ, держатель, даты, статус. Задайте name, mnn или ru_number. Справка, не медицинский совет. Тариф Pro. |
| get_drug_cardB | Карточка из ГРЛС: торговое имя, МНН, формы, держатель, производитель, статус. Справка, не медицинский совет. Тариф Pro. |
| search_drugA | Поиск по ГРЛС: торговое наименование или МНН. Справка, не медицинский совет. Тариф Pro. |
| get_zhnvlp_priceA | Предельная цена из реестра ЖНВЛП по названию или МНН. Справка, не медицинский совет. Тариф Pro. |
| check_recallA | Письма Росздравнадзора о сериях: название, серия, тип письма, номер и дата. Справка, не медицинский совет. Тариф Pro. |
| get_instructionC | Текст инструкции в официальной выгрузке ГРЛС отсутствует, ответ ready=false с причиной. Тариф Pro. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Most tools target distinct resources: search, drug details, registration status, pricing, recalls, and instructions. However, check_drug_registration and get_drug_card both surface status and holder information and accept similar query parameters, so their boundaries could be clearer.
All tool names follow a consistent verb_noun pattern using check_, get_, or search_. There is no mixing of naming conventions or vague action-only verbs.
Six tools is well-scoped for a read-only pharmaceutical registry server. Each tool covers a meaningful query type without unnecessary redundancy or bloat.
Core registry lookups are covered: search, drug card, registration status, pricing, and recalls. However, get_instruction is a non-functional stub that always returns ready=false, so instruction retrieval is a notable gap in the surface.