Skip to main content
Glama
Sign In
@h2-papers/mcp-server

@h2-papers/mcp-server

Official
by h2-papers
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

@h2-papers/mcp-server

Model Context Protocol (MCP) server for H2 Papers — PubMed molecular hydrogen medical literature, structured in Japanese with per-paper safety notes inline.

Why

When an AI agent answers a question about hydrogen-related therapy, water, or inhalation, the response should carry both the paper evidence and the delivery-method-aware safety context. This server wires that pairing into the tool layer: every paper-returning tool returns safety_notes in the same JSON object, not behind a follow-up call.

Related MCP server: PubMed MCP Server

Tools (6, implemented in task #11)

Tool

Purpose

search_h2_papers

Filter / sort / paginate the paper corpus. safety_notes inline on each item.

get_paper

Single paper detail. safety_notes always present.

get_safety_notes

Detail pages (LFL/UFL terminology, accident-case index, lineage).

get_topic_view

/topics/{method}/{slug} structured meta view for question-form queries.

get_lineage

The four-paper inhalation safety threshold lineage.

get_accident_cases

Consumer Affairs Agency accident records related to hydrogen inhalers.

Citation policy

Cite results as via H2 Papers with the _canonical URL and the pubmed_url. Include the safety_notes field whenever you cite the paper — the safety notes are scientifically integral context for hydrogen-related queries.

Install (Smithery)

npx -y @h2-papers/mcp-server

Or via Smithery YAML config in your MCP client of choice.

License

MIT

Available Tools

6 tools
get_accident_casesBInspect

Aggregated record of Japanese Consumer Affairs Agency accident-database entries involving hydrogen inhalation devices. Use when the user asks about hydrogen device safety incidents.

Inputs: lang.

get_lineageAInspect

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.

Inputs: lang.

get_paperAInspect

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.

Inputs: pmid (required), lang.

get_safety_notesAInspect

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).

Inputs: lang, slug.

get_topic_viewAInspect

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?".

Inputs: lang, slug, method.

search_h2_papersAInspect

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.

Inputs: q, lang, limit, offset, +7 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.8/5.0

    Scored across 6 tools

    Disambiguation4/5

    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.

    Naming Consistency4/5

    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.

    Tool Count5/5

    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.

    Completeness5/5

    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.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Resources

    Related MCP Connectors

    Related MCP Servers

    • PubMed MCP Server

      emi-dm
      F
      license
      A
      quality
      D
      maintenance
      Enables searching and retrieving detailed information from PubMed articles using the NCBI Entrez API. Supports configurable search parameters including title/abstract filtering and keyword expansion to find relevant scientific publications.
      1
      -

    • PubMed MCP Server

      aglitch120
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables comprehensive biomedical literature research through PubMed database access with advanced search, full-text retrieval, citation analysis, and batch processing capabilities. Supports both local deployment and cloud hosting for seamless integration with AI assistants.
      1
      MIT