Skip to main content
Glama
ckgerteis

jstage-mcp

by ckgerteis
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to jstage-mcp

No user-submitted related servers found.

    Related Servers

    • jstage-mcp-server

      Groshan67
      F
      license
      A
      quality
      B
      maintenance
      Enables searching Japanese scientific articles and journals on J-STAGE, with tools for article search, journal search, and volume listing, returning metadata and links to full text on publisher sites.
      4
      -

    • mcp-cinii

      iwaokimura
      A
      license
      A
      quality
      C
      maintenance
      Enables searching CiNii Research for academic articles, books, grants, and research data, and retrieving metadata for individual items.
      2
      MIT

    • cinii-mcp

      ckgerteis
      A
      license
      A
      quality
      A
      maintenance
      Enables querying Japan's national academic database, CiNii Research, for articles, books, dissertations, KAKEN projects, and researcher profiles via seven MCP tools.
      7
      2
      MIT

    • Japan Data MCP

      yurukusa
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to query Japanese public data (laws, corporations, statistics) from official government APIs, returning normalized English metadata with source attribution.
      1
      MIT

    • crossref-mcp

      jtl-neo
      A
      license
      A
      quality
      C
      maintenance
      Enables scholarly metadata lookups from the Crossref REST API, including works, members, journals, funders, types, licenses, and prefixes, as tools for LLM clients.
      18
      25 PyPI
      MIT
    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

    A4.3/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool targets a distinct operation: full-text search, DOI resolution, and journal issue navigation. There is no real overlap between query-based retrieval and known-identifier lookup, and list_issues is explicitly separated from article record retrieval.

    Naming Consistency5/5

    All tool names follow a consistent jstage_<verb>_<object> pattern using snake_case and a shared prefix. The verbs search, get, and list are predictable and clearly map to their respective actions.

    Tool Count5/5

    Three tools is at the lower end of a well-scoped range, but each tool earns its place by covering a core workflow. The count feels minimal yet sufficient for a focused J-STAGE article server.

    Completeness4/5

    Core discovery workflows are covered: searching articles, resolving a DOI, and navigating journal issues. Minor gaps exist for directly listing articles inside a specific issue or retrieving articles by non-DOI identifiers, but these are workable via search.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources