artifacthub-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_TRANSPORT | No | Transport mode: stdio or streamable-http | stdio |
| ARTIFACTHUB_RETRIES | No | Retries on HTTP 429, 502, 503, 504 and timeouts | 2 |
| ARTIFACTHUB_TIMEOUT | No | Request timeout in seconds | 30 |
| ARTIFACTHUB_BASE_URL | No | API root (for a self-hosted instance or proxy) | https://artifacthub.io/api/v1 |
| ARTIFACTHUB_MAX_CHARS | No | Responses longer than this are cut with a notice | 20000 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Look up cloud-native packages on Artifact Hub: Helm charts, operators, kubectl plugins, policies and more. Start with search_packages to get the kind, repo and name of a package, then use package_details, security_report, changelog or chart_values with those three values. Data is read-only and needs no credentials.
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_packagesA | Search Artifact Hub packages by free text (websearch syntax: quoted phrases, -exclusions, 'or'). Returns compact rows with kind, repo, name, version, app version, stars, last update, publisher trust flags and a non-zero vulnerability summary, plus the total count and next_offset for paging. Use the kind/repo/name values with the other tools. |
| package_detailsA | One-call profile of a package: description, versions (latest plus recent releases with dates and security-update flags), install reference, chart dependencies, container images, vulnerability summary, source links, maintainers, signing, publisher trust flags, stars and production-usage count. Readme text is left out on purpose. |
| security_reportA | Vulnerability scan summary for a package version's container images (Trivy results published on Artifact Hub). Resolves the package id itself. Returns per-image counts by severity and how many have a fix, then the worst findings (critical first, fixable first) with installed and fixed versions. An absent report is explained, not an error. |
| changelogA | Release notes for a package. Pass since_version to get only the releases newer than the version you run (the upgrade delta); otherwise the newest entries are returned. Each entry has the date, a security-update flag and trimmed change lines. Not every publisher provides a changelog; that case is reported. |
| chart_valuesA | Inspect a chart's default values.yaml without downloading all of it (they are often thousands of lines). Without |
| find_repositoriesA | Find package repositories (publishers) by name, for example to see whether a vendor has a verified or official repo, which kind it hosts, its URL and when Artifact Hub last tracked it. |
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 targets a distinct facet of the Artifact Hub workflow: discovery (search_packages, find_repositories), package profiling (package_details), and deep-dives (security_report, changelog, chart_values). The only near-overlap — vulnerability summaries in package_details vs. the detailed scan in security_report — is explicitly clarified in the descriptions as summary vs. per-image findings.
All names are consistent snake_case, but the style is mixed between verb_noun (search_packages, find_repositories) and bare noun phrases (package_details, security_report, changelog, chart_values). Terminology also drifts slightly between 'packages' and 'chart' (chart_values), which is a minor deviation from an otherwise predictable pattern.
Six tools is well-scoped for a read-only registry-inspection server, with no filler: search, profile, security, changelog, values and repo lookup each cover a distinct user need. Nothing feels thin or padded.
The surface covers the natural read lifecycle: discover packages and repos, get full package metadata, inspect security posture, review release notes, and examine chart defaults. Minor gaps exist (e.g. no way to list all versions of a package independently, no signature/verification or compare-versions helper), but agents can work around these via the existing tools.