hepdata-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HEPDATA_MCP_TRUST_PROXY_AUTH | No | Set to 1 to trust proxy authentication headers. | |
| HEPDATA_MCP_ALLOW_REMOTE_HTTP | No | Set to 1 to allow remote HTTP connections (only use behind hardened ingress). |
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
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| server_infoA | Return server health, version, and capability metadata. |
| search_recordsB | Search HEPData records using HEPData's native search syntax. |
| get_recordB | Fetch HEPData record metadata or full record JSON. |
| list_tablesB | List tables advertised by a HEPData record. |
| describe_tableC | Describe one HEPData table's metadata, variables, qualifiers, and size. |
| get_tableC | Fetch one HEPData table in JSON, YAML, or CSV format. |
| get_record_exportsB | Return supported HEPData export URLs without downloading files. |
| get_record_versionsB | Return available HEPData record versions and version-specific record URLs. |
| get_jsonldB | Fetch JSON-LD metadata for a HEPData record. |
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 9 tools
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.
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.
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.
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.