RegNetwork MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| REGNETWORK_MCP_ROOT | No | Optional. Sets the MCP data directory location. Defaults: Windows %LOCALAPPDATA%\RegNetworkMCP; macOS/Linux $XDG_DATA_HOME/regnetwork-mcp or ~/.local/share/regnetwork-mcp. |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_database_statusB | 检查线上统计接口、缓存、源统计一致性和当前工具能力。 |
| resolve_entitiesA | 按完整名称查询来源实体候选；保留歧义和不完整结果，返回的 ID 可用于后续查询。 |
| search_interactionsC | 精确查询起点或终点；至少给出一端名称/已解析 ID。完整性仅针对当前名称候选查询，别名不保证穷尽。 |
| get_neighborsA | 查询一跳上游/下游，保留方向、来源和截断；陌生纯 ID 需先用名称解析。 |
| extract_subnetworkA | 提取输入名称集合内部的有向网络；返回 subnetwork_id、输入状态和最多30条预览，完整边用于导出。 |
| summarize_networkB | 计算已提取子网络的度数、角色组成、自环、连通性；结构地位不等于疾病驱动性。 |
| get_interaction_evidenceA | 读取此前查询/映射取得的来源注释和 PMID；不抓取论文全文，不把缺失值变成证据。 |
| export_networkB | 在专用目录创建可复算网络文件及校验清单，返回可读取的 MCP resource URI。 |
| download_official_fileA | 下载 RegNetwork 官方下载页的一个 .7z 文件到本机 downloads/，写入 SHA-256 清单但不解压。每次仅下载一个官方清单项目，最大 8 GiB。 |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| metadata | |
| schema | |
| limitations |
TDQS
Scored across 9 tools
Each tool has a distinct role: status, entity resolution, exact interaction search, one-hop neighbor retrieval, subnetwork extraction, summarization, evidence retrieval, export, and official file download. The descriptions explicitly bound overlapping concepts such as search vs. neighbors and extraction vs. summarization.
All tool names use snake_case and follow a predictable verb_noun or verb_adjective_noun pattern. The verbs are clear and consistent across the set.
Nine tools is well-scoped for a regulatory network database connector. Each tool covers a necessary stage of the workflow: status, lookup, traversal, extraction, analysis, evidence, export, and download.
The surface covers the main read-only lifecycle for querying, analyzing, exporting, and downloading regulatory network data. Minor gaps remain, such as no standalone search by PMID or explicit alias enumeration, but the descriptions acknowledge these limitations.