About Probot Hdi
Probot Hdi is an MCP server in the Healthcare category: a CLI tool for checking drug-drug and herb-drug interactions using the Model Context Protocol. It has been installed 0 times through Conduid.
Install
claude mcp add probot-hdi -- npx -y @kinginsun/mcp-probot-hdinpx -y @kinginsun/mcp-probot-hdiThis server has no ConduID identity, so agent calls to it are not receipted. Pin the version you install and review the source before granting it credentials.
Ask AI
Ask AI about Probot Hdi
Powered by Claude · Grounded in docs
Security checks
- ·README presentNot checked yet.
- ·License declaredNot checked yet.
- ·Tests presentNot checked yet.
- ·Dependencies pinnedNot checked yet.
- ·No dynamic code executionNot checked yet.
- ·Scoped permissionsNot checked yet.
README
mcp-probot-hdi
An MCP (Model Context Protocol) server for querying herb-drug and drug-drug interactions from the Probot HDI database.
The server speaks MCP over stdio and forwards tool calls to the Cancer Probot HTTP MCP API (POST with JSON body and Authorization: Bearer).
Installation
npm install -g @kinginsun/mcp-probot-hdi
Configuration
Token (required)
Create a personal API token in your Cancer Probot account (user center). The plaintext value starts with pb- and is shown only once when created.
Set it via:
export PROBOT_MCP_TOKEN=pb-your_token_here
The server sends this value as the HTTP header Authorization: Bearer <token>. Tokens must start with pb-; other values are rejected at startup.
API base URL (optional)
By default requests go to https://cancer.probot.hk/probot_api/mcp (no trailing slash). Override if you need another deployment:
export PROBOT_HDI_API_BASE=https://example.com/probot_api/mcp
Cursor / Claude Desktop
Add to your MCP configuration:
{
"mcpServers": {
"probot-hdi": {
"command": "npx",
"args": ["@kinginsun/mcp-probot-hdi"],
"env": {
"PROBOT_MCP_TOKEN": "pb-your_token_here"
}
}
}
}
Tools
probot-hdi
Search herb-drug or drug-drug interactions by drug/herb names.
| Parameter | Type | Required | Description |
|---|---|---|---|
drug1 |
string | Yes | Drug/herb name, or multiple aliases in one string separated by ASCII | (see JSON examples) |
drug2 |
string | No | Second drug/herb; same pipe-separated alias convention |
maxRows |
number | No | Maximum results to return (default: 10) |
When only drug1 is provided, the API returns all known interactions involving that item (up to maxRows).
Example:
{
"name": "probot-hdi",
"arguments": {
"drug1": "aspirin|阿司匹林|乙酰水杨酸",
"drug2": "ginkgo biloba"
}
}
probot-search-item
Look up a drug or herb by name and return its item_id. Use this to resolve drug/herb names to unique identifiers before querying interactions by ID.
| Parameter | Type | Required | Description |
|---|---|---|---|
drug |
string | Yes | Drug/herb name, or multiple aliases separated by | |
Example:
{
"name": "probot-search-item",
"arguments": {
"drug": "aspirin|阿司匹林"
}
}
probot-hdi-by-id
Search herb-drug or drug-drug interactions by item_id(s) obtained from probot-search-item.
| Parameter | Type | Required | Description |
|---|---|---|---|
item_id1 |
string | Yes | First item_id |
item_id2 |
string | No | Second item_id |
maxRows |
number | No | Maximum results to return (default: 10) |
When only item_id1 is provided, the API returns all known interactions for that item (up to maxRows).
Example:
{
"name": "probot-hdi-by-id",
"arguments": {
"item_id1": "123",
"item_id2": "456"
}
}
Typical Workflow
- Direct query — Use
probot-hdiwith drug names for a quick one-step lookup. - Two-step query — Use
probot-search-itemto resolve names toitem_id, then useprobot-hdi-by-idfor precise interaction queries. This is useful when you need to verify which drug was matched or reuse the same ID across multiple queries.
Requirements
- Node.js >= 18.0.0
- A valid personal token (
pb-…) inPROBOT_MCP_TOKEN
License
MIT
README mirrored from the source repository 5 months ago. The original is authoritative.