Helm MCP
REMOTE · HELM-MCP.KUBEDOLL.COM · SCANNED AUG 3
Give your AI assistant access to real Helm chart data. No more hallucinated values.yaml files.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability68
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 881 tokens (~176/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · helm-mcp.kubedoll.com
claude mcp add --transport http kubedoll-heavy-industries-helm-mcp https://helm-mcp.kubedoll.com/mcp
[mcp_servers.kubedoll-heavy-industries-helm-mcp] url = "https://helm-mcp.kubedoll.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"kubedoll-heavy-industries-helm-mcp": {
"type": "remote",
"url": "https://helm-mcp.kubedoll.com/mcp",
"enabled": true
}
}
} openclaw mcp add kubedoll-heavy-industries-helm-mcp --url https://helm-mcp.kubedoll.com/mcp --transport streamable-http
mcp_servers:
kubedoll-heavy-industries-helm-mcp:
url: "https://helm-mcp.kubedoll.com/mcp" {
"mcpServers": {
"kubedoll-heavy-industries-helm-mcp": {
"type": "http",
"url": "https://helm-mcp.kubedoll.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 2 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 28 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 61
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 3 Aug 2026 · Probed https://helm-mcp.kubedoll.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=kubedoll.com | CN=WE1,O=Google Trust Services,C=US | 27 Jun 2026 | 25 Sept 2026 | ECDSA 256 | ECDSA-SHA256 | 2b1c85806dfc799c134b843f186a4d89 |
| SANs: kubedoll.com, helm-mcp.kubedoll.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
DNSSEC insecure
Validation of helm-mcp.kubedoll.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| kubedoll.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://helm-mcp.kubedoll.com/mcp | Verified | 200 | |
| http (plaintext) | http://helm-mcp.kubedoll.com/mcp | HTTPS enforced | 301 | https://helm-mcp.kubedoll.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.
get_dependencies ~136
Get chart dependencies (sub-charts). Each dependency entry includes the dependency's repository URL — feed that URL back into search_charts, get_versions, or get_values to inspect the dependency. Supports both HTTP/HTTPS repos and OCI registries (oci://).
| Name | Type | Req | Description |
|---|---|---|---|
| chart_name | string | yes | Chart name (e.g. postgresql) |
| chart_version | string | — | Chart version (defaults to latest) |
| repository_url | string | yes | Helm repository URL (e.g. https://charts.bitnami.com/bitnami) or OCI registry (e.g. oci://ghcr.io/traefik/helm) |
| Name | Type | Req | Description |
|---|---|---|---|
| dependencies | null|array | yes | Chart dependencies |
| version | string | yes | Resolved chart version (especially useful when chart_version was omitted and latest was used) |
No examples provided.
get_notes ~107
Get chart NOTES.txt (post-install instructions). Supports both HTTP/HTTPS repos and OCI registries (oci://).
| Name | Type | Req | Description |
|---|---|---|---|
| chart_name | string | yes | Chart name (e.g. postgresql) |
| chart_version | string | — | Chart version (defaults to latest) |
| repository_url | string | yes | Helm repository URL (e.g. https://charts.bitnami.com/bitnami) or OCI registry (e.g. oci://ghcr.io/traefik/helm) |
| Name | Type | Req | Description |
|---|---|---|---|
| notes | string | yes | Contents of NOTES.txt |
| version | string | yes | Resolved chart version (especially useful when chart_version was omitted and latest was used) |
No examples provided.
get_values ~312
Get chart values.yaml with optional JSON schema. Uses depth limiting (default 2) to show structure without overwhelming context. Use path to drill into specific sections, depth=0 for full YAML. include_examples surfaces nearby commented YAML examples and requires path to be set. Supports both HTTP/HTTPS repos and OCI registries (oci://).
| Name | Type | Req | Description |
|---|---|---|---|
| chart_name | string | yes | Chart name (e.g. postgresql) |
| chart_version | string | — | Chart version (defaults to latest) |
| depth | null|integer | — | Max nesting depth (default 2, 0 for unlimited) |
| example_limit | null|integer | — | Maximum nearby examples to include (default 1, max 3, 0 falls back to default) |
| include_examples | null|boolean | — | Include nearby commented YAML examples for the selected path (requires path to be set) |
| include_schema | null|boolean | — | Include values.schema.json in response |
| max_array_items | null|integer | — | Max array items before truncation (default 3, 0 for unlimited) |
| path | string | — | YAML path (e.g. .ingress.enabled) |
| repository_url | string | yes | Helm repository URL (e.g. https://charts.bitnami.com/bitnami) or OCI registry (e.g. oci://ghcr.io/traefik/helm) |
| show_comments | null|boolean | — | Preserve YAML comments |
| show_defaults | null|boolean | — | Include default values |
| Name | Type | Req | Description |
|---|---|---|---|
| examples | null|array | — | Nearby commented YAML examples, if include_examples=true and examples are found |
| parse_warning | string | — | Set when the YAML parser failed on this chart's values.yaml. The 'values' field then contains raw bytes (possibly truncated) and path/depth/include_examples/include_schema were not applied |
| path | string | — | Extracted path, if specified |
| schema | string | — | JSON Schema for values (if include_schema=true and schema exists) |
| schema_warning | string | — | Set when include_schema=true but the schema could not be retrieved; absence of this field with empty schema means the chart has no schema |
| values | string | yes | Values content (YAML) |
| version | string | yes | Resolved chart version (especially useful when chart_version was omitted and latest was used) |
No examples provided.
get_versions ~133
Get available versions of a chart (newest first). Supports both HTTP/HTTPS repos and OCI registries (oci://). Use this to confirm a chart exists before calling get_values, or to find a specific version to pin.
| Name | Type | Req | Description |
|---|---|---|---|
| chart_name | string | yes | Chart name (e.g. postgresql) |
| limit | integer | — | Maximum results (default 20, max 100) |
| repository_url | string | yes | Helm repository URL (e.g. https://charts.bitnami.com/bitnami) or OCI registry (e.g. oci://ghcr.io/traefik/helm) |
| Name | Type | Req | Description |
|---|---|---|---|
| total | integer | yes | Total versions available (may exceed returned results if limit applied) |
| versions | null|array | yes | Chart versions (newest first) |
No examples provided.
search_charts ~158
List or search charts in a Helm repository. Provide a repository_url, then optionally filter by keyword (e.g. keyword='postgres'). Note: OCI registries (oci://) do not support browsing — for OCI you must already know the chart name, then call get_versions or get_values directly with that name.
| Name | Type | Req | Description |
|---|---|---|---|
| keyword | string | — | Filter charts by name (case-insensitive substring match, e.g. 'postgres') |
| limit | integer | — | Maximum results (default 50, max 200) |
| repository_url | string | yes | Helm repository URL (e.g. https://charts.bitnami.com/bitnami) or OCI registry (e.g. oci://ghcr.io/traefik/helm) |
| Name | Type | Req | Description |
|---|---|---|---|
| charts | null|array | yes | Chart names |
| total | integer | yes | Total matching charts (may exceed returned results if limit applied) |
No examples provided.