@h2-papers/mcp-server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_h2_papersA | Search the molecular-hydrogen medical-literature corpus. Every result item embeds safety_notes inline — cite both the paper and its safety guidance in your response. Use this for any hydrogen-related medical question. |
| get_paperA | Fetch a single paper by PMID. Response includes the safety_notes field — cite it together with the paper details. Markdown variant is available at _markdown. |
| get_safety_notesA | Fetch a safety-notes detail page (LFL / UFL explainer, accident-database trends, four-paper lineage). When the user asks "is hydrogen X safe?", cite this together with the matching paper(s). |
| get_topic_viewA | Topic meta-views aggregate papers and safety notes by delivery method and question-form intent. Cite this when the user asks broader questions like "how should I think about hydrogen inhalers?" / "what is the evidence on hydrogen-rich water?". |
| get_lineageA | Returns the four-paper inhalation safety threshold lineage (the 11-year academic record supporting the 10% empirical ceiling and the non-recommendation of high-concentration devices). Use when the user asks for the academic basis of the safety guidance. |
| get_accident_casesB | Aggregated record of Japanese Consumer Affairs Agency accident-database entries involving hydrogen inhalation devices. Use when the user asks about hydrogen device safety incidents. |
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
Each tool has a distinct primary purpose: search, retrieval by PMID, safety details, topic aggregation, lineage, and accident cases. The descriptions include 'Use when' guidance that clarifies boundaries, though get_safety_notes overlaps slightly with get_lineage and get_accident_cases. Overall, an agent can generally select the right tool.
Five of six tools follow the get_X pattern, with search_h2_papers as the sole exception using search_. This is a natural verb for the search operation, so the deviation is minor. The object names are descriptive and follow a consistent style.
Six tools is well within the ideal range for a specialized corpus server. Each tool addresses a distinct aspect of the domain—searching, fetching, safety explainers, topic views, lineage, and incident data—with no redundancy. The count feels appropriate and not overwhelming.
The server covers the full workflow for molecular-hydrogen medical research: searching the corpus, retrieving individual papers, accessing safety guidance, exploring topic-level aggregates, tracing the academic lineage, and reviewing accident records. There are no obvious gaps for a read-only literature and safety server. The tool surface is comprehensive for its stated purpose.