Shiranui
Shiranui is the Model Context Protocol(MCP) Server for retreiving the clinical standard contents in the CDISC Library.
This MCP server is built with Python FastMCP.
https://github.com/user-attachments/assets/9cd7e1a6-2750-4910-bb03-763c323b9f22
Support CDISC Library API
- v2 Biomedical Concept Endpoints
- v2 Dataset Specialization Endpoints
- Controlled Terminology Codelist Endpoints
- ADaM Variable Metadata Endpoints
- SDTM Metadata Endpoints
- CDASH Metadata Endpoints
- SEND Metadata Endpoints
- Search Tool
Requirements
- Python v3.13 and UV were installed on your device.
- You have the CDISC Library API Key.
Installation
Download Shiranui from the Releases Page.
Mac and Linux
cd /your/shiranui/dir
uv sync
Set your API key as an environment variable named CDISC_LIBRARY_API_KEY.
Windows
Use back slash "\" for path separator charactor.
cd C:\your\shiranui\dir
uv sync
Set your API key as an environment variable named CDISC_LIBRARY_API_KEY.
Configure mcp client
LM Studio
Mac and Linux
{
"mcpServers": {
"Shiranui": {
"command": "uv",
"args": [
"run",
"/full/path/to/shiranui/dir/.venv/bin/shiranui"
]
}
}
}
Windows
Use slash"/" for path separator charactor.
{
"mcpServers": {
"Shiranui": {
"command": "uv",
"args": [
"run",
"C:/full/path/to/shiranui/dir/.venv/Scripts/shiranui"
]
}
}
}
You need to replace "/full/path/to/shiranui/dir" to match your own environment.
In addition to LM Studio, it may also work with Claude Desktop, Codename Goose, and other MCP Clients.
License
This project is licensed under the MIT License - see the LICENSE file for details.
Metadata
Release files for iflow-mcp_i-akiya_shiranui 0.1.0
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 |
|---|---|---|---|---|
| iflow_mcp_i_akiya_shiranui-0.1.0.tar.gz | 64.7 kB | Without provenance | Details for iflow_mcp_i_akiya_shiranui-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| iflow_mcp_i_akiya_shiranui-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for iflow_mcp_i_akiya_shiranui-0.1.0-py3-none-any.whl |
Total release size: 79.1 kB
Release files / iflow_mcp_i_akiya_shiranui-0.1.0.tar.gz
| Download URL | iflow_mcp_i_akiya_shiranui-0.1.0.tar.gz |
|---|---|
| Size | 64.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7a218e7e8f87a03770cea02496fa097df6dc563ac7bc12acac4afd11d46359cd
|
|
BLAKE2b-256 checksum How to use checksums |
9d8b3e140e514b9e7b58d9066026d70a11ca0df5dac538d7e12fa22c1a42c042
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.9.28 {"installer":{"name":"uv","version":"0.9.28","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Debian GNU/Linux","version":"13","id":"trixie","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Release files / iflow_mcp_i_akiya_shiranui-0.1.0-py3-none-any.whl
| Download URL | iflow_mcp_i_akiya_shiranui-0.1.0-py3-none-any.whl |
|---|---|
| Size | 14.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
bfaf28765326e25329e63a46fea47ca82cfbc68464c8f8bf0190aaa17a16a516
|
|
BLAKE2b-256 checksum How to use checksums |
20eaa07c6fd929caee52d99763d9d6ae45d7bbd6d0a38bdd92ce3181127e1c57
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.9.28 {"installer":{"name":"uv","version":"0.9.28","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Debian GNU/Linux","version":"13","id":"trixie","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Security for iflow-mcp_i-akiya_shiranui 0.1.0
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.