Skip to main content
Glama
HEPData

hepdata-mcp

Official
by HEPData
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to hepdata-mcp

No user-submitted related servers found.

    Related Servers

    • mcp-datacite

      pipeworx-io
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides access to DataCite DOIs for research datasets, enabling searching and retrieval of dataset metadata.
      243 npm
      MIT

    • OpenBind MCP Server

      QuentinCody
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables discovery and querying of public OpenBind structure-affinity datasets, experimental binding events, benchmark results, and live Fragalysis targets and observations through read-only REST endpoints without requiring an API key.
      -

    • cern-opendata-mcp-server

      cyanheads
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables searching and exploring CERN Open Data records, files, analysis environments, CMS validated-run (good-run) lists, and HLT trigger paths through MCP tools. Supports exact-vocabulary filtering with live facet counts, license and citation retrieval, and runs over stdio or Streamable HTTP.
      1
      Apache 2.0

    • mcp-inspire-hep

      pipeworx-io
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables searching and retrieving high-energy physics literature, authors, institutions, and conferences from INSPIRE-HEP.
      395 npm
      MIT

    • cern-inspire-mcp-server

      cyanheads
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables searching high-energy-physics literature, author profiles, experiments, and HEPData measurement records, fetching full paper dossiers, computing citation summaries and h-indices, and exporting BibTeX or LaTeX entries through chainable query identifiers. It runs as a stdio process or a local Streamable HTTP server, exposing eight tools and one literature resource.
      1
      Apache 2.0
    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.5/5.0

    Scored across 9 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action: searching records, fetching metadata, listing tables, describing a table, fetching table data, getting exports, versions, JSON-LD, and server info. There is no ambiguity between them.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern (e.g., search_records, get_record, list_tables, describe_table, get_table). Even server_info follows this structure, and there is no mixing of conventions.

    Tool Count5/5

    With 9 tools, the set is well-scoped for a HEPData MCP server. Each tool serves a clear purpose in navigating and retrieving data, and none feel redundant or missing.

    Completeness4/5

    The tool surface covers the core workflows of searching, retrieving, and exploring HEPData records and tables, including versions, exports, and metadata formats. Minor gaps exist, such as no tool for uploading or modifying data, but these are out of scope for a typical read-only data access server.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources